At 09:13 2006-06-06 -0400, Eric Wood wrote:
My server was falsed listed on just 1 RBL whereas the every other RBL did
list me. I had a few people I could not send to until I removed my server.
I presume you meant to say "every other RBL did [NOT] list me."
So in my mind, there are two major problems with RBLs:
1. An RBL gets a new entry but does not bother to consult with it's peer RBL
lists before listing it.
Peer DNSBLs? Are you smoking something?
Different DNSBLs have different criteria for listing. Further, if any
given DNSBLs wouldn't list until other DNSBLs listed, you'd have a
deadlock, as nobody would list anything because nobody else has yet either
- and if someone DID, it'd be because they're not following some joke of a
peer protocol.
It's like deferring your right-of-way. "You go." "No, you go." "Really,
YOU go." "You go - I insist." "Alright already, just go." "Hey jackass,
find your gas pedal and go." <rev, crash!>
Or are you suggesting that DNSBLs employ some pre-DNSBL list that could be
used by other DNSBLs? Again - different DNSBLs have different criteria for
listing.
Why not rag on your friends' mailhost for not requiring a validating DNSBL
listing? It's up to the user of the data to use it in a sensible fashion.
2. A mail server should not reject email if 95% of the RBLs says there's not
a problem. In other words, don't just go by 1 RBL says.
Why would a mail server have to consult with 20 DNSBLs? PERHAPS people
should be using DNSBLs with more RELIABLE listing procedures?
I can understand where you're coming from WRT to irritation with DNSBLs
listing you and thus interrupting your ability to send to some people
(whose services elect to use those DNSBLs). AOL has some braindead stuff
in place which periodically whacks discussion list traffic on a site I
admin for (it amounts to them using user input from AOLers who think a SPAM
button is an appropriate way to uns*bscribe from a list). I even have a
client who must use my servers to relay all their outbound mail because
they obtain web hosting services through a hosting outfit that some years
ago had a spammer client and as a result got their entire netblock
blacklisted, which affects every site hosted on that network (it isn't a
huge netblock by any means, but still sizeable - a /18) -- even though none
of them are using the specific IPs which had been used by the spammer. The
client in question is relaying replies to classified advertising, and thus
want to get information to the poster, not have it rejected because of an
ancient blacklisting.
---
Sean B. Straw / Professional Software Engineering
Procmail disclaimer: <http://www.professional.org/procmail/disclaimer.html>
Please DO NOT carbon me on list replies. I'll get my copy from the list.
____________________________________________________________
procmail mailing list Procmail homepage: http://www.procmail.org/
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail