4 ms·

If the mailing list changes the From address, then the message won't show the correct author in the message list in my email client. Replying may work (because

If the mailing list changes the From address, then the message won't show the correct author in the message list in my email client. Replying may work (because of Reply-To:), but not having the correct "From" in the client is really a deal breaker. Besides, DKIM already solved this problem by not caring where the mail comes from, just that the message was signed. It seems the solution to me is to stop using SPF if you want to use mailing lists.

gcp 10y ago
Which email client is that? Presumably, this could be fixed (well, worked around) there.
- __david__ 10y ago
  Thunderbird. I suspect most clients operate this way.
  - gcp 10y ago
    File a bug? Maybe there's an extension for it, too. AFAIK almost every mailing list has to deal with the DMARC problem by rewriting From.
noja 10y ago
Why not? The from: address would be the mailing list address, but the from: name could be the original poster's name.
- phicoh 10y ago
  The problem is that address books pick up stuff out of "From: User <user@domain>". So if you now start sending mail with "From: User <no-reply@mailing-list>" you create a lot of chaos.
  - noja 10y ago
    Some clients have a "reply to list" button, so they can recognise a mailing list. Perhaps they could then also handle the name problem.
garaetjjte 10y ago
DMARC policy rejects messages only when they failed both SPF and DKIM checks. It seems problem is that mailing lists like to mangle message content.
- phicoh 10y ago
  That's not a problem. Mailing lists have been doing that since long before DMARC. Having the mailing list name in the Subject is very handy. Footers are also more convenient that having to look in headers.
- Nazzareno 10y ago
  Not exactly, the DMARC policy is very flexible. Each server, after a period of monitoring when he receives a detailed report of what would happen if a policy is enforced, can define his own policies.

gcp 10y ago

Which email client is that? Presumably, this could be fixed (well, worked around) there.

__david__ 10y ago
Thunderbird. I suspect most clients operate this way.
- gcp 10y ago
  File a bug? Maybe there's an extension for it, too. AFAIK almost every mailing list has to deal with the DMARC problem by rewriting From.

noja 10y ago

Why not? The from: address would be the mailing list address, but the from: name could be the original poster's name.

phicoh 10y ago
The problem is that address books pick up stuff out of "From: User <user@domain>". So if you now start sending mail with "From: User <no-reply@mailing-list>" you create a lot of chaos.
- noja 10y ago
  Some clients have a "reply to list" button, so they can recognise a mailing list. Perhaps they could then also handle the name problem.

garaetjjte 10y ago

DMARC policy rejects messages only when they failed both SPF and DKIM checks. It seems problem is that mailing lists like to mangle message content.

phicoh 10y ago
That's not a problem. Mailing lists have been doing that since long before DMARC. Having the mailing list name in the Subject is very handy. Footers are also more convenient that having to look in headers.
Nazzareno 10y ago
Not exactly, the DMARC policy is very flexible. Each server, after a period of monitoring when he receives a detailed report of what would happen if a policy is enforced, can define his own policies.