Am Mi, den 14.07.2004 schrieb Philippe um 13:13: > > mailq -v > ======================================================================= > [root@P4 root]# mailq -v > /var/spool/mqueue (1 request) > -----Q-ID----- --Size-- -Priority- ---Q-Time--- > --------Sender/Recipient--------i6EB0ihR002857 150 210483 Jul > 14 18:00 <phd2@xxxxxxxxxxxxxx> > (host map: lookup (fcomfrench.com): deferred) > <phd2@xxxxxxxxxxxxxx> > Total requests: 1 > ======================================================================= > > [root@P4 root]# cat /etc/resolv.conf > search AAA > nameserver 203.146.237.237 > nameserver 203.146.237.222 > ======================================================================= > [root@P4 root]# cat /etc/hosts > # Do not remove the following line, or various programs > # that require network functionality will fail. > 192.168.0.1 P4.AAA P4 > 127.0.0.1 localhost.localdomain localhost > ======================================================================= Philippe, the error or at least the reason for queuing is plainly obvious there! Why didn't you earlier post the output of "mailq -v", because exactly that shows what's the reason. Until now I thought the queue would not contain any useful information. The reason for queuing is that fcomfrench.com can not be resolved! >> host map: lookup (fcomfrench.com): deferred) << Your DNS setup is broken in some kind. From "host -a fcomfrench.com" I see an A record with a very short TTL. Do you very freqently update that record with the actual IP? I think you better switch to use your ISP's SMTP server as your smart host. 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 17:52:03 up 1 day, 15:34, load average: 0.20, 0.38, 0.35
Attachment:
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
