raf via Postfix-users:
> > From reading the code, these two restrictions seem equivalent except when
> > SMTPUTF8 extension is used.
> > when the SMTPUTF8 is in play, reject_non_fqdn_helo_hostname will convert a
> > hostname containing UTF to an internationalized domain name
> > before checking. https://en.wikipedia.org/wiki/Internationalized_domain_name
> >
> > So reject_invalid_helo_hostname will reject hostnames that contain UTF8 but
> > are otherwise valid.
The implementation almost gets this right.
reject_invalid_helo_hostname only allows valid ASCII forms. There
is a source-code comment "Fix 20140706" that EAI is not allowed here.
reject_non_fqdn_helo_hostname allows UTF-8 if the client requests
SMTPUTF8, which makes no sense because EHLO must be sent before the
client can request SMTPUTF8 support. This was not fixed on 20140706,
apparently the result of a classical mistake: fix one problem and
assume that there are not other instances of that problem.
Wietse
_______________________________________________
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
