Contacting an ISP that doesn't have a postmaster page

How do you contact an ISP about a block that doesn’t have a postmaster page? While there’s no one answer, I do have some suggestions.
Start by contacting the postmaster@ or abuse@ addresses. For smaller ISPs, the same people handling outbound abuse are the people handling inbound filtering.
When you contact them have the following:

  • What IPs you’re sending from.
  • What the rejection message is (or if it’s not a rejection message, that the mail is undelivered or going to bulk).
  • The recipient you’re sending to.
  • The type of message.

Keep the message short and sweet. Do not send 5 paragraphs about your business model. I’ve been on the receiving end of the 5 paragraphs of your business model, as have so many of the ISPs that it’s turned into a joke among delivery: “Let me tell you about my business model…” They don’t care, they just want to know what the problem.
The message should have 3 (short!) sections.

  1. State the problem: “Mail I am sending from IP address is consistently going to the bulk folder. These are [sales receipts / tickets / bills / newsletters].”
  2. State what you’ve done to fix it:”We have changed our delivery in X fashion” (limited connections, improved data hygiene, stopped mailing very old addresses, fired the idiot sales guy who decided spamming was a good idea, whatever it is).
  3. Ask for a resolution: We’d like to know what you are seeing from our mail server that’s causing you to think this mail is unwanted by your recipients. I’ve attached a copy of the blocked / bulked message.

You MUST include the sending IP address in all correspondence. I can’t emphasize this enough. Without the IP, no one can help you. Without the IP they may even not bother to answer you. Without the IP the only response you will get it “what’s the IP?”
Also, don’t try and call. I know a lot of people prefer using phone to email, but in this case, use email. Calls are mostly useless.
The biggest issue is that getting an IP address over the phone is horrible. But when the IP is in an email, it’s a simple cut and paste into the internal tools. But there are also communication and documentation issues. Some ISPs like to have records of discussions about blocking and unblocking. On the communication level, when things are written down then no one is relying on faulty memories or hastily written notes about what needs to happen.
At smaller ISPs or even some small businesses, you can ask your recipients to talk to their support desk or admin.If the ISPs have customers telling them the email is wanted they’re much more likely to make filtering adjustments.

Related Posts

Delivery emergencies and the holidays

There is a lot of contention between ISPs and senders at the best of times. As we move into the holiday season, retailers are increasing their email marketing, sometimes quite significantly. This causes more delivery issues as recipients and MTAs react to the increased volume.
At many non retail companies, however, the pace of work slows down. There are distractions and office parties and people taking long lunches to finish their holiday shopping. Non-critical departments are not staffed for official holidays like Thanksgiving and Christmas Day.
This means that delivery issues may not be responded to as quickly as senders might like. Just this morning I got a call from someone who wants his delivery issues to be fixed by tomorrow. I’m sorry, even if I were to treat this as an emergency, there is work and investigation that needs to be done at the ISP end, and they’re not necessarily going to have a staffed delivery desk on Thanksgiving day. And even if they do have a staffed desk, it’s possible the staff won’t be focused and issues won’t be handled as fast as they might otherwise be.
I’d love to help, but there’s a limit to what I can do. Filtering decisions are made by the ISP, or their filter vendor, and sometimes they don’t happen as fast as we’d like. It’s frustrating for senders to have to deal with, but these are the realities of email delivery.

Read More

What is a dot-zero listing?

320px-HITRON_MH-65C_Fires_warning_shots

Some email blacklists focus solely on allowing their users to block mail from problematic sources. Others aim to reduce the amount of bad mail sent and prefer senders clean up their practices, rather than just blocking them wholesale. The Spamhaus SBL is one of the second type, using listings both to block mail permanently from irredeemable spammers and as short term encouragement for a sender to fix their practices.
All a blacklists infrastructure – and the infrastructure of related companies, such as reputation monitoring services – is based on identifying senders by their IP addresses and recording their misbehaviour as records associated with those IP addresses. For example, one test entry for the SBL is the IP address 192.203.178.107, and the associated record is SBL230. Because of that they tend not to have a good way to deal with entities that aren’t associated with an IP address range.
Sometimes a blacklist operator would like put a sender on notice that the mail they’re emitting is a problem, and that they should take steps to fix that, but they don’t want to actually block that senders mail immediately. How to do that, within the constraints of the IP address based blacklist infrastructure?
IP addresses are assigned to users in contiguous blocks and there’s always a few wasted, as you can’t use the first or last addresses in that range (for technical / historical reasons). Our main network consists of 128 IP addresses, 184.105.179.128 to 184.105.179.255, but we can’t put servers on 184.105.179.128 (as it’s our router) or 184.105.179.255 (as it’s the “broadcast address” for our subnet).
So if Spamhaus wanted to warn us that we were in danger of having our mail blocked, they could fire a shot across our bow without risk of blocking any mail right now by listing the first address in our subnet – 184.105.179.128 – knowing that we don’t have a server running on that address.
For any organization with more than 128 IP addresses – which includes pretty much all ISPs and ESPs – IP addresses are assigned such that the first IP address in the range ends in a zero, so that warning listing will be for an address “x.y.z.0” – it’s a dot-zero listing.

Read More

ISP Relationships

Delivra has a new whitepaper written by Ken Magill talking about the value (or lack thereof) of relationships with ISPs. In Ken’s understated way, he calls baloney on ESPs that claim they have great delivery because they have good relationships with ISPs.
He’s right.
I get a lot of calls from potential clients and some calls from current clients asking me if I can contact an ISP on their behalf and “tell the ISP we’re really not a spammer”. My normal answer is that I can, but that there isn’t a place in the spam filtering process for “sender has hired Laura and she says they’re not a spammer.” I mean, it would be totally awesome if that was the case. But it’s not. It’s even the case where I’m close friends with folks inside the ISPs.
I’m pretty sure I’ve told the story before about being at a party with one of the Hotmail ISP folks. There was a sender that had hired me to deal with some Hotmail issues and I’d been working with Barry H. (name changed, and he’s not at Hotmail any more) to resolve it. During the course of the party, we started talking shop. Barry told me that he was sure that my client was sending opt-in mail, but that his users were not reacting well for it. He also told me there was no way he could override the filters because there wasn’t really a place for him to interfere in the filtering.
Even when folks inside the ISPs were willing and able to help me, they usually wouldn’t do so just because I asked. They might look at a sender on my request, but they wouldn’t adjust filters unless the sender met their standards.
These days? ISPs are cutting their non-income producing departments to the bone, and “sender services” is high up the list of departments to cut. Most of the folks I know have moved on from the ISP to the ESP side. Ken mentions one ISP rep that is now working for a sender. I actually know of 3, and those are just employees from the top few ISPs who are now at fairly major ESPs. I’m sure there are a lot more than that.
The reality is, you can have the best relationships in the world with ISPs, but that won’t get bad mail into the inbox. Filters don’t work that way anymore. That doesn’t mean relationships are useless, though. Having relationships at ISPs can get information that can shorten the process of fixing the issue. If an ISP says “you are blocked because you’re hitting spam traps” then we do data hygiene. If the ISP says “you’re sending mail linking to a blocked website” then we stop linking to that website.
I have a very minor quibble with one thing Ken said, though. He says “no one has a relationship with Spamhaus volunteer, they’re all anonymous.” This isn’t exactly true. Spamhaus volunteers do reveal themselves. Some of them go around openly at MAAWG with nametags and affiliations. A couple of them are colleagues from my early MAPS days. Other do keep their identities secret, but will reveal them to people they trust to keep those identities secret. Or who they think have already figured it out. There was one drunken evening at MAAWG where the nice gentleman I was joking with leaned over and says “You know I am elided from Spamhaus, right?” Uh. No? I didn’t. I do now!
But even though I have the semi-mythical personal relationship with folks from Spamhaus, it doesn’t mean my clients get preferential treatment. My clients get good advice, because I know what Spamhaus is looking for and can translate their requirements into solid action steps for the client to perform. But I can think of half a dozen ESP delivery folks that have the same sorts of relationships with Spamhaus volunteers.
Overall, relationships are valuable, but they are not sufficient to fix inbox delivery problems.

Read More