Just out of curiosity, why is this not the MTA's job? (actually I'm really surprised it made it through the MTA unscathed)
I suppose maybe the RFC says something about it...hmm...
Here's a fun one that I think Mailman ought to worry about.
I've started getting reports of truncated digests coming out of my site. It always seemed to truncate after a specific user's posting in the digest.
When I went looking, it turns out that user had a signature that happened to have a NULL (ascii 0) character at the end -- and that causes some mail clients (Netscape for one) to think it's hit EOF and it stops reading the message.
This has a couple of implications for Mailman: it hoses digests, which is a big problem. And it would cause all mailman footers on individual messages to be missing. I'll bet (but haven't looked yet) that it casues problems in the archives, too.
Because of this, I think Mailman needs to be sensitive to NULL characters and strip them from messages during processing. If they exist in a message, they need to be deleted.
chuq
Chuq Von Rospach - Plaidworks Consulting (mailto:chuqui@plaidworks.com) Apple Mail List Gnome (mailto:chuq@apple.com)
And they sit at the bar and put bread in my jar and say 'Man, what are you doing here?'"
Mailman-Developers mailing list Mailman-Developers@python.org http://www.python.org/mailman/listinfo/mailman-developers