> > Mar 7 13:25:36 armor postfix-113/smtpd[4009829]: NOQUEUE: reject:
> > RCPT from unknown[173.213.231.144]: 504 5.5.2 <cp4435>: Helo command
> > rejected: need fully-qualified hostname; from=<>
> > to=<webad...@example.org> proto=ESMTP helo=<cp4435>
> >
> > reject_non_fqdn_helo_hostname,
>
> > It also appears that smtpd_helo_required is still set to the default
> > 'no', but wouldn't it normally be advisable to enable that check?
>
> Replace "reject_non_fqdn_helo_hostname" with:
>
> main.cf:
> pcre = pcre:${config_directory}/
>
> # In the client, helo, sender or recipient restriction list
> smtpd_..._restrictions =
> ...
> check_helo_access ${pcre}non-fdqn-helo.pcre
> ...
>
> non-fdqn-helo.pcre:
> /^cp4435$/ DUNNO
> /^/ reject_non_fqdn_helo_hostname
Okay, very interesting. I hadn't realized I could add commands to
files referenced in restrictions. But I still want to leave the
reject_invalid_helo_hostname parameter?
I've now added the check_helo_access to smtpd_recipient_restrictions
and smtpd_helo_restrictions, but do I really need
smtpd_helo_restrictions if I'm also adding them to
smtpd_recipient_restrictions?
Thanks so much for your help.
