Jeremy there are a bunch of ways that we can handle this, but knowing "certain" people I'm sure the only acceptable solution is for us to modify the archived emails in the mbox, so that the past archives show up properly. Of course that would not deal with the on-going emails....
The settings to modify Pipermail behavior are all in ~mailman/Mailman/mm_cfg.py (look in Defaults.py for examples of items to change/set) There are a lot of options we can change there and then play with re-archiving. I've got a few test beds of 2.1 running on my home network so it's easy for me to do. Let me know if you want me to look at it. The best answer for Trilug is for someone to setup Mhonarc on the Mailman server and use that instead of Pipermail. I would volunteer to do that, but everytime I touch the servers Tanner and I come to blows, and I've had enough of him to last me the rest of my life. Jon On Thu, 2003-08-14 at 13:01, Jeremy Portzer wrote: > Hello. > > I feel like this must be an F.A.Q. but I could find no mention of it in > the searchable archives or the FAQ-O-Matic. > > Anyway, it seems that evolution has a bug in message display that > affects GPG-signed email sent to mailman 2.1.x lists (when the GPG > signature uses PGP/MIME). Mailman adds the list's signature as a MIME > attachment, and for some reason evolution shows ONLY the list signature, > and not the body of the message at all! > > This is apparently fixed in Evolution 1.4.3, but unfortunately a large > number of our users are using prior versions of evolution, like 1.2.2 > that's included in Red Hat Linux 9. I suspect this is true of many > users around the community. Though this is an evolution bug, most of > our users are seeing it as a "mailman problem," because suddenly they > cannot view their messages after we upgraded to mailman 2.1.x. > > Does anyone have any ideas or workarounds? Is there any way to make > mailman 2.1.2 go back to the old behavior that doesn't use MIME to add > the signature (or just skips it for MIME messages) ? > > Note: I've also heard that Outlook Express has a similar problem > reading GPG-signed emails with evolution's MIME-added signature, so this > isn't really uniquely an evolution problem. But Outlook Express handles > GPG pretty pitifully anyway, so I'm not worrying about that. > > Thanks for any advice, > > Jeremy ------------------------------------------------------ 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
