Re: Spamassassin not scanning all emails
> My Spamassassin worked for years without skipping any emails. Suddenly > (and not coresponding to an upgrade) emails started showing up in my inbox > without spamassassin headers. Look in your log and see if you have reports of an 'insecure dependency' in SA. Loren
Re: Spamassassin not scanning all emails
jdow wrote: I've whined. It SEEMS to trace to a perl bug. In fact it seems to be related to a perl interaction between threads which should be impossible. ...and I've long ago sent you a patch to help debug it. :p
Re: Spamassassin not scanning all emails
If it was in $USER/.spamassassin/user_prefs it's very good. There is a Yep, the rawbody rule was in my user_prefs. workaround if you are using procmail. (If SA does not put headers into the message run it again. I run it as "spamassassin" rather than the daemon to be sure. I've seen VERY VERY few sneak through under that regime. I was thinking about doing that, but thought it would be best to find out what was really happening. I've no interest right now in adding that rawbody rule back in, as it wasn't doing anything. The number of untagged emails seems to have dropped substantially (maybe even to zero). Thanks for your (and everyone else's) help! =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- | Jason Marshall, [EMAIL PROTECTED] Spots InterConnect, Inc. Calgary, AB | =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Re: Spamassassin not scanning all emails
From: "Jason Marshall" <[EMAIL PROTECTED]>
How big are the messages that aren't getting scanned?
Over 250k?
Random sizes, most far smaller than 250k.
And do you have per user rules enabled? If so do any of the user
rules have a rawbody or full rule attribute?
I do; each user has a .spamassassin/user_prefs file. Most of them are
exactly the same. I did notice that I had put a rawbody rule into my
config file some time ago. I've taken it out just now, as it was never
getting hit.
You could check your logfiles. By default spamd logs to the "mail"
facility, so
they should be in your /var/log/maillog.
The emails that are not getting scanned do NOT show up in the logs. The
ones that do get scanned, I can look for by message-id, but not these
ones.
I just noticed that I get "spamd[797]: prefork: child states: " quite
often in the logs. This doesn't look bad to me, but I don't know what
is supposed to mean... Probably nothing.
If the above answers to my questions are "yes" search also for
"PerMsgStatus".
You could well be onto something. I see lots (750+) of these in today's
logs:
Feb 13 18:56:38 ocelot spamd[4200]: Use of uninitialized value in numeric
le (<=) at /usr/local/share/perl/5.8.4/Mail/SpamAssassin/PerMsgStatus.pm
line 2703.
Feb 13 18:56:38 ocelot spamd[4200]: Use of uninitialized value in sprintf
at /usr/local/share/perl/5.8.4/Mail/SpamAssassin/PerMsgStatus.pm line
2707.
Feb 13 18:56:38 ocelot spamd[4200]: Use of uninitialized value in numeric
eq (==) at /usr/local/share/perl/5.8.4/Mail/SpamAssassin/PerMsgStatus.pm
line 430.
Those certainly look like failures to me!
I've turned off the rawbody rule I had in my config file; what are the
chances that that was the fix?
If it was in $USER/.spamassassin/user_prefs it's very good. There is a
workaround if you are using procmail. (If SA does not put headers into
the message run it again. I run it as "spamassassin" rather than the
daemon to be sure. I've seen VERY VERY few sneak through under that regime.
I should have noticed that no one else was whining about the amount of
spam getting through, and if they were getting as much as me (hundreds a
day, untagged) they surely would have!!
I've whined. It SEEMS to trace to a perl bug. In fact it seems to be
related to a perl interaction between threads which should be impossible.
{^_^}
Re: Spamassassin not scanning all emails
Jason Marshall wrote: > > I just noticed that I get "spamd[797]: prefork: child states: " > quite often in the logs. This doesn't look bad to me, but I don't > know what is supposed to mean... Probably nothing. That means 4 children exist, and they are all idle. That's a good thing :)
Re: Spamassassin not scanning all emails
How big are the messages that aren't getting scanned? Over 250k? Random sizes, most far smaller than 250k. And do you have per user rules enabled? If so do any of the user rules have a rawbody or full rule attribute? I do; each user has a .spamassassin/user_prefs file. Most of them are exactly the same. I did notice that I had put a rawbody rule into my config file some time ago. I've taken it out just now, as it was never getting hit. You could check your logfiles. By default spamd logs to the "mail" facility, so they should be in your /var/log/maillog. The emails that are not getting scanned do NOT show up in the logs. The ones that do get scanned, I can look for by message-id, but not these ones. I just noticed that I get "spamd[797]: prefork: child states: " quite often in the logs. This doesn't look bad to me, but I don't know what is supposed to mean... Probably nothing. If the above answers to my questions are "yes" search also for "PerMsgStatus". You could well be onto something. I see lots (750+) of these in today's logs: Feb 13 18:56:38 ocelot spamd[4200]: Use of uninitialized value in numeric le (<=) at /usr/local/share/perl/5.8.4/Mail/SpamAssassin/PerMsgStatus.pm line 2703. Feb 13 18:56:38 ocelot spamd[4200]: Use of uninitialized value in sprintf at /usr/local/share/perl/5.8.4/Mail/SpamAssassin/PerMsgStatus.pm line 2707. Feb 13 18:56:38 ocelot spamd[4200]: Use of uninitialized value in numeric eq (==) at /usr/local/share/perl/5.8.4/Mail/SpamAssassin/PerMsgStatus.pm line 430. Those certainly look like failures to me! I've turned off the rawbody rule I had in my config file; what are the chances that that was the fix? I should have noticed that no one else was whining about the amount of spam getting through, and if they were getting as much as me (hundreds a day, untagged) they surely would have!! I can send my config file if anyone's interested in seeing it. Now, it's mostly just whitelist entries. Thanks guys!!! =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- | Jason Marshall, [EMAIL PROTECTED] Spots InterConnect, Inc. Calgary, AB | =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Re: Spamassassin not scanning all emails
From: "Matt Kettler" <[EMAIL PROTECTED]>
Jason Marshall wrote:
Good day!
My Spamassassin worked for years without skipping any emails. Suddenly
(and not coresponding to an upgrade) emails started showing up in my
inbox without spamassassin headers.
How big are the messages that aren't getting scanned?
Over 250k?
And do you have per user rules enabled? If so do any of the user
rules have a rawbody or full rule attribute?
I call spamc via procmail. Spamassassin is v3.1.0, and I run spamd like
this:
/usr/bin/spamd -d --min-spare=3 --max-conn-per-child=50 -m 15
I've tried adjusting the -m values even as high as 50, and it doesn't
seem to make any difference.
It shouldn't make any difference.
Is it possible that spamd is being overloaded? This server "only" does
about 25000 messages a day, has 3 gigs of RAM, and a decent 2.0 GHz CPU.
I don't believe there are hardware issues -- nothing seems to be working
incorrectly other than spamc.
Is there anywhere to look for messages from spamd about why it doesn't
appear to be either accepting new connections, or isn't scanning, or
whatever it's actually doing? Thanks!
You could check your logfiles. By default spamd logs to the "mail" facility, so
they should be in your /var/log/maillog.
If the above answers to my questions are "yes" search also for "PerMsgStatus".
{^_^}
Re: Spamassassin not scanning all emails
Jason Marshall wrote: > Good day! > > My Spamassassin worked for years without skipping any emails. Suddenly > (and not coresponding to an upgrade) emails started showing up in my > inbox without spamassassin headers. How big are the messages that aren't getting scanned? Over 250k? > > I call spamc via procmail. Spamassassin is v3.1.0, and I run spamd like > this: > > /usr/bin/spamd -d --min-spare=3 --max-conn-per-child=50 -m 15 > > I've tried adjusting the -m values even as high as 50, and it doesn't > seem to make any difference. It shouldn't make any difference. > > Is it possible that spamd is being overloaded? This server "only" does > about 25000 messages a day, has 3 gigs of RAM, and a decent 2.0 GHz CPU. > I don't believe there are hardware issues -- nothing seems to be working > incorrectly other than spamc. > > Is there anywhere to look for messages from spamd about why it doesn't > appear to be either accepting new connections, or isn't scanning, or > whatever it's actually doing? Thanks! You could check your logfiles. By default spamd logs to the "mail" facility, so they should be in your /var/log/maillog.
Spamassassin not scanning all emails
Good day! My Spamassassin worked for years without skipping any emails. Suddenly (and not coresponding to an upgrade) emails started showing up in my inbox without spamassassin headers. I call spamc via procmail. Spamassassin is v3.1.0, and I run spamd like this: /usr/bin/spamd -d --min-spare=3 --max-conn-per-child=50 -m 15 I've tried adjusting the -m values even as high as 50, and it doesn't seem to make any difference. Is it possible that spamd is being overloaded? This server "only" does about 25000 messages a day, has 3 gigs of RAM, and a decent 2.0 GHz CPU. I don't believe there are hardware issues -- nothing seems to be working incorrectly other than spamc. Is there anywhere to look for messages from spamd about why it doesn't appear to be either accepting new connections, or isn't scanning, or whatever it's actually doing? Thanks! =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- | Jason Marshall, [EMAIL PROTECTED] Spots InterConnect, Inc. Calgary, AB | =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
