In further messing around, I've discoverd a difference in how webmail handles text in the "plain text" and "rich text" formatted emails. I havent quite nailed it down for firegpg, but it certainly makes a difference for my other gpg software...

When you're writing in plain text formatted email, the text doesnt have any special formatting and remains the way you're typing it... and the text box just wraps the text to fit in the box... when you hit save, the webmail program does re-wrap the text (which from what I can tell is what is breaking the signatures)

but... when you're writing in a rich text formatted email, the text never gets "re-wrapped" when you click send which means the signature never breaks...

Try and throw in that concept into your testing and see if that helps you reveal the problem better... Hope it helps!

I just did some testing to see what exactly the problem is... it's not just with FIREGPG... it happens with other PGP software and gmail as well.

It seems that when you write a message in gmail with text that exceeds 80 characters (and wraps with soft carriage returns) gmail will rewrap the line by cutting it back as much as 10 characters after it's sent (or you click the send button anyway). This changes the signed texted enough to fail the signature.

The only fix I can see is to manually wrap lines (hard carriage return) at the 80th character to prevent google from re-wrapping itself and breaking the signature. Teh Ghey!

Oh yea... and the proportional font used in the message body text box makes this near impossible!