[Re: ATTMail's handling of MIME headers]
Does anyone else have any additional information on this.
The following info is not ATTMail related, but is also about MIME
header dropping.
I found out how LISTSERV (a widely used mailing list server) does MIME
headers. If a receiver wants to receive MIME messages, then he/she
must set IETFHDR for him/herself, for the particular mailing list on
that server. The default is apparently not to pass MIME (and other)
headers.
So, while people can get around this problem, it could be quite
irritating.
I realize that changing MIME in any major way would reset it to
"Proposed", and that that is therefore not desirable. But it seems to
me that, *if* anybody wants to get around this problem, then they
could define a new content type or subtype, e.g. message/mime, which
would mean that a MIME message is enclosed, possibly with some unique
string that could be used by receiving software when the top-level
MIME headers have been stripped.
Content-Type: message/mime
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0
From: suzie(_at_)harvard(_dot_)edu
To: joe(_at_)foo(_dot_)com
Subject: new proposal
dslfkjsdlkfjsdlkfgjsglkjsdlfkjsddslkjfdsf <--- unique string
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0
Hi Joe,
How's things? [...]
This is roughly how I would want to do it. Comments?
I'm not sure how much of a problem MIME header dropping is going to
be, but I'm pretty sure that nobody else knows either (not even Ned).
Regards,
Erik