On 4/14/22 10:45 AM, Mark Sapiro wrote:
On 4/14/22 10:18, David Newman wrote:
On 4/14/22 9:50 AM, Mark Sapiro wrote:
It could accept a defective message or one with specific defects, but this is problematic for further processing. For example, at least one MUA, Thunderbird, renders such a message with an empty body.
That's not my experience. Mailman 3 accepted without complaint a PGP-signed message I sent from Thunderbird 91.8.0 and forwarded it to list subscribers with the message body intact.
Yes, and that's what we expect, but MM 3 does not accept the defective message, and T-bird does not render the body of such a message. I.e., if such a message composed by Apple Mail 15 is sent via a non-Mailman channel to a T-bird user, the user can't read it.
Sorry, I misspoke. The Apple Mail sender used S/MIME signing, not PGP signing.
In Thunderbird, I was able to read an S/MIME-signed message the user sent directly to me complaining about the 501 bounce. Thunderbird said the signature was invalid due to the use of an untrusted CA, but I could read the message body.
dn