Community
Participate
Working Groups
I got a DMARC notification after I sent an email from my personal email to the incubator mailing list, because your mailman installation kept the DKIM headers after having modified the subject and body, which then failed validation. I suppose your mailman should drop the DKIM signature, resign it with its own signature and also change the envelope sender, because if it keeps my email as sender it will fail DMARC verification everywhere. I'm only midly affected because my DMARC policy is "none", but yahoo.com users for example have a "reject" policy, so it means they're all pretty much excluded from using your mailing lists, as every SMTP host that checks DMARC will reject any email to your mailing list coming from them.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
@Webmaster - this issues seems to be getting much worse since it was first filed here (and in Bug 414061). I guess this is because so many more companies are turning on stricter dmarc?
It's possible. We're actively working on deploying a new mail server. -M.
I have been running with this rule in Gmail for a while and it seems to have mostly resolve the issue on my end: Matches: list:(eclipse.org) Do this: Skip Inbox, Never send it to Spam The messages that fail DMARC/etc still show up with a warning like this in gmail: This message was not sent to Spam because of a filter you created.
DKIM should be correctly handled now. -M.
