| Summary | PGP: Bad signature for mails with to long lines |
| Queue | IMP |
| Queue Version | 6.1.6 |
| Type | Bug |
| State | Not A Bug |
| Priority | 2. Medium |
| Owners | |
| Requester | balthasarbiedermann (at) gmail (dot) com |
| Created | 01/17/2014 (4223 days ago) |
| Due | |
| Updated | 01/22/2014 (4218 days ago) |
| Assigned | 01/17/2014 (4223 days ago) |
| Resolved | 01/22/2014 (4218 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Not A Bug
Therefore, the use of [OpenPGP] with format=flowed messages is
strongly discouraged. [OpenPGP-MIME] is recommended instead.
We only send messages as OpenPGP-MIME. As per the RFC, there is
absolutely nothing wrong with this and is, in fact, explicitly allowed.
Looks like Thunderbird is confusing OpenPGP w/ OpenPGP-MIME when
dealing with these kind of messages.
State ⇒ Feedback
Can verify that the signature is verified as good with the GnuPG4win
reference program (Claws Mail) and mutt.
Priority ⇒ 2. Medium
Patch ⇒ No
Milestone ⇒
Queue ⇒ IMP
Summary ⇒ PGP: Bad signature for mails with to long lines
Type ⇒ Bug
State ⇒ Unconfirmed
I found a bug in in imp when you try to sign a message with pgp.
If I create a Mail with a to long line, imp does not apply automatic
line wrapping, but uses format=flowed instead. For such a mail the PGP
signature is shown as bad when it is checked with
Thunderbird/Enigmail/Gpg4win or with R2Mail2 on Android. Horde itself
shows a valid PGP signature.
For mails with no long lines (less than 78 characters per line) the
signed mails are validated as correct with all clients.