AOL, AOL, AOL - they always do things a bit differently. I can't fully
blame them as they probably are still the #1 target of spammers.
As others have written, the most important information is in the outgoing
SMTP logs so you can see what AOL said, if anything, about why they are
refusing the ma
On Sun, Nov 23, 2014 at 04:54:09PM -0700, David Dodell wrote:
> Hi, I know from past experience that the OS X version of Mailman is met with
> some contempt because of what Apple did with it .. but I have it working well
> for several years on a 10.7.5 Lion Server, and it has been very stable.
N
This is why it's important to keep server configurations in a
configuration management system, like Chef, Puppet, cfengine, Ansible,
Salt Stack, etc. When set up right, the configuration management
will put back any unwanted OS changes, or at the very least tell
after an upgrade what files no long
I've converted a list to Mailman, and as I posted previously, I
decided to use "wrapped" messages to keep AOL's hairtrigger spam
filters from discarding incoming messages from AOL users.
Now I'm getting complaints from Outlook 2007 and Squirrelmail
users that the messages from Mailman show up as t
On Sat, Oct 18, 2014 at 11:03:11AM -0700, Mark Sapiro wrote:
...
> I have a somewhat different issue. I am using dmarc_moderation_action =
> Munge From, and when an AOL user posts to the list, the list message
> sent back to the user bounces with "521 5.2.1 : AOL will not accept
> delivery of this
I'm setting up a new Mailman server to replace an elderly MajorDomo
that isn't DMARC-compatible.
I set up the list to use the list's address as the From address and to
put the sender's address in Reply-To:. I started playing around with a
test list - in no time at all, AOL began bouncing all my m
