Opened 7 years ago
Closed 18 months ago
#2087 closed task (fixed)
difficulty posting on gdal-dev and osgeo incubator lists
Reported by: | jive | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | SysAdmin | Keywords: | |
Cc: |
Description
Received the following via email:
Dear Incubator-owner,
Last week I send my first email to the incubator@…. Even though the email arrived in the archive, it was not received by all subscribers.
- It was not received by Jody Garnett
- I did receive it myself, but with a warning that:" This sender failed our fraud detection checks and may not be who they appear to be."
I looked into the header of the email that I received and it contains the following:
Authentication-Results: spf=pass (sender IP is 140.211.15.3) smtp.mailfrom=lists.osgeo.org; surrey.ac.uk; dkim=fail (signature did not verify) header.d=surrey.ac.uk;surrey.ac.uk; dmarc=fail action=none header.from=surrey.ac.uk;
On the Mailman developer Wiki I found a discussion about DKIM trouble: https://wiki.list.org/DEV/DKIM
So my best guess is that Mailman breaks the DKIM signature that is created by surrey.ac.uk, and leaves the broken signature in place. Therefore the message fails authentication tests and is not delivered to all users.
I suppose this is not an issue specific to the OSGeo incubator list. Nevertheless it seems to be a problem that requires a solution. Please let me know if you need any further information from me. If you are aware of a workaround that I can follow that would also be great.
With kind regards,
Alex
Change History (8)
comment:1 by , 7 years ago
comment:3 by , 7 years ago
Summary: | difficulty posting on osgeo incubator list → difficulty posting on gdal-dev and osgeo incubator lists |
---|
comment:4 by , 7 years ago
Component: | Mailing Lists → Systems Admin |
---|---|
Owner: | changed from | to
Reassigning to SAC, I'm afraid I'm helpless in this kind of mailman issues, sorry.
comment:5 by , 7 years ago
Added REMOVE_DKIM_HEADERS = Yes
to /etc/mailman/mm_cfg.py
. Please verify that it does the trick.
comment:6 by , 7 years ago
I just tried it with the following message:
https://lists.osgeo.org/pipermail/incubator/2018-February/003556.html
The problem does not seem to be resolved. I receive the same warning that "This sender failed our fraud detection checks and may not be who they appear to be."
The email header contains the same snippet that I quoted before. Please let me know if you need the full email header to help diagnose the problem.
comment:7 by , 6 years ago
I have received some feedback from my email provider. They write the following:
We have been sending out a standard communication with mail providers as and when a new mailprovder or list is used.
"Most if not all mailing list software now has a way of better handling DMARC reject policies. Occasionally this requires an update to a more recent version of the list software or configuring some settings.
Most of these settings involve re-writing the FROM domain of emails with a DMARC reject policy and adding a “Reply-to” address so the user experience is effectively the same. Recipients can therefore not only receive the emails but also reply to the original sender"
comment:8 by , 18 months ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
I originally reported this bug by email.
I would just like to add that this problem does not seem to occur with the osgeo-discuss list, where I also posted last week. Perhaps it is possible to compare the configuration of the osgeo-discuss and the incubator lists, and copy over the osgeo-discuss settings related to DKIM.