Daniel Kahn Gillmor writes:
On 09/11/2013 08:44 PM, Stephen J. Turnbull wrote:
Abhilash Raj writes:
I have attached all 3 type of message, each in a different file. Please
can you place it in your maildir and check how your MUAs respond to it
and report here? The message
On 09/12/2013 03:11 AM, Stephen J. Turnbull wrote:
So you're proposing this, I guess:
multipart/signed
multipart/mixed
text/whatever # optional mailman header
multipart/signed
text/whatever # original signed
On 09/11/2013 04:58 AM, Abhilash Raj wrote:
I have attached all 3 type of message, each in a different file. Please
can you place it in your maildir and check how your MUAs respond to it
and report here? The message signature will not be verified(the
signature text is actually gibberish),
On 09/13/2013 12:29 AM, Daniel Kahn Gillmor wrote:
http://dkg.fifthhorseman.net/src/mailman/multisigned-images/
I've added a fourth message, with a variant on the content wrapping
structure stephen and i were just talking about:
└┬╴multipart/signed 11903 bytes
├┬╴multipart/mixed 8561 bytes
Daniel Kahn Gillmor writes:
I'm just pointing out that mailman commonly produces what you've
called invalid data,
In the OpenPGP sense that the whole message cannot be considered to be
validly signed, even though it may contain a multipart/signed part
with a valid signature.
and that its
In the upcoming mailman 2.1.16 there has been the introduction of the optional
feature author_is_list
Replace the sender with the list address to conform with policies like ADSP
and DMARC. It replaces the poster's address in the From: header with the list
address and adds the poster to the
