James
James
Yes, it's invalid, but unfortunately, messages in the wild still put encoded words there. I don't think adding a decoding step here is a problem. I think in this case,...
No. And I haven't been able to reproduce it with newer messages, only ones from last year. Chances are they fixed it already.
@emersion are you opposed to making such a change to your library?
No updates, sorry. Didn't get around to pursuing this issue any further.
Thanks for the interest! We're working on it. @LBeernaertProton is in contact with the IMAP Wiki maintainers; we'll deal with this as soon as we find the time.
Hi @BlackLight, thanks for the detailed feedback. Please excuse the delay in replying, just got back from vacation. Just to be sure we're on the same page: as far as...
Hey, finally got a chance to look into this. The parts in the code you linked to are unrelated (they're used for importing messages, not sending/building). However, the root cause...
`crypto.NewPlainMessage` does *not* call `internal.CanonicalizeAndTrim`. I think you may have misread the function(s) you linked to. Here the two functions (the first just calls `clone`, the second calls `CanonicalizeAndTrim`): ```...
Right there, follow the link you just posted and read the implementation of `NewPlainMessage` (few lines above what you linked to). It doesn't call `CanonicalizeAndTrim`. The fix is to use...
It's only important for clearsigned messages. The spec requires trimming trailing whitespace from each line; that's just an unfortunate limitation of the format. See for instance [Inline PGP in E-mail...