Quanah Gibson-Mount:
>
> 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[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
Note that this is logged within the same second, so changing the
POSTFIX milter_xxx_timeout settings has no effect.
Have you considered changing the timeout settings on the MILTER end?
It is possible that the Milter times out when requests from Postfix
are too far apart in time. The Postfix SMTP server has a 300s time
limit for client commands (reduced to 10s under overload). The Milter
time limit may be less.
The error message comes from this Postfix code fragment:
/*
* Receive the packet length.
*/
if ((vstream_fread(milter->fp, (char *) &len, UINT32_SIZE))
!= UINT32_SIZE) {
smfic_name = str_name_code(smfic_table, event);
msg_warn("milter %s: can't read %s reply packet header: %m",
milter->m.name, smfic_name != 0 ?
smfic_name : "(unknown MTA event)");
If you monitor the postfix-to-Milter communication with a network
sniffer, then you will see that the Milter closes the connection
without sending the SMFIC_RCPT reply to Postfix.
Wietse
