[ale] testing firegpg with mailman

[Jeremy T. Bouse]

Jim Kinney wrote:
> So we have now verified that the problem is NOT mailman but FireGPG (it
> _is_ beta software). We have sent signatured email from non-firegpg and
> successfully read them with both firegpg and other email readers. This
> eliminates mailman from mangling gpg sigs generically.
> 
> We have also sent firegpg through ale to firegpg and the sig is good in
> Firegpg only. My emails all come through Ale's mailman with intact
> signature yet non firegpg users report errors.
> 
> This indicates to me that firegpg has an outbound error that breaks
> other readers but is also inversely flawed on the read as firegpg will
> report correct signature on messages it sends and then reads. Thus it
> can correct the error.
> 
> I suspect a broken mime parser is adding then removing the spurious
> linefeed. Time for a bug report.
> -- 
> -- 
> James P. Kinney III
> Actively in pursuit of Life, Liberty and Happiness        
> 

	Actually I'm not certain we've said it's FireGPG itself... I have sent
multiple emails from Gmail w/ FireGPG to myself and have had the
signature verified successfully... The only time the Gmail/FireGPG
signatures are not verifying is when the message is sent through Mailman
when sending to ALE. Otherwise FireGPG hasn't produced any issues, so I
still contend that Mailman or the ALE server itself is doing something
to the message before re-sending it out to the list. Also as I've read
responses others have duplicated my results and conclusions as well.

	Yes, FireGPG is probably doing some other things that it probably
shouldn't but it doesn't seem to be affecting this issue.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 261 bytes
Desc: OpenPGP digital signature
Url : http://mail.ale.org/pipermail/ale/attachments/20091129/606748ad/attachment.bin