Note: postfix 2.7.10 release
A number of customers are noting that they are getting the following error
when using a milter:
Jun 26 20:18:10 zmail postfix/smtpd[11438]: connect from
server.domain.com[1.2.3.4]
Jun 26 20:18:10 zmail postfix/smtpd[32729]: NOQUEUE: filter: RCPT from
server.domain.com[1.2.3.4]: <bounce-2596705-20907...@list.somewhere.com>:
Sender address triggers FILTER smtp-amavis:[127.0.0.1]:10026;
from=<bounce-2596705-20907...@list.somewhere.com> to=<u...@domain.com>
proto=ESMTP helo=<server.domain.com>
Jun 26 20:18:10 zmail postfix/smtpd[32729]: warning: milter
inet:127.0.0.1:7026: can't read SMFIC_RCPT reply packet header: Success
Jun 26 20:18:10 zmail postfix/smtpd[32729]: NOQUEUE: milter-reject: RCPT
from
server.domain.com[1.2.3.4]: 451 4.7.1 Service unavailable - try again later;
from=<bounce-2596705-20907...@list.somewhere.com> to=<u...@domain.com>
proto=ESMTP helo=<server.domain.com>
Jun 26 20:18:10 zmail postfix/smtpd[32729]: lost connection after RCPT from
server.domain.com[1.2.3.4]
Jun 26 20:18:10 zmail postfix/smtpd[32729]: disconnect from
server.domain.com[1.2.3.4]
So far, we've tried increasing timeouts for the milter via:
milter_connect_timeout
milter_command_timeout
milter_content_timeout
But even for very large values, we are still seeing the problem occur.
Setting milter_default_action=accept stops the error messages, but then
bypasses the milter for these messages, somewhat defeating the purpose of
the milter. ;)
Any hints on what else we can look at?
Thanks,
Quanah
--
Quanah Gibson-Mount
Sr. Member of Technical Staff
Zimbra, Inc
A Division of VMware, Inc.
--------------------
Zimbra :: the leader in open source messaging and collaboration
