ISP Information pages

I have posted a ISP Information Page. Right now it contains links to Postmaster pages, Whitelist signup pages and FBL signup pages. I have some ideas on what information would be helpful to add, but would like to hear what types of info people would like to have easy access to.
What do you think I should add to the page?

Related Posts

Getting whitelisted by endusers

One of the best ways to ensure mail is delivered to a recipients inbox is to encourage the recipient to add the senders from: address to their address book. In cases where an ISP might otherwise bulk folder the email, they will instead put the email into the inbox.
Senders are changing their practices to get recipients to add from addresses to address books. There are a number of companies reminding users to add addresses on the webpage at the time of signup. Most emails have recommendations in each email. Recently, there have been multiple reports of companies who send specific email campaigns to encourage recipients to whitelist the sender.
Cool Email Idea: Customized Whitelisting Instructions from ReturnPath.
How & Why You Need to be Added to Your Recipient’s Address Book from VerticalResponse.
In addition to the direct benefit to the recipient that whitelists the individual sender, there are some hints that ISPs are looking at individual whitelisting as part of their internal sender reputation scoring.

Read More

When the script doesn't work

DJ asks in the comments of Friday’s post:

As Seth said, great reminder. For those that have great processes/channels in place, I’ve found incredible success. However, sometimes I’ve found my answer on Twitter (i.e., @godaddyguy). Also, there have been times where I’ve gone through the script (i.e., shaw.ca) and have never heard back. What then?

Read More

Personal Contacts at ISPs: Part 2

I’ve talked quite a bit recently about working with ISPs and personal contacts. Today I have an example of what not to do.
One of my ISP friends informed me that another blogger published correspondence from an individual at that ISP, including the individual’s full contact information. The correspondence wasn’t a big deal, the blogger was assigned an IP address by their ISP that was previously used by a spammer. The ISP had a block on the address and he was contacting them to get the block removed. It was totally a misunderstanding on the blogger’s part and the blogger removed the info when the ISP contacted him. Still, once something is out on the net, it’s out there forever.
Don’t do that. Really. When someone at an ISP helps you, don’t go publishing their information on a blog somewhere. They will find out, even if it’s just because their mailbox explodes or their phone starts ringing off the hook with multiple calls about an “emergency” situation. It hurts the person who helped you, who now has to deal with a major increase in volume and work load, and they’re never going to help you again.
This also hurts the rest of us, as ISP employees retreat farther and farther away from contact with senders. Even those of us who are careful with contact information may find it hard to get responses when others in the field are spreading info around.
I know some ISPs can be difficult to get any information from. That’s part of my reason for publishing the ISP information page was to help people find the right contact information. I think it’s extremely important for delivery professionals to understand that you don’t need a personal contact at an ISP to resolve most issues. What you do need is a deep understanding of SMTP, a smattering of knowledge about DNS and HTTP, a firm grasp of privacy issues and an understanding of the dynamics of email.

Read More