On 7/17/23 4:29 PM, Reindl Harald wrote:
no single mailing-list on this planet does this - period
Can we agree to disagree?
Maybe no /contemporary/ mailing list. But there have been -- and I
contend still are -- LOTS of mailing lists that did / do this very thing.
.forward does this.
Alias expansion does this.
Mailman 2.x used to do this by default.
I've seen multiple mailing lists sate that they will unsubscribe people
if they send email from a domain with strict SPF settings because they
refuse to deal with altering the RFC5321.MailFrom envelope address.
You only need to look as far as mailing lists getting tripped by SPF.
If the mailing lists weren't re-using the RFC5321.MailFrom from the
incoming message in the message that they send out, there wouldn't be a
problem. Yet there have been many GB of email written about this very
problem.
DMARC/DKIM are problematic for mailing-lists but
envelope-ender/spf/spoofing-protecting is a no-brainer
I take it that you are in favor of the mailing list sending outgoing
messages using an RFC5321.MailFrom envelope sender that is different
than the the incoming message's RFC5321.MailFrom envelope sender.
Before VERP and SPF it was very common for mailing lists to send
outgoing messages with the same RFC5321.MailFrom as the incoming message
had.
it's time to understand the difference between from-header and
envelope-sender or for the sake of god stop operating public mailservers
at all
Yet there are people that don't know the difference.
Grant. . . .
