David B?rgin:
> I?m running a milter that may perform rejection (SMFIS_REJECT) at the
> milter HELO stage. This condition appears in the system log as follows:
>
> Jan 04 13:50:07 mail postfix/smtpd[149922]: connect from unknown[156.0.64.217]
> Jan 04 13:50:07 mail spf-milter[147333]: mail.mydomain.org (helo): fail
> Jan 04 13:50:07 mail spf-milter[147333]: rejected message from sender
> "mail.mydomain.org"
> Jan 04 13:50:07 mail postfix/smtpd[149922]: NOQUEUE: milter-reject: HELO from
> unknown[156.0.64.217]: 550 5.7.23 SPF validation failed; proto=SMTP
> helo=<mail.mydomain.org>
The remote SMTP client sent EHLO (or HELO). The Milter rejected the
command with "550 5.7.23 SPF...". Postfix logged the response and
replied to the remote SMTP client.
> Jan 04 13:50:07 mail postfix/smtpd[149922]: NOQUEUE: milter-reject: MAIL from
> unknown[156.0.64.217]: 550 5.7.23 SPF validation failed; from=<> proto=SMTP
> helo=<mail.mydomain.org>
The remote SMTP client sent MAIL FROM. Postfix reused the last
Milter "reject", logged the response, and replied to the remote
SMTP client.
So the real question is "Why did the client not disconnect after
receiving a 550 EHLO reponse?". Servers aren't supposed to disconnect
after replying with 550.
Wietse
