[Bug 558193] Re: admin.py unicode error patch (shouldn't these all be fixed?)
mark at msapiro.net
Thu Mar 29 02:16:16 CEST 2012
This bug report seems, at least currently, invalid. Email addresses in
Mailman must be us-ascii. This has been strictly enforced since Mailman
2.1.6. Prior to that, control characters [\000-\037\177] could get
through and prior to 2.1.2, high-bit characters [\200-\377] could get
through, but no longer.
Further, contrary to the assertion that non-ascii email addresses are
valid, I don't thing they are, at least in an SMTP environment and
Mailman send via SMTP. RFCs 821, 2821 and 5321 all say "Commands and
replies are composed of characters from the ASCII character set".
Presumably, this applies to "RCPT TO <forward-path>". In addition, both
RFC 2821 and 5321 say in section 4.1.2 Command Argument Syntax "Systems
MUST NOT define mailboxes in such a way as to require the use in SMTP of
non-ASCII characters (octets with the high order bit set to one) or
ASCII "control characters" (decimal value 0-31 and 127)." RFC 821
doesn't say exactly that, but the BNF grammer in its section 4.1.2.
COMMAND SYNTAX is even stricter.
Further, according to RFCs 822, 2822 and 5322, headers in messages must
be ascii, and RFC 2047 which specifies a way to encode non-ascii in
headers is clear that email addresses can't be so encoded.
Finally, comments in the original Debian bug <http://bugs.debian.org
/cgi-bin/bugreport.cgi?bug=315358> report from which this derives
recognize that this is an issue of invalid list data being migrated from
Mailman 2.0. I hope by this late date, that is no longer an issue.
** Bug watch added: Debian Bug tracker #315358
** Changed in: mailman
Status: New => Invalid
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
admin.py unicode error patch (shouldn't these all be fixed?)
To manage notifications about this bug go to:
More information about the Mailman-coders