-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, March 19, 2003, Johannes Posel wrote...
>> And what is that supposed to achieve? And where does the checking occur. > Resolving the IP address from the host wanting to deliver the mail. > In your case this would be "66.228.134.123", which resolves fine[1] Right... but it's not DSL... and what happens with addresses that don't reverse? The spam filters would be useless. >> I think doing that kind of filtering is a little silly when it >> comes to spam. I get so much spam daily that has faked host details >> for the first 2 > You cannot fake your IP address. No... but you can insert extra header lines... and that was what I was talking about... What part does the filter pick up on, the first line to report a receive, or the last one. >> received lines that this kind of checking would be pointless. Also >> check > It's not about checking headers at all. The rejection takes place > even before the client send his EHLO greeting. Ahh... I see... I thought you were talking about a client side filter. That is of course in-effective when the mail is being received from another mail server. Which is normally the case in most situations as spammers fire emails through open relays. Of course, if people knew how to set things up properly, and allow relaying from authenticated hosts, or trusted addresses only, things would be a lot easier. - -- Jonathan Angliss ([EMAIL PROTECTED]) -----BEGIN PGP SIGNATURE----- iQA/AwUBPnibYiuD6BT4/R9zEQLxZACgmdugiqjkgH23HeNjugldC/Z0e9cAoJxU XcRfxYMa8Av03QNlW5H9Skwn =e2fx -----END PGP SIGNATURE----- ________________________________________________ Current version is 1.62 | "Using TBUDL" information: http://www.silverstones.com/thebat/TBUDLInfo.html
