Mailman 3 options and results:
DMARC mitigation action: Wrap the message in an outer message From: the list.
DMARC Mitigate unconditionally: No
DMARC rejection notice:
DMARC wrapped message text:
From: Michael Paoli via BALUG-test3 <balug-test3(a)lists.balug.org>
Reply-To: Michael Paoli <[localpart](a)yahoo.com>
DMARC mitigation action: Reject the message
DMARC Mitigate unconditionally: Yes
DMARC rejection notice: Testing DMARC rejection
DMARC wrapped message text: DMARC wrapped message text: headers may be munged
(no munging when posted from @linuxmafia.com)
posting from @yahoo.com bounces:
Your message to the BALUG-test3 mailing-list was rejected for the following
reasons:
Testing DMARC rejection
DMARC mitigation action: Reject the message
DMARC Mitigate unconditionally: No
DMARC rejection notice: Testing DMARC rejection
DMARC wrapped message text: DMARC wrapped message text: headers may be munged
posting from @yahoo.com bounces:
Your message to the BALUG-test3 mailing-list was rejected for the following
reasons:
Testing DMARC rejection
DMARC mitigation action: Wrap the message in an outer message From: the list.
DMARC Mitigate unconditionally: No
DMARC rejection notice: Rejected due to DMARC.
DMARC wrapped message text: Because of DMARC, headers may be munged
posting from @yahoo.com:
adds a first MIME section that has:
Because of DMARC, headers may be munged
From: Michael Paoli via BALUG-test3 <balug-test3(a)lists.balug.org>
Reply-To: Michael Paoli <[localpart](a)yahoo.com>
DMARC mitigation action: Reject the message.
DMARC Mitigate unconditionally: Yes
DMARC rejection notice:
DMARC wrapped message text:
posting from @yahoo.com:
our message to the BALUG-test3 mailing-list was rejected for the following
reasons:
You are not allowed to post to this mailing list From: a domain which
publishes a DMARC policy of reject or quarantine, and your message has
been automatically rejected. If you think that your messages are
being rejected in error, contact the mailing list owner at
balug-test3-owner(a)lists.balug.org.
Anyway, given the potentially non-ideal situation with DMARC, this seems best compromise:
DMARC mitigation action: Wrap the message in an outer message From: the list.
DMARC Mitigate unconditionally: No
DMARC rejection notice:
DMARC wrapped message text:
And hyperkitty has at least some display/munging issues:
greater than symbol on at least end of email address
shows as as apersand gt semicolon
at symbol in at least email address show as (a)