On Wednesday, June 4, 2014 8:38:49 PM CEST, Wietse Venema wrote:
I'll read the RFCs carefully and see where it allows UTF8 in SMTP
command parameters and replies.
You'll do that, but I'll tell you anyway: The client may use it once the
server has issued an EHLO response containing SMTPUTF8, and the server may
use it once the client has issued a MAIL FROM, VRFY or EXPN command with
the SMTPUTF8 parameter.
Postfix (both with and without my patch) violates that. If a client tells
Postfix:
MAIL FROM:<æ@æ.æ>
then Postfix may conceivably answer that æ@æ.æ is not a legal sender
address, since æ.æ isn't a valid domain. 6531 says that that response
should be ASCII-only, since the client hasn't given permission to use UTF8
in responses. My viewpoint is that no matter what RFC6531 says, the client
must accept hearing its own arguments in the SMTP reply. Postfix is right
and 6531 is wrongish, so I followed Postfix' reply style rather than comply
with 6531.
However even without reading those RFCs it is clear that UTF8 cannot
be used in 220 server greetings or in EHLO commands or replies,
because at that time the server/client have not agreed to use UTF8.
Right.
Thus, myhostname (or equivalent) must be ASCII, as it always must
have been. There is no need to use valid_mail_domain() in
reject_non_fqdn_hostname etc.
Right. I made some mistakes. I wish I were perfect, but know I am not.
Arnt
