-----BEGIN PGP SIGNED MESSAGE----- I recall that before the 2.0 release there were some problems with messages getting mangled so that the following error appeared when viewing in pine:
[Error: Formatting error: Non-hexadecimal character in QP encoding] After moving to 2.11, this bug appears to have re-appeared and a new, similar bug was introduced. What's really strange is that this bug appears to be related to the full body report, which I had turned off in my local.cf. Did upgrading to 2.11 overwrite my local.cf? Is that supposed to happen when I ugrade? - -- Public key #7BBC68D9 at | Shane Williams http://pgp.mit.edu/ | =----------------------------------+------------------------------- All syllogisms contain three lines | [EMAIL PROTECTED] Therefore this is not a syllogism | www.gslis.utexas.edu/~shanew -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBPId6/Wa83yV7vGjZAQG2mgQAhNKc4Kd/Wcf1BoEKoePdxjXtEVSacKCa UNC2IYuh2PDG+qNAvks9cvz4EDU5THGkKUyJZmySXAi5eA7tYmGXjZgSywdMPwiz qxm02iM239JHmV+WPLcFs2rXeDrlfMSNNhoefV9VxhcbNjZ6gHU2ufjAlbxWp4HH d02Ahzjm7+8= =hMdX -----END PGP SIGNATURE----- _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
