On 06/29/2012 12:00 PM, Steve wrote: > not meaning to spark up new discussions about this issue (we've had that > before). But I really think, the energy invested in this discussion > would be better invested in writing mailman tweaks.
In the language of software engineering, this has moved from a defect to fix to a lifecycle issue. "Defect" is the stage where a bug is reported: "fix" is the stage where the fix is available: "lifecycle" is the often years-long process of getting the fix out to people who need it. If I understand things correctly (and I may not be), Werner does not host gnupg.org himself. He rents a box in a colo facility for that, and he's more or less stuck with whatever versions of software the provider offers. The provider hasn't offered an updated GNU Mailman, so GnuPG-Users has this unfortunate situation where PGP/MIME doesn't reliably work on it. For what it's worth, my message left here as a correctly-signed PGP/MIME message. I received it back from the list as just 'signature.asc'. A (partial) diff of the two emails reveals: > > This is an OpenPGP/MIME signed message (RFC 2440 and 3156) > --===============1821215289== 12,13c61,62 < protocol="application/pgp-signature"; < boundary="------------enigBE03611A84F54D493777EBD6" --- > protocol="application/pgp-signature"; > boundary="------------enigBE03611A84F54D493777EBD6" 71a121,135 > > > --===============1821215289== > Content-Type: text/plain; charset="us-ascii" > MIME-Version: 1.0 > Content-Transfer-Encoding: 7bit > Content-Disposition: inline > > _______________________________________________ > Gnupg-users mailing list > [email protected] > http://lists.gnupg.org/mailman/listinfo/gnupg-users That should hopefully make it clear exactly what the problem is. _______________________________________________ Gnupg-users mailing list [email protected] http://lists.gnupg.org/mailman/listinfo/gnupg-users
