[GTALUG] We are having DMARC/DKIM troubles ...

[Bob Jonkman]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Stewart wrote:
> The reason given by Yahoo is this:
> 
> https://help.yahoo.com/kb/postmaster/SLN7253.html

That's got it completely backwards. For a mailing list the "Sender" is
the list address, "From" is the person who actually wrote the
message[1]. And if "Reply-to" munging must be done, then common (bad)
practice is to set it to the list address.

I wouldn't take any pains to accommodate such a badly broken mail
provider, especially on a technical list like this where people
understand the problem.

I run a number of mailing lists, and on the non-technical lists I do
mung "Reply-to" to the list address because the subscribers to those
lists expect that behaviour. My preference is to mung "Reply-to" only
when the message author has not explicitly set it, respecting the
author's intent. As far as I know, only Listserv can do this. Sadly,
neither Mailman nor Mercury Mail have that degree of finesse.

I'm sure everyone has seen this and the posts leading up to it:
http://marc.merlins.org/netrants/reply-to-still-harmful.html

- --Bob.

[1] http://tools.ietf.org/html/rfc5322#section-3.6.2


- --
Bob Jonkman <bjonkman at sobac.com>          Phone: +1-519-635-9413
SOBAC Microcomputer Services             http://sobac.com/sobac/
Software   ---   Office & Business Automation   ---   Consulting
GnuPG Fngrprnt:04F7 742B 8F54 C40A E115 26C2 B912 89B0 D2CC E5EA

On 2016-06-11 11:19 AM, Stewart C. Russell wrote:
> If replies seem patchy, we've just had a bunch of people - mostly
> Yahoo and Rogers users - auto-kicked from the list due to DMARC.
> This is an ongoing pain for list admins. The reason given by Yahoo
> is this:
> 
> https://help.yahoo.com/kb/postmaster/SLN7253.html
> 
> Yeah, they're advising Reply-To mungeing as an industry standard.
> Joy!
> 
> cheers, Stewart --- Talk Mailing List talk at gtalug.org 
> https://gtalug.org/mailman/listinfo/talk
> 


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
Comment: Ensure confidentiality, authenticity, non-repudiability

iEYEARECAAYFAldcTMYACgkQuRKJsNLM5eoWbwCg3cRsDNfJMAfWvC2chKUZgz1m
3zAAoMAzmEbUd2YxO4r9naAn4hodSLQZ
=ng6P
-----END PGP SIGNATURE-----