Signed emails that contain URLs that Gmail makes into links do not verify. If I instead view the original, which is plaintext, select the signed block, and verify that, it checks out just fine.

Can we switch to looking at the raw email to verify it? Or is that a security concern since Gmail is injecting formatting into the original message, which is simply different from the original and we don't want to go back before it parsed and enhanced the message? Curious... And if a client sends a multi-part message, could each part be signed via PGP and verified separately? Like the text/plain part could be verified by itself (without web addresses and emails enhanced by gmail) and a text/html rich part could still be signed and verified in its text version... just wondering how easy that integration is.

The nabble page above that has the "bug" is due to the html on the page. if you copy the "original" text, you get the > that was escaped as HTML entities (>). If you view the source of the page and take that, though, you get something different, which is probably the source of the problem - mis-interpreting HTML entities. Any thoughts?