-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, March 20, 2003, Johannes Posel wrote...
>> The RBL lists would block 192.168.0.0/24 instead of just the later >> half of the range. > I'd see this analogy, with 192.168.* being dial-up and 10.0.* beign > fixed-IP customers. Then you wouldn't have an issue with them blocking the dialup blocks. My example shows that an RBL could block the ISDN block as well as the dialup. >> That's an odd stance. Last time I checked (and as you stated), AOL >> bounce mail to their own SMTP servers. > No, I mean like this: A mail server gets an incoming connection from > an IP which belongs to AOL. It refuses this connection except if > this IP beongs to the listed AOL MXes. See what I mean? Yes I know... but last time I checked, AOL didn't allow outbound connections on port 25, and were bounced through their own SMTP servers. This'd result in a firewall rule that didn't do anything as the connections could never reach you as per AOL. But I could be wrong. >> an example) for example. It just changes your name when somebody does >> a lookup. If you're blocking by IP range (which is what RBLs do), >> names don't mean a thing. > Which RBL are we talking about? RBLs store IP addresses, not names. Your mail server looks up addresses based on IP address... if it is listed, then it gets blocked. The problem is, some RBLs blacklist whole segments without much research... as Marck found out. Talking of which *grins*... I think this thread could be moved to TBOT now before it gets flogged ;) - -- Jonathan Angliss ([EMAIL PROTECTED]) -----BEGIN PGP SIGNATURE----- iQA/AwUBPnpS4yuD6BT4/R9zEQKnngCfVGaoDJGlwm+1dhrdsHsntSwgeSAAn3VK lppOBzhcghXqeliBANIn7piR =U/df -----END PGP SIGNATURE----- ________________________________________________ Current version is 1.62 | "Using TBUDL" information: http://www.silverstones.com/thebat/TBUDLInfo.html
