Re: DNS tests getting aborted
> Actually my DNS is working fine. Other DNS rulesets are hitting fine > like RCVD_IN_BL_SPAMCOP_NET > > In order to get URI tests working I have to put rbl_timeout 40 in my > local.cf > The default rbl_timeout of 15 is too less, but that is strange. It had > been working with my older SA 3.1.5 though See http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5511
Re: DNS tests getting aborted
On Mon, 2007-06-11 at 09:34 -0400, Theo Van Dinter wrote: > On Mon, Jun 11, 2007 at 06:48:04PM +0530, ram wrote: > > [8454] dbg: dns: success for 0 of 29 queries > > [8454] dbg: dns: timeout for after 10 seconds > > > > but dig on the machine is working fine without any issues. > > my user_prefs file shows dns_available yes > > and I have Net::DNS > > Is the first DNS server listed in resolv.conf functional? Net::DNS isn't > quite as resilient as bind-tools, unfortunately. ie: dig may return fine if > it's skipping other name servers, while Net::DNS stops at the first one. > Actually my DNS is working fine. Other DNS rulesets are hitting fine like RCVD_IN_BL_SPAMCOP_NET In order to get URI tests working I have to put rbl_timeout 40 in my local.cf The default rbl_timeout of 15 is too less, but that is strange. It had been working with my older SA 3.1.5 though Among these RBL tests can I give higher priority can I say do URIDNSBL_1 first and if found short circuit else perform other RBLs Thanks Ram
Re: DNS tests getting aborted
On Mon, Jun 11, 2007 at 04:43:28PM +0200, arni wrote: > >Please do not reply to this email address as it has been automatically > >generated, but email any queries to: [EMAIL PROTECTED] > are you realising, that you're "spamming" a mailinglist here? fyi, I sent a mail to their support addr (above) asking that they fix their system asap. if it continues, we'll have to unsubscribe the user in question. -- Randomly Selected Tagline: "Now please floppy from your first drive and insert the boot floppy." - Red Hat Installation for Linux pgpBwngOhA296.pgp Description: PGP signature
Re: DNS tests getting aborted
[EMAIL PROTECTED] schrieb: Server .116 The email attached has been identified by one of our team as legitimate but unfortunately was incorrectly tagged as SPAM. The email address has been whitelisted to ensure this will not happen again and we are currently looking into the reasons why this happened. No mail has been lost as the quarantined mail folder is continuously checked by members of Team Genesis, but please accept our apologies for any inconvenience caused. Your SPAM scanning system; Ullyses is continually being upgraded and refined so we anticipate a steadily decreasing number of incidents like this as the system learns your personal profile. If you feel that you are receiving an inappropriate amount of SPAM then can we ask you to contact us either by email to: [EMAIL PROTECTED] or call your Genesis representative who will be happy to assist. Please do not reply to this email address as it has been automatically generated, but email any queries to: [EMAIL PROTECTED] Thank you and take care Mark are you realising, that you're "spamming" a mailinglist here?
DNS tests getting aborted
Server .116 The email attached has been identified by one of our team as legitimate but unfortunately was incorrectly tagged as SPAM. The email address has been whitelisted to ensure this will not happen again and we are currently looking into the reasons why this happened. No mail has been lost as the quarantined mail folder is continuously checked by members of Team Genesis, but please accept our apologies for any inconvenience caused. Your SPAM scanning system; Ullyses is continually being upgraded and refined so we anticipate a steadily decreasing number of incidents like this as the system learns your personal profile. If you feel that you are receiving an inappropriate amount of SPAM then can we ask you to contact us either by email to: [EMAIL PROTECTED] or call your Genesis representative who will be happy to assist. Please do not reply to this email address as it has been automatically generated, but email any queries to: [EMAIL PROTECTED] Thank you and take care Mark --- Begin Message --- Hi, I have been using SA 3.1.5 for a long time now. I am testing SA 3.2 on a test machine before upgrade. Something seeems to be missing , none of the uridnsbl tests are working when I run SA in debug mode I can see 8454] dbg: check: running tests for priority: 500 [8454] dbg: dns: success for 0 of 29 queries [8454] dbg: dns: timeout for after 10 seconds [8454] dbg: dns: timeout for habeas-firsttrusted after 10 seconds [8454] dbg: dns: timeout for dob after 10 seconds [8454] dbg: dns: timeout for after 10 seconds [8454] dbg: dns: timeout for zen after 10 seconds [8454] dbg: dns: timeout for njabl after 10 seconds [8454] dbg: dns: timeout for after 10 seconds [8454] dbg: dns: timeout for bsp-firsttrusted after 10 seconds [8454] dbg: dns: timeout for spamcop after 10 seconds [8454] dbg: dns: timeout for dsbl-lastexternal after 10 seconds [8454] dbg: dns: timeout for dob after 10 seconds [8454] dbg: dns: timeout for spamcop after 10 seconds [8454] dbg: dns: timeout for njabl after 10 seconds [8454] dbg: dns: timeout for zen-lastexternal,zen-lastexternal,zen after 10 seconds [8454] dbg: dns: timeout for after 10 seconds [8454] dbg: dns: timeout for sorbs after 10 seconds [8454] dbg: dns: timeout for after 10 seconds [8454] dbg: dns: timeout for after 10 seconds [8454] dbg: dns: timeout for after 10 seconds [8454] dbg: dns: timeout for after 10 seconds [8454] dbg: dns: timeout for bsp-untrusted after 10 seconds [8454] dbg: dns: timeout for after 10 seconds [8454] dbg: dns: timeout for whois after 10 seconds [8454] dbg: dns: timeout for after 10 seconds [8454] dbg: dns: timeout for whois,whois-lastexternal after 10 seconds [8454] dbg: dns: timeout for after 10 seconds [8454] dbg: dns: timeout for after 10 seconds [8454] dbg: dns: timeout for iadb-firsttrusted after 10 seconds [8454] dbg: dns: timeout for sorbs-lastexternal,sorbs after 10 seconds [8454] dbg: async: aborting remaining lookups [8454] dbg: rules: running head tests; score so far=1.412 [8454] dbg: rules: compiled head tests -- but dig on the machine is working fine without any issues. my user_prefs file shows dns_available yes and I have Net::DNS What am I missing ? Thanks Ram *** Qmail-Scanner Quarantine Envelope Details Begin *** X-Antivirus-GenesisGroup-Mail-From: "[EMAIL PROTECTED]" via ssdd X-Antivirus-GenesisGroup-Rcpt-To: "[EMAIL PROTECTED]" X-Antivirus-GenesisGroup: 1.25st (perlscan: 1.25st. clamdscan: 0.90.2/3398. spamassassin: 3.1.8. problem Found. Processed in 3.689535 secs) process 21329 Quarantine-Description: SPAM exceeds "quarantine" threshold - hits=4.0/3.2 SA_REPORT hits = 4.0/3.2 -0.0 SPF_PASS SPF: sender matches SPF record -0.7 GENESIS_thanks BODY: body contains the string thanks 0.1 compareBODY: username and real name don't match 2.1 namecheck_bad BODY: Invalid username for sender 1.4 GENESIS_USERCHECK HEADER: Recipient not recognised (destcheck) 1.1 GENESIS_REMOTESMTP BODY: 25/TCP not listening on remote host *** Qmail-Scanner Envelope Details End ***--- End Message ---
Re: DNS tests getting aborted
On Mon, Jun 11, 2007 at 06:48:04PM +0530, ram wrote: > [8454] dbg: dns: success for 0 of 29 queries > [8454] dbg: dns: timeout for after 10 seconds > > but dig on the machine is working fine without any issues. > my user_prefs file shows dns_available yes > and I have Net::DNS Is the first DNS server listed in resolv.conf functional? Net::DNS isn't quite as resilient as bind-tools, unfortunately. ie: dig may return fine if it's skipping other name servers, while Net::DNS stops at the first one. -- Randomly Selected Tagline: Bender: He's a witch! pgpzYsP6A9IDy.pgp Description: PGP signature
Re: DNS tests getting aborted
On Mon, 11 Jun 2007, ram wrote: Hi, I have been using SA 3.1.5 for a long time now. I am testing SA 3.2 on a test machine before upgrade. Something seeems to be missing , none of the uridnsbl tests are working when I run SA in debug mode I can see 8454] dbg: check: running tests for priority: 500 [8454] dbg: dns: success for 0 of 29 queries [8454] dbg: dns: timeout for after 10 seconds [8454] dbg: dns: timeout for habeas-firsttrusted after 10 seconds [8454] dbg: dns: timeout for dob after 10 seconds [8454] dbg: dns: timeout for after 10 seconds [8454] dbg: dns: timeout for zen after 10 seconds [8454] dbg: dns: timeout for njabl after 10 seconds [8454] dbg: dns: timeout for after 10 seconds [8454] dbg: dns: timeout for bsp-firsttrusted after 10 seconds [8454] dbg: dns: timeout for spamcop after 10 seconds [8454] dbg: dns: timeout for dsbl-lastexternal after 10 seconds [8454] dbg: dns: timeout for dob after 10 seconds [8454] dbg: dns: timeout for spamcop after 10 seconds [8454] dbg: dns: timeout for njabl after 10 seconds [8454] dbg: dns: timeout for zen-lastexternal,zen-lastexternal,zen after 10 seconds [8454] dbg: dns: timeout for after 10 seconds [8454] dbg: dns: timeout for sorbs after 10 seconds [8454] dbg: dns: timeout for after 10 seconds [8454] dbg: dns: timeout for after 10 seconds [8454] dbg: dns: timeout for after 10 seconds [8454] dbg: dns: timeout for after 10 seconds [8454] dbg: dns: timeout for bsp-untrusted after 10 seconds [8454] dbg: dns: timeout for after 10 seconds [8454] dbg: dns: timeout for whois after 10 seconds [8454] dbg: dns: timeout for after 10 seconds [8454] dbg: dns: timeout for whois,whois-lastexternal after 10 seconds [8454] dbg: dns: timeout for after 10 seconds [8454] dbg: dns: timeout for after 10 seconds [8454] dbg: dns: timeout for iadb-firsttrusted after 10 seconds [8454] dbg: dns: timeout for sorbs-lastexternal,sorbs after 10 seconds [8454] dbg: async: aborting remaining lookups [8454] dbg: rules: running head tests; score so far=1.412 [8454] dbg: rules: compiled head tests -- but dig on the machine is working fine without any issues. my user_prefs file shows dns_available yes and I have Net::DNS What am I missing ? Is the plugin enabled in the init.pre (uncommented)? Specifically: # URIDNSBL - look up URLs found in the message against several DNS # blocklists. # loadplugin Mail::SpamAssassin::Plugin::URIDNSBL
DNS tests getting aborted
Hi, I have been using SA 3.1.5 for a long time now. I am testing SA 3.2 on a test machine before upgrade. Something seeems to be missing , none of the uridnsbl tests are working when I run SA in debug mode I can see 8454] dbg: check: running tests for priority: 500 [8454] dbg: dns: success for 0 of 29 queries [8454] dbg: dns: timeout for after 10 seconds [8454] dbg: dns: timeout for habeas-firsttrusted after 10 seconds [8454] dbg: dns: timeout for dob after 10 seconds [8454] dbg: dns: timeout for after 10 seconds [8454] dbg: dns: timeout for zen after 10 seconds [8454] dbg: dns: timeout for njabl after 10 seconds [8454] dbg: dns: timeout for after 10 seconds [8454] dbg: dns: timeout for bsp-firsttrusted after 10 seconds [8454] dbg: dns: timeout for spamcop after 10 seconds [8454] dbg: dns: timeout for dsbl-lastexternal after 10 seconds [8454] dbg: dns: timeout for dob after 10 seconds [8454] dbg: dns: timeout for spamcop after 10 seconds [8454] dbg: dns: timeout for njabl after 10 seconds [8454] dbg: dns: timeout for zen-lastexternal,zen-lastexternal,zen after 10 seconds [8454] dbg: dns: timeout for after 10 seconds [8454] dbg: dns: timeout for sorbs after 10 seconds [8454] dbg: dns: timeout for after 10 seconds [8454] dbg: dns: timeout for after 10 seconds [8454] dbg: dns: timeout for after 10 seconds [8454] dbg: dns: timeout for after 10 seconds [8454] dbg: dns: timeout for bsp-untrusted after 10 seconds [8454] dbg: dns: timeout for after 10 seconds [8454] dbg: dns: timeout for whois after 10 seconds [8454] dbg: dns: timeout for after 10 seconds [8454] dbg: dns: timeout for whois,whois-lastexternal after 10 seconds [8454] dbg: dns: timeout for after 10 seconds [8454] dbg: dns: timeout for after 10 seconds [8454] dbg: dns: timeout for iadb-firsttrusted after 10 seconds [8454] dbg: dns: timeout for sorbs-lastexternal,sorbs after 10 seconds [8454] dbg: async: aborting remaining lookups [8454] dbg: rules: running head tests; score so far=1.412 [8454] dbg: rules: compiled head tests -- but dig on the machine is working fine without any issues. my user_prefs file shows dns_available yes and I have Net::DNS What am I missing ? Thanks Ram
