Changes at AOL Postmaster desk

The recent layoffs at AOL did affect the AOL Postmaster desk, and information I have received is that there was significant loss. As a result of the staff decrease, some changes have been made to the whitelisting and FBL processes. In order for a FBL to be approved it must meet the new FBL guidelines. In a nutshell, anyone wanting to get a FBL from AOL must meet ONE of the following criteria.

  • The reverse DNS for each IP shares the FBL domain.
  • At least one authoritative nameserver for each IP shares the FBL email domain.
  • The IP WHOIS information for each IP shares the FBL email domain in common. The domain may appear in any of the listed email addresses.
  • The ASN WHOIS information for each IP shares the FBL email domain in common. The domain may appear in any of the listed email addresses.

These are not exactly new policies, some version of them have always been in place. The intent of the checks is to make sure that people only get the FBLs for IP ranges that belong to them. In the past, the checks were done by hand by the folks on the postmaster desk. With the massive decrease in staff, these checks have been automated.
A few people have complained about the new checks and the fact that their applications were denied. The good news is there are escalation paths and ways to get decision makers to take a look at the application. Also, the process is being tweaked so that everyone who should get a FBL does actually get one.

Related Posts

Do it yourself mail systems

Through my position here at Word to the Wise I’ve interacted with dozens of companies over the years. Some companies outsource the mechanics of email sending to email service providers, others buy a software or MTA solution from one of the many vendors out there. For both these groups delivery problems are usually issues with permission or user expectations. Technically there are few problems with sending, bounce handling, unsubscriptions and rate limiting. The commercial software, either as created by an ESP or a vendor, typically does these things well.
The last group, those who use a home built system, are a whole different story. They often do no bounce processing relying on the underlying mail transport agent (typically qmail) to do all that work. The problem is that a general mail transport agent handles bounces for a particular email send, but does not have any functionality to handle future emails to addresses that bounce. Consequently the list does not get bounce handled, dead addresses pile up and their delivery rates plummet.
A few weeks ago Derek talked about senders using homegrown email systems and the pitfalls therein. He has a good list of things companies should think of before deciding a home grown system is right for them.

Read More

MAAWG: Sender Best Practices

The MAAWG Sender Subcommittee has published a Sender Best Current Practices document.
This document details what the current best practices in the sending industry are. Summarized the document says:

Read More

ISPs like boxes of meat

On the heels of JDs post about building relationships with ISPs, many of our Abacus customers and our ISP contacts have been commenting that boxes of meat are always welcome.
Please, remember to send them boxes of meat.
Meat may not get your email delivered, but it will make the ISPs remember you fondly.

Read More