5/13 Is there something wrong with spam assassin? I changed nothing
in my configuration files, but suddenly none of the junk mails
are getting processed. Thanks.
\_ Are you using spamc? If so the problem appears to be that
spamd isn't running.
\_ root has bigger fish to fry and spamd has stopped
frequently. I gave up and invoke spamassassin directly
now. See crebbs' procmail example above since he does
the same.
\_ what does root do if not make sure services that a
lot of people use keep running?
\_ Root is probably studying for finals,
give root a break. - yaalum
\_ Um, their classwork? Considering their salary for
the job, I think root@soda is doing pretty well.
-- alum
\_ while 1 { spamd };
\_ putting it into cron so that it starts
ever hour or so is better
\_ Well, no. Invoking spamassassin
directly is the correct answer.
\_ If everyone did this, soda
would be unusable.
\_ Your pont? If everyone who
had an account logged into
soda at once, it would be
unusable.
\_ When a more elegant
and less resource
intensive soln is
available it ought
to be used. I'm not
saying that root
needs to set this
asap, just whenever
so that things are
better for everyone.
\_
3:06PM up 112 days, 16:56, 219 users, load averages: 0.69, 0.55, 0.44
\_ you can look at your email headers and see what (if any) score
spamassassin is giving those mails. I have noticed a lot of
low scoring spam these days. You can change the rules in
your .spamassassin/user_prefs file to try to catch some of
these but you can cause false positives if you are not careful.
(though, perhaps your like me and if someone sends you HTML-only
mail, you don't care if you miss it). -crebbs
\_ The spam that is getting through doesn't have any of the
spam assassin headers (X-Spam-Status, X-Spam-Level, or
X-Spam-Checker-Version) which leads me to believe that
they never got run through spam assassin or that spam
assassin didn't do anything to the messages.
Perhaps the problem is with procmail and not spam
assassin? - !OP
\_ If you don't have those fields i assume it isn't going
through spamassassin. You can look at my .forward
and .procmailrc if you want to see a setup that works.
My last spam was caught at 9:30 this morning.
(i'm no expert, just followed a given recipe) -crebbs
\_ Thanks. Looks like my problem is with spamc/d.
\_ Also, you might want to check if the latest version is
installed?
\_ Hmm, I'm having the same problem as well. The last spam caught
was yesterday @ 6pm. Today, had two pieces of spam without any
X-Spam headers. Even mailed myself, no X-Spam headers. I haven't
changed any configuration in quite some time.
\_ Are you using spamc? If so the problem appears to be that
spamd isn't running.
\_ Yup. Should I be using something else?
\_ No according to the man pages we should all be using
spamc. Someone with root access should start spamd
so that spamc starts working again.
\_ mail root for this, don't post to the motd
root doesn't monitor the motd
\_ root has bigger fish to fry and spamd has stopped
frequently. I gave up and invoke spamassassin directly
now. See crebbs' procmail example above since he does
the same.
\_ pros & cons of doing this?
\_ spamassassin is slower and requires more
system resources than spamc. |
http://csua.com/feed/