In honor of recent discussions on pipermail, I think I've found another issue with archiving, though this seems to be in Mailman.Scrubber.
In a few recent posts to the GnuPG lists, Werner Koch sent along some signed patches fixing issues in the gpg code. Unfortunately, the archives ate his posts[1] so we can't point others to the patches in the archives as nicely as one would like. It seems that the problem is that both message parts lack a "Content-type: text/plain; charset=us-ascii" header and the first part also lacks a "Content-disposition: inline" header. If I edit the raw message to include a "Content-type: text/plain; charset=us-ascii" header for each mime part, it passes the scrubber as is archived properly. From my limited reading of RFC 2045[2], it seems that a mime part without a content-type header should be assumed to be text/plain; charset=us-ascii. Is the scrubber wrong to not assume this or are there too many issues with making this (apparently quite standards conformant) assumption? [1] http://lists.gnupg.org/pipermail/gnupg-users/2006-December/029976.html [2] http://www.ietf.org/rfc/rfc2045.txt -- Todd OpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ====================================================================== To know what is right and not to do it is the worst cowardice. -- Confucius
pgpbumhTkm81V.pgp
Description: PGP signature
------------------------------------------------------ Mailman-Users mailing list [email protected] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
