For When You Can't Have The Real Thing
[ start | index | login ]
start > Getting Delisted From SORBES

Getting Delisted From SORBES

Created by dave. Last edited by dave, 7 years and 15 days ago. Viewed 3,236 times. #1
[edit] [rdf]
labels
attachments
(2 December 2011)

So one spam flood later (and I love cleaning 80K+ messages out of a sendmail queue, thank you very much) and one of my mail relays is blacklisted. So its time to trot around to the black holes and try to get delisted.

Dealing with SORBS to get an IP delisted from their spammer blacklist was an interesting experience.

Me: (goes to website, clicks the delist IP buttons)

SORBS: you must either be using the IP you are trying to delist, or log in to an account.

Me: (Creates account, clicks the delist IP buttons)

SORBS: you must either be using the IP you are trying to delist, or have it associated with your account in the network manager.

Me: (Brings up network manager)

SORBS: you cannot associate a network with your account if your details do not match the whois info for that network.

Me: (Clicks through the enter-a-ticket, then explains:) This IP is geographically remote to me and relays mail for my customers who can't send mail directly. One customer had an integrity issue and dumped a ton of spam on this system. The customer has been blocked and is being cleaned; all pending spam has been removed. Please delist me.

SORBS Robot: Marking your request as rejected because this IP sent a really large amount of spam, so we're gonna need an explanation of what happened indicating you've fixed it.

Me: This IP is geographically remote to me and relays mail for my customers who can't send mail directly. One customer had an integrity issue and dumped a ton of spam on this system. The customer has been blocked and is being cleaned; all pending spam has been removed. Please delist me.

SORBS Tech (24 hours later): OK, I've delisted you because there have not been any more occurrences in the last 24 hours. However, to help you figure out what happened, please have this header snippet that explains where the spam was coming from.

Obviously nobody reads any of the extra text fields in their tickets, even the ones they ask for. I explained the problem twice, and the handling tech still managed to ignore the information and provided me with the header snippet (which duplicated the identifying string I put into both my explanations) to help me.

Now maybe they deal with a high number of people who are more just delist me and I'll clean things later, but I thought my message exhibited enough clue that they'd understand I knew what I was doing.

no comments | post comment
This is a collection of techical information, much of it learned the hard way. Consider it a lab book or a /info directory. I doubt much of it will be of use to anyone else.

Useful:


snipsnap.org | Copyright 2000-2002 Matthias L. Jugel and Stephan J. Schmidt