-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Jeff Chan writes: >On Monday, March 29, 2004, 5:36:02 PM, Justin Mason wrote: >> Kai writes: >>> Justin: could you write a 5-liner saying what the final version of the >>> module does, and in what order? > >> Sure, maybe when I get some free time ;) > >> In the meantime, the POD docs in Mail::SpamAssassin::Plugin::URIBL >> should help. > >Pardon my noobness, but can you provide a URL? http://spamassassin.org/full/3.0.x/dist/lib/Mail/SpamAssassin/Plugin/URIDNSBL.pm >> My take is to cut off at the registrar-registered portion: e.g. >> "foo.co.uk", "foo.biz" etc., and use stringent timeouts. The >> scanning will always kill any pending lookups 2 seconds after >> the normal DNSBL lookups complete. > >This extraction of domains sounds important and interesting. >Do the docs or source code include how this was done? It's >not immediately obvious to me how one can programmatically >determine the registered part of domains. It's pretty simple -- we have a list of TLDs that use 3-level domains (like .co.uk) and all others are assumed to be 2-level (like .com). Then we cut off at the level below the TLD. That's done by the function Mail::SpamAssassin::Util::uri_to_domain() . There are a couple of exceptions we don't deal with: - dyndns.org-type sites. I think the operators of those will be quite stringently antispam if it arises, given how quickly they've rolled out SPF! - www.geocities.com-type sites. Impossible to do URIBL lookups there anyway, since all hosts share the same As and NSes, so we're reliant on them exercising some abuse control. The SBL will list abusers anyway I think -- wonder if they've listed terra.es yet? But I don't think those exceptions will cause trouble. PS: I was wrong -- I said it didn't limit how many lookups it started. In fact it does -- it'll use a random selection of 'uridnsbl_max_domains' (default: 20) from all the URIs in the message. - --j. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Exmh CVS iD8DBQFAaN1CQTcbUG5Y7woRAtEQAJ9KnYW2dTCWuCIUtT9qYUTngiNaVgCg2FLf E2FdtCVuHhIZRkhLkMstDNI= =5tlF -----END PGP SIGNATURE-----
