Hi all,
I have a weird one. This morning an AOL user posted to one of my lists. Normally this is no problem, since I have the list in question set to munge the From: of messages from problematic domains (AOL, Yahoo, etc). For some reason it didn't work this time. Naturally, I received bounce reports left and right, complaining about unauthenticated Email from AOL.
Did my server fail to retrieve the DMARC information for AOL for some transient reason, or could there be another problem? I have double checked that the list is set to munge the From: of such messages, but it didn't this time.
Thanks for any help,
Jayson
On 11/14/18 11:53 AM, Jayson Smith wrote:
Did my server fail to retrieve the DMARC information for AOL for some transient reason, or could there be another problem? I have double checked that the list is set to munge the From: of such messages, but it didn't this time.
What's in Mailman's vette and error logs? and what Mailman version is this?
Errors in retrieving DMARC policy should be logged in 'error'. Also, since Mailman 2.1.25, if the policy can't be retrieved, mitigations will be applied as if the policy were reject.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Hi,
The error in /var/lib/mailman/log/error is as follows:
Nov 14 10:24:29 2018 (1063) DNS lookup for dmarc_moderation_action for list (Redacted) not available
I recently upgraded a lot of packages on my Debian system. I compiled Mailman from source since Debian didn't have the version I wanted. Do I need to recompile and reinstall?
Thanks,
Jayson
On 11/14/2018 5:25 PM, Mark Sapiro wrote:
On 11/14/18 11:53 AM, Jayson Smith wrote:
Did my server fail to retrieve the DMARC information for AOL for some transient reason, or could there be another problem? I have double checked that the list is set to munge the From: of such messages, but it didn't this time.
What's in Mailman's vette and error logs? and what Mailman version is this?
Errors in retrieving DMARC policy should be logged in 'error'. Also, since Mailman 2.1.25, if the policy can't be retrieved, mitigations will be applied as if the policy were reject.
On 11/14/18 2:35 PM, Jayson Smith wrote:
Hi,
The error in /var/lib/mailman/log/error is as follows:
Nov 14 10:24:29 2018 (1063) DNS lookup for dmarc_moderation_action for list (Redacted) not available
That says Mailman couldn't import dns.resolver.
You need to have the dnspython package installed for Python. Get it from http://www.dnspython.org/ or https://pypi.python.org/pypi/dnspython/ or just do
pip install dnspython
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Hi,
That did the trick, thanks!
Jayson
On 11/14/2018 6:09 PM, Mark Sapiro wrote:
On 11/14/18 2:35 PM, Jayson Smith wrote:
Hi,
The error in /var/lib/mailman/log/error is as follows:
Nov 14 10:24:29 2018 (1063) DNS lookup for dmarc_moderation_action for list (Redacted) not available
That says Mailman couldn't import dns.resolver.
You need to have the dnspython package installed for Python. Get it from http://www.dnspython.org/ or https://pypi.python.org/pypi/dnspython/ or just do
pip install dnspython
participants (2)
-
Jayson Smith
-
Mark Sapiro