On Wednesday 20 December 2006 21:55, Sandy Drobic wrote:
> The problem is, if that address was earlier assigned to a dynamic dialin
> pool, you will still be blocked by blacklists that list this address space
> as dynamic. You may know it is static now, but the blacklists often don't
> care, and the server administrators who use the blacklists care even less.

Radius servers (dialup) usually have their own pool.

Regular dhcp (as found on dsl or cable modems) is a different animal.
My IP for instance is pseudo-static, I've had the same IP since dirt. 
I'm allowed up to 8 IPs on this cable modem, and I can but the Linux 
laptop up in it once a week and ALWAYS get the same IP. 

That's where the problem comes in.  Not so much with dial up, because those
customers never run mail servers or any other services anyway. 

I support 4 medium size companies with statics. Until 4 months ago when I 
started bitching really loudly about static reverses being indistinguishable 
from dynamic reverses one or two of these would would get listed in sorbs 
every month or two.  And it was always listed under dynamic IP, never under
any of the other spammer categories. (I do egress filtering, so even if they
get a worm its not going anywhere).

It just so happens that these clients are shuttling large engineering 
documents between branch offices and other companies, and can't wait while 
the ISPs mail server chokes on these large document, so they run their own 
mail servers.  

It took me (and a few other system maintainers around the state)  4 months of 
bitching to get their policy changed so that statics have the word "static" 
in the reverse.  One of my cohorts reported that his static was listed in 
sorbs as a dynamic IP AGAIN after this happened.  The truth is that sorbs
does no checking at all.  Its totally unreliable.  Blocking on dynamic IP is
collective punishment, universally condemned in every other area of society
except fighting spam it would seem.

The ISP still will not allow the subscriber to specify the reverse.  But 
that's another topic.


-- 
_____________________________________
John Andersen

Attachment: pgpffZaglpMTo.pgp
Description: PGP signature

Reply via email to