>I am using Win2k SP 1 with Outlook2k (with a large bundle of patches,
mostly security
>stuff)...and I have not noticed the behavior you mention.
>For the record, when I began my reply to this note, your original was
in HTML
>or RTF (I forgot to pay attention), not plaintext. I simply typed
<ALT>-o|T
>(Format|Plaintext) and got down to business.
I nagged my sysadmin, and it turned out the Exchange was set to still
send out multipart-MIME even when the message was configured as
PlainText. He's changed that setting now, so this one should be fine.
My belief is that individual message rebroadcasts don't get much
processing by the listserv app, so they pass through the same way;
readers using email clients that can handle multipart-MIME OK get a
readable message (if they can handle HTML, they show a pretty plain HTML
message; if they don't like HTML they show the PlainText). But
ActiveState's mail app doesn't do a good job with multipart-MIME, and so
screws up the message when either building the digest or saving to the
web archive.
For whatever that's worth.
_______________________________________________
ActivePython mailing list
[EMAIL PROTECTED]
http://listserv.ActiveState.com/mailman/listinfo/activepython
