Hi,
I'd say the domain does need to be fixed first. I recently encountered a
mail server (not AOL) which refused to accept mail from my domain
because I didn't have an MX record.
As far as I can tell, it is not the individual AOL users who need to
request whitelisting, but rather, the server sending mail on behalf of
the list. Remember, all the AOL users are doing is possibly sending some
messages if they participate on the list, and they're also receiving
list traffic. Since the issue is with AOL users receiving mail, not
sending mail, it's the mail server that needs to be whitelisted, but
before doing that I'd make sure all the DNS stuff is in order.
Jayson
On 12/4/2015 5:06 PM, Woody Mon via Mailman-Users wrote:
Thank you for everyone's ideas and recommends.
I've checked and every list subscriber has the
As Mark suggested trying, I'll change "from_is_list" to "Munge From" to see if that has
any effect. And if not will try "Wrap Message".
Note that almost all list subscribers are set to receive Digests, so hoping
this doesn't mess with the format of the digests any (the list is text only, no
html or attachments)..
As Mark related, I suspect the issue is DNS related, and AOL is just finally
cracking down on mail sent from this particular list server.
A free web based DNS checker reports the following for the listserver domain:
1. FAIL - SOA record check. "No nameservers provided an SOA record for the
zone".
2. FAIL - MX records check. "No MX records exist within the zone. This is legal, but
if you want to receive E-mail on this domain, you should have MX record(s)."
3. PTR record for the domain "Error: Invalid IP address"
I'm not privy to the details but I suspect the list server runs within a
virtual host environment.
>From the header of a list digest email I received yesterday
-----
Return-Path: listname-boun...@lsubdomain.domain1.org
X-RC-FROM: <listn...@lsubdomain.domain1.org>
Received: from localhost ([127.0.0.1]:obfuscated-port#
helo=hostname.domain2.org)
by hostname.domain2.org with esmtp (Exim 4.85)
(envelope-from <listn...@lsubdomain.domain1.org>)
id obfuscated date & timestamp
X-AntiAbuse: Primary Hostname - hostname.domain2.org
X-AntiAbuse: Original Domain - domain3.org
X-AntiAbuse: Sender Address Domain - subdomain.domain1.org
From: listname-requ...@subdomain.domain1.org
Subject: Listname Digest, Vol ##, Issue ###
To: listn...@subdomain.domain1.org
Reply-To: listn...@subdomain.domain1.org
-------
It appears the listserver domain (domain1) runs on the domain2.org host and
which is responsible for sending mail for domain1. Whereas the 'abuse' domain
(domain3) is the domain name of the parent organization which hosts domain2,
which the domain1 listserver runs upon.
I'm considering sending a direct email to all the list subscribers with AOL
addresses, recommending they either contact AOL to request a whitelist solution
or to send us an alternative (freemail) email address which we'll change their
list subscription to.
Besides the list provider repairing their DNS configuration, is the above a
recommended solution?
If I was a network administrator I likely could phrase all this in better
terms. ;-)
------------------------------------------------------
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
https://mail.python.org/mailman/options/mailman-users/jaybird%40bluegrasspals.com
------------------------------------------------------
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
