On 9/3/2009 3:55 PM, Jack wrote:
Hello Everyone,
I have the following settings in my postfix config:
smtpd_helo_required = yes
smtpd_recipient_restrictions =
reject_invalid_helo_hostname,
check_helo_access hash:/etc/postfix/helo_access,
reject_invalid_helo_hostname,
reject_non_fqdn_helo_hostname,
No reason to have reject_invalid_helo_hostname listed twice...
Now either I’m being to strict with the above and possibly causing some
rejects or exchange boxes are not helping keep things simple.
The below is the logging from one of the rejects, I see the non_fqdn is
at play here, but should I not be using that in my setting or should the
sender update their helo string??
I don't see anything like that. Did you post the wrong log
snippet?
Sep 3 09:01:29 pluto postfix/smtpd[20653]: NOQUEUE: filter: RCPT from
mail3.hbo.com[64.236.235.240]: <la...@d3.com>: Recipient address
triggers FILTER filter:dummy; from=<marvelle.southerl...@hbo.com>
to=<la...@d3.com> proto=ESMTP helo=<nymail1.homebox.com>
... a check_recipient_access map with a FILTER result.
Sep 3 09:01:29 pluto postfix/smtpd[20653]: NOQUEUE: reject: RCPT from
mail3.hbo.com[64.236.235.240]: 450 4.7.1 <la...@d3.com>: Recipient
address rejected: SPF-Result=nymail1.homebox.com: 'SERVFAIL' error on
DNS 'SPF' lookup of 'nymail1.homebox.com'; from=<m...@hbo.com>
to=<la...@d3.com> proto=ESMTP helo=<nymail1.homebox.com>
an SPF failure, caused by a temporary DNS error. I assume
this is some SPF policy service.
Postfix doesn't complain about the helo anywhere here, and
nothing obviously wrong with the helo the client used.
-- Noel Jones
