Changes to AOL FBL

In a blog post today, AOL announced they are changing the from address on their FBL emails from scomp@aol.net to fbl-no-reply at postmaster.aol.com. This change will take place on January 16th, 2017.
AOLlogoForBlog
While this may seem a minor change to announce so far in advance, it’s really not. Because AOL was the first FBL, there are many tool chains that have been kludged together to handle the messages. Many of these tool chains rely on “scomp” in the header to work.
This is as good a time as any to review your current FBL handling code. Are you handling FBL messages correctly? Is there anywhere in your code that does things based on scomp being in the header?
Actually, it’s a good time to take a step back and think about FBLs in general and what you should be doing with the mail. These aren’t just complaints, they are direct feedback from your recipients. Sure, they just have to hit a button, but it’s still feedback.
Do you listen to that feedback or just unsubscribe folks?
Do you pay attention to which campaigns, mailings and offers trigger higher levels of FBLs?
Do changes in FBL rates factor into your marketing strategy at all? Why not?
Do you even know what happens when a FBL email arrives at your sever? Are you sure?
All of these are useful questions to ask at any time. But now that some folks are having to touch the FBL code, maybe it’s a time to develop a strategy for FBL processing. Use that data to inform and improve your marketing.
 
 

Related Posts

New AOL Postmaster Pages

AOL has updated their Postmaster pages with a new design and new resources for senders who are sending to AOL.  If you are sending to AOL, use the updated site to sign up for the feedback loop, request whitelisting, open a trouble ticket, or learn about the AOL error codes and bulk sending best practices.
AOL Postmaster Pages

Read More

New FBL information

A couple new bits of information for folks interested in participating in feedback loops.
If you’re an ESP, you’ll want to sign up for the two new FBLs that were released this month. XS4ALL and Telenor are now offering complaint feeds to senders.
If you’re a mail recipient and want the ability to report spam, try the new browser/MUA plugins for reporting spam released by the French anti-spam grup Signal Spam
These browser plugins allow recipients to report spam directly from a button in the browser. Signal Spam reports:
The button is working for the biggest webmails around, such as yahoo!, SFR, gmail, outlook, AOL, laposte, free, and is downloadable for Chrome, Safari and Firefox with this links :
Chrome
Safari
Firefox
These plugins are currently in beta, but should be released by the end of 2016.
For those folks who use our ISP information page, I haven’t yet added Telenor and XS4ALL to the pages of available FBLs. Part of that is because we’re looking at options to improve data presentation and ease of maintenance. The perl script that magically generated the summary page from other pages was great, until it hid itself on some VM somewhere and can’t be found. There are other things we want to maintain as public resources, so we’re looking into options. (wikimedia was one of our early attempts… it didn’t do what we needed). Anyone have a public KB or wiki package they particularly like?

Read More

AOL broken (again)

AOLlogoForBlogI am, apparently, still one of the top hits when you Google for AOL. When things break at AOL, this means I get lots of contacts, comments and even phone calls from people looking for help.
I’m really not AOL support. (Really. I’m not. If you’re an AOL user I can’t help you log into your account. Please don’t call. Please don’t ask. Contact AOL directly.)
BUT! So many AOL users thinking I am means I learn about AOL problems fairly early in the cycle. As of this morning I’m getting a lot of reports that AOL is broken. I tried logging into my account and got the following:
AOLErrorforBlog
On the delivery end mail is still being accepted. I can send mail to that particular account, even though I can’t log into it. But, senders may see lower engagement from AOL users until the issue is resolved.

Read More