[Mailman-Users] Gmail now flagging list emails as suspicious
Hi everyone, We have a mailman list running version 2.1.38. https://homesteadfarm.org/mailman/listinfo/neighbors_homesteadfarm.org The list has been in service for more than 20 years and we have 400+ people on the list who live in our neighborhood. Recently, Gmail is flagging list emails with this message (in a bright orange-yellow box): Be careful with this message Gmail could not verify that it actually came from homesteadfarm.org. Avoid clicking links, downloading attachments, or replying with personal information. I read through the archives and thought there was a similar thread. In particular, this response seemed relevant: https://www.mail-archive.com/mailman-users@python.org/msg73812.html In particular: 4) Add your own outgoing DKIM signature. My apologies in advance if I am asking a stupid question, but how does one go about adding their own outgoing DKIM signature? Thanks, Matt -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/
[Mailman-Users] Re: Gmail now flagging list emails as suspicious
On 2/27/22 22:19, mattf...@gmail.com wrote: My apologies in advance if I am asking a stupid question, but how does one go about adding their own outgoing DKIM signature? This needs to be done by the admins of the server that hosts the list. It appears that your list is a cPanel Mailman list hosted by InMotion Hosting, Inc. You would need to contact them about this. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/
[Mailman-Users] Re: Gmail now flagging list emails as suspicious
You can set up DKIM pretty easily on cPanel in my experience. Look for the "email deliverability" link under "email" on the account home page. If you have WHM access (unlikely on a shared account, likely on a VPS) you can manage all your accounts, again using the "email deliverability" link under "email" in the left navigation pane. On Mon, Feb 28, 2022 at 9:17 AM Mark Sapiro wrote: > On 2/27/22 22:19, mattf...@gmail.com wrote: > > > > My apologies in advance if I am asking a stupid question, but how does > one go about adding their own outgoing DKIM signature? > > > This needs to be done by the admins of the server that hosts the list. > > It appears that your list is a cPanel Mailman list hosted by InMotion > Hosting, Inc. You would need to contact them about this. > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, Californiabetter use your sense - B. Dylan > -- > Mailman-Users mailing list -- mailman-users@python.org > To unsubscribe send an email to mailman-users-le...@python.org > https://mail.python.org/mailman3/lists/mailman-users.python.org/ > Mailman FAQ: http://wiki.list.org/x/AgA3 > Security Policy: http://wiki.list.org/x/QIA9 > Searchable Archives: > https://www.mail-archive.com/mailman-users@python.org/ > https://mail.python.org/archives/list/mailman-users@python.org/ > -- === Russell Clemings === -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/
[Mailman-Users] DMARC Wrap Message doesn't preserve addressees
We've noticed that with DMARC moderation set to "Wrap Message", the rewritten header doesn't preserve the original addressee list. In the particular case that I'm looking at right now, the list address itself is removed from the Cc header. We've had a few complaints that this results in responses not going back to the list, as intended. I don't see a related config option, but I'm wondering if I've missed something. Is this possibly the side-effect of, or an undesirable interaction with, some other configuration option we might have set? We're running v2.1.38. Thanks -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/
[Mailman-Users] Re: DMARC Wrap Message doesn't preserve addressees
On 2/28/22 15:41, Matthew Pounsett wrote: We've noticed that with DMARC moderation set to "Wrap Message", the rewritten header doesn't preserve the original addressee list. In the particular case that I'm looking at right now, the list address itself is removed from the Cc header. We've had a few complaints that this results in responses not going back to the list, as intended. Wrap message is intended to send the original message wrapped in an outer message from the list. This is something akin to a MIME format digest containing only one message. Replying to the message works best if you can open the message/rfc822 message part which is the original message and reply to that. That said, not all MUAs make that easy or even possible. The wrapper itself will only copy the To:, In-Reply-To:, References:, Subject:, X-Mailman-Approved-At: and Date: headers from the wrapped message. In addition, it will include any headers that were set or modified by the CookHeaders handler. These include X-Ack:, X-BeenThere:, X-Mailman-Version:, Precedence:, List-Id: and From: and may or may not include X-Ack:, Reply-To: and Cc: depending on various list settings and message characteristics. See remarks beginning at https://bazaar.launchpad.net/~mailman-coders/mailman/2.1/view/head:/Mailman/Handlers/CookHeaders.py#L193 and https://bazaar.launchpad.net/~mailman-coders/mailman/2.1/view/head:/Mailman/Handlers/CookHeaders.py#L272 for things that affect this. I don't see a related config option, but I'm wondering if I've missed something. Is this possibly the side-effect of, or an undesirable interaction with, some other configuration option we might have set? There is no configuration setting per se. The bottom line is the original Cc: will not be in the wrapper in many cases. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/
[Mailman-Users] Re: DMARC Wrap Message doesn't preserve addressees
On Mon, Feb 28, 2022 at 9:23 PM Mark Sapiro wrote: > > message characteristics. See remarks beginning at > https://bazaar.launchpad.net/~mailman-coders/mailman/2.1/view/head:/Mailman/Handlers/CookHeaders.py#L193 > and > https://bazaar.launchpad.net/~mailman-coders/mailman/2.1/view/head:/Mailman/Handlers/CookHeaders.py#L272 > for things that affect this. The logic there is a bit complex, so let me see if I've got this straight ... if I set reply_goes_to_list to 1, and the message already has a reply_to, the list address would be appended to that header? Or replace it? It's not entirely clear to me. -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/
[Mailman-Users] Re: DMARC Wrap Message doesn't preserve addressees
On 2/28/22 19:25, Matthew Pounsett wrote: The logic there is a bit complex, so let me see if I've got this straight ... if I set reply_goes_to_list to 1, and the message already has a reply_to, the list address would be appended to that header? Or replace it? It's not entirely clear to me. If first_strip_reply_to is Yes, the list address will replace the Reply-To. If it is No, the list address will be added to the Reply-To. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/
