On Thursday 27 December 2018 05:06:04 am Miles Fidelman wrote:
> Speaking as someone who hosts a couple of dozen email lists, I really
> don't understand what the fuss is about here.
>
> DMARC breaks mailing lists - it's that simple. It breaks pretty much
> anything that forwards mail. (FYI: Early on, it broke the IETF's
> lists. Rather annoying, that.)
>
> If one runs a list, and wants folks on gmail, AOL - any service that
> honors p=reject - then one has to:
>
> 1. adjust headers so that list mail appears to originate from the list
> manager, not from the original author

1.) is my understanding of what TDE does. Here are some of the {snipped} TDE
headers:

Return-Path: <trinity-users-return-{snip}@???>
Envelope-to: {snip}@???
Reply-To: trinity-users@???
From: Michael <{snip}@???>
To: trinity-users@???
X-Get-Message-Sender-Via: srv04.srv04-inet-design.com: authenticated_id:
inetd/from_h
X-Authenticated-Sender: srv04.srv04-inet-design.com: {snip}@???

My guess is it's either, or both together, Reply-To or Return-Path that make
the desired behavior change. Based upon the email ‘From: chillfan’ here that
doesn’t work that has in the headers:

Reply-To: chillfan@??? [1]

instead of no ‘Reply-To:’ at all for messages here that do work.

(Return-Path seems to already be set.)
(Added the X- as TDE seems to authenticate me as a sender, where Devuan
doesn’t. No real idea if that’s relevant.)

# # #

As we seem to be way over thinking this....

Suggestion: Just try adding, or replacing if already present, the ‘Reply-To:’
for all messages with the value:

Reply-To: dng@???

That’s not going to break the list, and will answer the question immediately.

Best,
Michael

[1] I would mangle that, but it’s clear text in the original.