-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Jeff DeReus wrote:
Unfortunately filter_content was not set to yes. I am assuming that would be fairly "handy".
I'm not sure whether that will any effect on the archiving or not. It's been a long time since I tested that.
Although everything goes through properly with filter_content disabled and when unsigned.
To be clear, does the message arrive properly to list members or is the attachment and body stripped there as well as in the archives? In my testing only the archived copy was stripped.
As to the message in the archives, the only piece that successfully arrived was
Skipped content of type multipart/mixed-------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 186 bytes Desc: This is a digitally signed message part Url : http://www.blah.org/pipermail/developers/attachments/20060510/529c55f0/PGP.b... <http://www.cactuscode.org/pipermail/developers/attachments/20060510/529c55f0/PGP.bin>
The archiver bug is mentioned here, but I couldn't see any resolution to that part of the problem (and sourceforge isn't cooperating with me ATM):
http://mail.python.org/pipermail/mailman-coders/2005-March/001687.htmlHowever, viewing the list mbox file the full message with the attachment ?flattened? is there.
Flattened? Reading the mbox of my test list with mutt the message and attachment were all normal and the signature verified properly.
Todd OpenPGP -> KeyID: 0xD654075A | URL: www.pobox.com/~tmz/pgp
A snooze button is a poor substitute for no alarm clock at all.
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (GNU/Linux) Comment: When crypto is outlawed bayl bhgynjf jvyy unir cevinpl.
iG0EARECAC0FAkRrgjomGGh0dHA6Ly93d3cucG9ib3guY29tL350bXovcGdwL3Rt ei5hc2MACgkQuv+09NZUB1qNiQCgyOLh8+FLr+VOhAM2smIW6VS7MyQAn2p27nQv /h16smlehbhCcMqyfV7/ =JTNq -----END PGP SIGNATURE-----