I have attached a snippet of the output of spamd -D that talks about URIDNSBL debug: plugin: loading Mail::SpamAssassin::Plugin::URIDNSBL from @INC debug: plugin: registered Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x8c75694) debug: plugin: loading Mail::SpamAssassin::Plugin::Hashcash from @INC debug: plugin: registered Mail::SpamAssassin::Plugin::Hashcash=HASH(0x8c35840) debug: plugin: loading Mail::SpamAssassin::Plugin::SPF from @INC debug: plugin: registered Mail::SpamAssassin::Plugin::SPF=HASH(0x8c36ef0) debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x8c75694) implements 'parse_config' debug: plugin: Mail::SpamAssassin::Plugin::Hashcash=HASH(0x8c35840) implements 'parse_config' debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x8c75694) inhibited further callbacks debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x8c75694) inhibited further callbacks debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x8c75694) inhibited further callbacks debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x8c75694) inhibited further callbacks debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x8c75694) inhibited further callbacks debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x8c75694) inhibited further callbacks debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x8c75694) inhibited further callbacks debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x8c75694) inhibited further callbacks debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x8c75694) inhibited further callbacks debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x8c75694) inhibited further callbacks debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x8c75694) inhibited further callbacks debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x8c75694) inhibited further callbacks debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x8c75694) inhibited further callbacks debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x8c75694) inhibited further callbacks debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x8c75694) inhibited further callbacks debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x8c75694) inhibited further callbacks debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x8c75694) inhibited further callbacks debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x8c75694) inhibited further callbacks debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x8c75694) inhibited further callbacks debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x8c75694) inhibited further callbacks debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x8c75694) inhibited further callbacks debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x8c75694) inhibited further callbacks debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x8c75694) inhibited further callbacks debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x8c75694) inhibited further callbacks debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x8c75694) inhibited further callbacks debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x8c75694) inhibited further callbacks debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x8c75694) inhibited further callbacks debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x8c75694) inhibited further callbacks debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x8c75694) inhibited further callbacks debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x8c75694) inhibited further callbacks debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x8c75694) inhibited further callbacks debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x8c75694) inhibited further callbacks Does that look correct? I don't notice any errors, but I wasn't sure about "inhibited further callbacks". --Mike Carlson [EMAIL PROTECTED] http://www.uselessthoughts.com
________________________________ From: Mike Carlson Sent: Wed 11/3/2004 2:15 PM To: Mathieu Nantel; users@spamassassin.apache.org Subject: RE: URIDNSBL I don't have any of those tests showing up in the tagged spam. I did notice a -2.4 for not passing through untrusted hosts. I am going to have to change that score I think. I dont think I am going to give spam credit for not being sent through a known spam host. --Mike Carlson [EMAIL PROTECTED] http://www.uselessthoughts.com ________________________________ From: Mathieu Nantel [mailto:[EMAIL PROTECTED] Sent: Wed 11/3/2004 1:55 PM To: users@spamassassin.apache.org Subject: Re: URIDNSBL Heh, that's easy: 99% of your spam will score on either of these tests: 5.0 URIBL_SBL Contains an URL listed in the SBL blocklist 5.0 URIBL_AB_SURBL Contains an URL listed in the AB SURBL blocklist 5.0 URIBL_JP_SURBL Contains an URL listed in the JP SURBL blocklist 5.0 URIBL_WS_SURBL Contains an URL listed in the WS SURBL blocklist 5.0 URIBL_OB_SURBL Contains an URL listed in the OB SURBL blocklist 5.0 URIBL_SC_SURBL Contains an URL listed in the SC SURBL blocklist (yes, my scoring is agressive) The more proper way of checking this is to run: spamd -D which will outputthis if you are loading URIDNSBL: debug: plugin: loading Mail::SpamAssassin::Plugin::URIDNSBL from @INC debug: plugin: registered Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x35ced0) On November 3, 2004 02:52 pm, Mike Carlson wrote: > How do I know if SA is using URIDNSBL? > > I am running SA 3.0 on FreeBSD with MimeDefang and now emails are scoring > very very low and some users are getting a ton of spam through. I want to > make use of URIDNSBL if I can, but I am not sure if it is working or not. > > --Mike Carlson > [EMAIL PROTECTED] > http://www.uselessthoughts.com -- Mathieu Nantel - Systems Manager Ecopia BioSciences Inc. (514) 336-2724 x434
