James Gray wrote:
Why are rules that look up against this list still in the base of
SpamAssassin?? The SORBS dynamic list is so poorly maintained that
it's practically useless and if you are an unfortunate who ends up
incorrectly listed in it, good luck getting off it! Case at hand, the
company I work for purchased a /19 address block directly from APNIC
before anyone else had it (IOW, we were the first users of that block).
We now have both our external mail IP's listed in SORBS_DUL despite
the fact the /24 they belong to, and the /24's on either side have
NEVER been part of a dynamic pool. SORBS refuse to delist them as our
MX records are different to these outgoing mail servers! FFS - we run
managed services for a number of ISP's why the hell would we *want* to
munge all our inbound and outbound mail through the same IP's?!?
Seriously folks, can we make SORBS_DUL optional and not "on by
default" in the general distribution?
If you have a complaint, provide _evidence_. otherwise, it goes to
/dev/troll0.
while you are at it, fix your DNS. your domain has been succesfully
submitted to rfci (boguxms):
http://www.rfc-ignorant.org/tools/lookup.php?domain=gray.net.au
once you fix your MX, increase the TTL in your NS and your MX. small TTL
is indicative of fast flux. it's certainly conformant, but it's
suspicious, which is enough to get you on the dark side of the moon.
