AOL users get “unsubscribed” from our listservs

AOL logos
click to enlarge

Half a dozen AOL users got “unsubscribed” from our intellectual property listservs today, which follows a dozen AOL users that got “unsubscribed” yesterday.  In this blog article I explain why this happened. 

Our listserv server (called “Mailman“) tries to be respectful:

    • Our server provides an “unsubscribe” link at the bottom of every listserv posting, and if the recipient clicks on that link, they really do get unsubscribed, instantly.
    • If somebody flags a listserv posting as supposedly being spam, our server unsubscribes that person.
    • If an email address stops working, then after several failed attempts, our server unsubscribes that person.

This is exactly what a listserv server ought to do, and that is what our server does.

There are several things that an email sender can do to signal that the sender’s outbound email is not spam, including:

    • DKIM or DomainKeys Identified Mail,
    • SPF or Sender Policy Framework,
    • PTR or Pointer,  and
    • DMARC or Domain-based Message Authentication, Reporting and Conformance.

Our listserv server does these four things, and it does them correctly.

One way to get into trouble is to end up on somebody’s spam black-hole list.  We check our reputation on black-hole lists frequently, and our listserv server at IP address 159.198.40.90 does not end up on anybody’s spam black-hole list.  (The sole exception is a list called UCEPROTECTL3.  If you are on the UCEPROTECTL3 black-hole list, this is not because you sent any spam.  It is because somebody else with a “nearby” IP address, differing in the last octet, sent some spam.  Our server thus sometimes ends up on the UCEPROTECTL3 black-hole list due to bad behavior by somebody at some other IP address.)

Each member of a listserv has, necessarily, selected some email service provider (ESP) for their email.  There are at least two harms that follow if that member’s ESP wrongly tags our listserv postings as spam:

    • the member does not receive the postings, and
    • the bounce messages trick our server into thinking that the member does not want to receive any more postings, and so our server “unsubscribes” the member from the listserv.
  • Which brings us to AOL’s misbehavior in recent weeks.  In recent weeks, AOL consistently bounces our listserv postings to its customers with this SMTP error message:

SMTP error from remote mail server after end of data: 554 Message not allowed – [PH01] Email not accepted for policy reasons. Please visit https://senders.yahooinc.com/error-codes

You can look up the “554” error code at the web page that they invite us to visit.  Quoted here is their explanation of “554”:

    • You’re trying to send a message to an invalid email address.  (This can’t be it, unless somehow every “aol” address in our membership became “invalid” simultaneously.)
    • Your message failed authentication checks against your sending domain’s DMARC or DKIM policy.  (This can’t be it, because our DMARC and DKIM policies are correct.)
    • The message contains characteristics that Yahoo won’t accept for policy reasons.
    • Other suspicious behavior which leads Yahoo to issue a permanent rejection for your SMTP connection.
    • Your IP is listed by Spamhaus.  Please check with https://www.spamhaus.org.  (No, our IP 159.198.40.90 is not listed by Spamhaus.)

We carefully monitor traffic into and out of our listserv server.  If, for example, our server had been compromised by malware and was being used for some bad purpose, we would eventually figure this out.  We try very hard to secure our listserv server:

    • We methodically apply software patches, for example the recent patches for PHP and NGINX.
    • We avoid using that server for anything else, such as hosting web sites, so as to mimize its attack surface.
    • We run periodic virus scans on the server.
    • We methodically install updates on the operating system software (Linux) and the management system (Cpanel).

So as far as I can see, AOL is just flatly wrong to be bouncing our listserv postings with this “554” error code.

Yahoo sender feedback
click to enlarge

AOL used to be owned by Yahoo, and we have an account with Yahoo to let us know if anybody flags any of our email as spam.  At right you can see that in the past 180 days, our listserv server has sent 148 emails to Yahoo (or AOL).  During those 180 days, our spam complaint rate was zero.  (We subscribe to similar postmaster tools with Gmail and Microsoft, and with them, our spam complaint rate is also zero.)

But the plain fact is that in recent weeks, AOL has been consistently bouncing every listserv posting from our server.  This tricks our Mailman server into “unsubscribing” every AOL customer from all of our listservs.

What can you do if you are an AOL user and you got “unsubscribed”, and you don’t want to be “unsubscribed”?

It won’t do any good to ask me to fix it.  We’re already doing everything right.  There is nothing more that we could do, in addition to what we already do, to try to keep these bad things from happening.

You could subscribe again at our listservs information page.  But unless your service provider AOL were to change its bad behavior, you will just get unsubscribed again, in this automatic way.

Probably what you need to do is get on the phone with AOL and tell them to stop blocking the listserv postings from 159.198.40.90.

I welcome comments below.

Leave a Reply

Your email address will not be published. Required fields are marked *