/etc/resolv.conf and sendmail

[Alexander Dalloz]

Am Do, den 15.07.2004 schrieb Philippe um 18:00:

> > Looks ok too. The only thing you will face is, that your private domain
> > name AAA and the FAQD P4.AAA is not resolvable for any mail host
> > outside. So many MTAs will reject your mail and not accept it. Therefor
> > I asked you to better choose your ISP's SMTP server as smart host.
> I have no choice right now, my ISP does not offer it.
> By the way, I don't have any mail rejected, as far as I am concerned.

Wonders me a bit, because meanwhile - since certainly around 2 years -
most MX host admins do not allow mail sent from unresolvable host
addresses. I.e. within Sendmail configuration you will have to
explicitly enable the acceptance of those mails. Ok, if your ISP does
not offer you such a service that is bad. Another fact is that big ISPs
like AOL do not any more accept mail coming from dial-in IPs. More and
more admins restrict things like that to fight the SPAM hitting their
machines and customer accounts.

> > A last question. You showed us a mail being in queue with "mailq -v"
> > output with recipient <phd2 at fcomfrench.com>. Is only that one queued
> > after the initial start of Sendmail after a reboot or every recipient?
> Every ercipient. I chenged the email address in the log to protect my
> recipient from spam. But any mail is queued, until the first sendmail
> restart. Then, no more problem. That is why I think that when sendmail
> is started at boot, with of course no connection and an empty
> resolv.conf, it decides to queue every mail. Why ? I really don't know.

O, you changed the information from "mailq -v". I understand that but
makes it harder to find the devil which makes your mail queuing. So
speaking more generally: once you restarted your system and still see
your mail is queued and not immediately sent you will have to run "mailq
-v" to see which mails are in the queue. The command will too give you
the reason why the mail is queue and did not leave your host. Either it
is deferred because of host lookup error or another reason might be a
temporary error on the recipient MX host side. This information is
essential to know what happens! If again you find the mail queued
because of hostname lookup error you will have to run the debug code I
gave you yesterday, to check if it reports additional useful
information.

From current state I see no way to help you out. From so far given error
message it is clearly a DNS error. Do you run a caching nameserver your
own? You may too try using different DNS servers in the
/etc/resolv.conf.

> I try the IPV6 trick and I will tel you more.

Ok.

> Philippe

Alexander


-- 
Alexander Dalloz | Enger, Germany | GPG key 1024D/ED695653 1999-07-13
Fedora GNU/Linux Core 2 (Tettnang) Athlon CPU kernel 2.6.6-1.435.2.3.uml
Serendipity 18:08:39 up 2 days, 15:50, load average: 2.19, 1.94, 1.57 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
Url : http://lists.fedoraproject.org/pipermail/users/attachments/20040715/17b5c2a6/attachment-0002.bin