DMARC Failures for Mailing List
Now that we've got our new mail server going and the DMARC reports are coming in, I'm finding a lot of DMARC failures for messages that I'm sending to this list.
It seems that when I send a message to this list, the list software forwards it to other people on my behalf, but uses my email address in the header_from.
This results in an SPF failure, because SPF only allows our MX to send mail for our domain.
The DKIM check is also failing. I think the list software may be re- writing the message bodies.
Another user that I replied to on this list a day ago said my list mail went to spam on his gmail.
- Will our domain reputation be harmed by having a lot of copies of the same messages going to a bunch of different people on different ISPs and all of them failing DMARC?
It seems that some places are using databases that look for duplicate content sent to multiple recipients to identify bulk mail and spam.
- Is there any way to mitigate DMARC issues for mailing lists? It seems like the mailing list software should be sending out the emails as itself, not as the user that submitted the message.
Now that we've got our new mail server going and the DMARC reports are coming in, I'm finding a lot of DMARC failures for messages that I'm sending to this list.
It seems that when I send a message to this list, the list software forwards it to other people on my behalf, but uses my email address in the header_from.
This results in an SPF failure, because SPF only allows our MX to send mail for our domain.
The DKIM check is also failing. I think the list software may be re-writing the message bodies.
Another user that I replied to on this list a day ago said my list mail went to spam on his gmail.
- Will our domain reputation be harmed by having a lot of copies of the same messages going to a bunch of different people on different ISPs and all of them failing DMARC?
It seems that some places are using databases that look for duplicate content sent to multiple recipients to identify bulk mail and spam.
- Is there any way to mitigate DMARC issues for mailing lists? It seems like the mailing list software should be sending out the emails as itself, not as the user that submitted the message.
On 17/11/2023 12:38 EET Nick Lockheart forum@ageofdream.com wrote:
Now that we've got our new mail server going and the DMARC reports are coming in, I'm finding a lot of DMARC failures for messages that I'm sending to this list.
It seems that when I send a message to this list, the list software forwards it to other people on my behalf, but uses my email address in the header_from.
This results in an SPF failure, because SPF only allows our MX to send mail for our domain.
The DKIM check is also failing. I think the list software may be re- writing the message bodies.
Another user that I replied to on this list a day ago said my list mail went to spam on his gmail.
- Will our domain reputation be harmed by having a lot of copies of the same messages going to a bunch of different people on different ISPs and all of them failing DMARC?
It seems that some places are using databases that look for duplicate content sent to multiple recipients to identify bulk mail and spam.
- Is there any way to mitigate DMARC issues for mailing lists? It seems like the mailing list software should be sending out the emails as itself, not as the user that submitted the message.
Now that we've got our new mail server going and the DMARC reports are coming in, I'm finding a lot of DMARC failures for messages that I'm sending to this list.
It seems that when I send a message to this list, the list software forwards it to other people on my behalf, but uses my email address in the header_from.
This results in an SPF failure, because SPF only allows our MX to send mail for our domain.
The DKIM check is also failing. I think the list software may be re-writing the message bodies.
Another user that I replied to on this list a day ago said my list mail went to spam on his gmail.
- Will our domain reputation be harmed by having a lot of copies of the same messages going to a bunch of different people on different ISPs and all of them failing DMARC?
It seems that some places are using databases that look for duplicate content sent to multiple recipients to identify bulk mail and spam.
- Is there any way to mitigate DMARC issues for mailing lists? It seems like the mailing list software should be sending out the emails as itself, not as the user that submitted the message.
There is an ARC signature, and you need to somehow whitelist the key used to sign it. Then hopefully it is less failing.
Aki
On Fri, 17 Nov 2023, Nick Lockheart wrote:
Now that we've got our new mail server going and the DMARC reports are coming in, I'm finding a lot of DMARC failures for messages that I'm sending to this list.
[...]
- Is there any way to mitigate DMARC issues for mailing lists? It seems like the mailing list software should be sending out the emails as itself, not as the user that submitted the message.
I believe Mailman can be (and should be) configured to do exactly this.
Best regards
Kenneth
dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-leave@dovecot.org
On 11/17/23 10:38, Nick Lockheart wrote:
The DKIM check is also failing. I think the list software may be re-writing the message bodies.
I believe one of the reasons for the DKIM failure is this addition/configuration by mailman in the footer of every message (the unsubscribe stuff):
>>
dovecot mailing list --dovecot@dovecot.org To unsubscribe send an email todovecot-leave@dovecot.org
>>
--x9p
On 11/17/23 10:38, Nick Lockheart wrote: The DKIM check is also failing. I think the list software may be re- writing the message bodies. I believe one of the reasons for the DKIM failure is this addition/ configuration by mailman in the footer of every message (the unsubscribe stuff):
>>
dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-leave@dovecot.org
>> --x9p
participants (4)
-
Aki Tuomi
-
Kenneth Irving
-
misc＠x9p.org
-
Nick Lockheart