>One possible explanation is that the filter queries a >broken DNS (blocklist) server When the problem occured, I already thought about the broken DNSBL query. The content filter isn't doing any DNSBL check and the problem persists.
>Another possibility is that the >Postfix SMTP server behind the content filter has problems when it >tries to resolve the 127.0.0.1 client IP address to a hostname. How would be resolving a problem 127.0.0.1 when in my /etc/hosts.conf I have : order hosts,bind and the right entry in /etc/hosts How does the qmgr determines when it can send the message to the content filter ? Marco -----Message d'origine----- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] De la part de Wietse Venema Envoyé : vendredi 26 septembre 2008 15:40 À : Postfix users Objet : Re: Delivery delay problems Marco TCHI HONG: > Our problem is that mail stay a long time in the active queue before the > content filter, but when it's sent to the server where mailboxes are > stored there's no problem: > > Sep 26 10:11:57 mx postfix/smtp[1387]: 1906C718411: > to=<[EMAIL PROTECTED]>, relay=127.0.0.1[127.0.0.1]:9026, conn_use=5, > delay=230, delays=0.93/210/0/19, dsn=2.0.0, status=sent (250 2.0.0 Ok > (2.0.0 Ok: queued as 5A0B6718ACF )) Wietse: > The mail spends 19 seconds in the content filter. This means that > your content filter performance sucks. Marco TCHI HONG: > Ok, so the problem is definitely a content filter problem ? > This has nothing to do with our Postfix configuration if I understand. You need to find out why the mail spends 19 seconds in the content filter. One possible explanation is that the filter queries a broken DNS (blocklist) server. Another possibility is that the Postfix SMTP server behind the content filter has problems when it tries to resolve the 127.0.0.1 client IP address to a hostname. And then there are a billion other possibilities. Wietse
