James Gray wrote:
On Wed, 26 Mar 2008 03:31:34 am mouss wrote:
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.
Meh - call me a troll. I'm posting here (personally, not as part of work) as
a long-time SpamAssassin and mail server user/administrator and have no need
to prove anything about my work systems.
I am not asking you to prove anything about your work systems or about
yourself. you have accused sorbs but provided nothing to support your
accusation.
Note that I am not affiliated with sorbs.
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
Yes - that's one of my personal domains, not the work one. Yes the TTL's are
short because I recently reorganised my DNS server and added some new slaves.
I just haven't got around to changing the TTL's. TTL's are fixed now, along
with the bum-steer regarding the address I got from the guys handling my
secondary MX. Grrr.
Thanks for the heads up.
The real issue is that your MX points to a CNAME. This is why I
submitted the domain to rfci. fix this and get delisted (on rfci, of
course).
