> Now to tackle the problem of MIME-tools not 2047-encoding headers. Right
> now it (MIME-tools and hence Majordomo) follows the GIGO rule; if 8-bit
> headers come in, they go out. This is suboptimal, but it's also impossible
> to rectify in a sane manner.
I have just noticed that it is possible to make a very strong case for this
GIGO behavior from RFC1123:
5.3.6 Mailing Lists and Aliases
An SMTP-capable host SHOULD support both the alias and the list
form of address expansion for multiple delivery. When a
message is delivered or forwarded to each address of an
expanded list form, the return address in the envelope
("MAIL FROM:") MUST be changed to be the address of a person
who administers the list, but the message header MUST be left
unchanged; in particular, the "From" field of the message is
unaffected.
I would argue that together with Jason's arguments which show that there is no
generally useful alternative to GIGO behavior, this is sufficient justification
for making GIGO the default behavior of Majordomo with respect to 8-bit
characters in comments of the From: header, as long as a configuration option
is provided which can be used to force Majordomo to emit only RRC-822 compliant
messages.
However, more serious syntax errors in the From: address should by default be
handled by consulting the list-owner about the message, IMHO.
-- NB.
References:
|
|
