Re: [dmarc-ietf] non-mailing list use case for differing header domains

2020-08-09 Thread Jim Fenton
On 8/5/20 9:36 AM, Jesse Thompson wrote: > On 8/4/20 11:52 AM, Alessandro Vesely wrote: >> On 2020-08-04 6:10 p.m., Dotzero wrote: >>> There is another solution. Move users to a separate domain from the domain > Long ago we put users on our org domain as a way to unify users (in a very > decentral

Re: [dmarc-ietf] non-mailing list use case for differing header domains

2020-08-09 Thread Dave Crocker
On 8/9/2020 9:54 AM, Tõnu Tammer wrote: "Message transit from author to recipient is through relays that typically make no substantive change to the message content and thus preserve the DKIM signature." If this is not the case, the relay is actually violating DKIM standard. However, a mailing

Re: [dmarc-ietf] non-mailing list use case for differing header domains

2020-08-09 Thread Tõnu Tammer
Hi! I keep reading the discussion and I am surprised how people express views that current DMARC standard does not work. I am surprised that technical people here express this view. DMARC relies on SPF and DKIM. The latter is particularly important for the mailing lists to ensure that DMARC works

Re: [dmarc-ietf] non-mailing list use case for differing header domains

2020-08-09 Thread Hannu Aronsson
Hello, Quick correction: As DMARC requires only either DKIM or SPF which I had confused, this removes the need for the proposal point 1). Thanks for the off-list help received. This seems to be mostly an SPF issue, but still remains when - SPF used used alone without DMARC (not sure if relevant

Re: [dmarc-ietf] non-mailing list use case for differing header domains

2020-08-09 Thread Hannu Aronsson
Hello, I have been lurking here around for a while and we have been working at M3AAWG for some time as well. Today’s DMARC is breaking more and more email as it gets more widely and often overly strictly deployed. I feel the major issue with DMARC is email forwarding in it’s many forms, in ad