You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Liam-PrintingAutomation <li...@printingautomation.com> on 2006/03/22 16:36:21 UTC
SA just stopped working
I installed spamassassin not long ago on our server, and it worked great!
Then sometime in the last couple of weeks it appears to have just
stopped working. No incoming e-mails are being tagged with spamassassin
headers anymore.
I restarted sendmail (eh, I know that wouldn't really do anything, but
hey, why not,) and I have in /etc/mail/spamassassin the files init.pre,
spamassassin-default.rc, spamassassin-spamc.rc.
In init.pre I have:
loadplugin Mail::SpamAssassin::Plugin::URIDNSBL
loadplugin Mail::SpamAssassin::Plugin::Hashcash
loadplugin Mail::SpamAssassin::Plugin::SPF
and in the other two files, both have:
# send mail through spamassassin
:0fw
| /usr/bin/spamassassin
Between the time it worked and I discovered it no longer working, I
didn't make any config changes, or any server changes for that matter.
What else should I look at to see if I can get it back up and going?
Thanks!
Liam
Re: SA just stopped working
Posted by jdow <jd...@earthlink.net>.
From: "Liam-PrintingAutomation" <li...@printingautomation.com>
> jdow wrote:
>
>> From: "Liam-PrintingAutomation" <li...@printingautomation.com>
>>
>>> I installed spamassassin not long ago on our server, and it worked
>>> great!
>>> Then sometime in the last couple of weeks it appears to have just
>>> stopped working. No incoming e-mails are being tagged with
>>> spamassassin headers anymore.
>>>
>>> I restarted sendmail (eh, I know that wouldn't really do anything,
>>> but hey, why not,) and I have in /etc/mail/spamassassin the files
>>> init.pre, spamassassin-default.rc, spamassassin-spamc.rc.
>>> In init.pre I have:
>>> loadplugin Mail::SpamAssassin::Plugin::URIDNSBL
>>> loadplugin Mail::SpamAssassin::Plugin::Hashcash
>>> loadplugin Mail::SpamAssassin::Plugin::SPF
>>>
>>> and in the other two files, both have:
>>> # send mail through spamassassin
>>> :0fw
>>> | /usr/bin/spamassassin
>>
>>
>> That is a procmail recipe not a SpamAssassin anything. Of course, neither
>> of the other two files you list is an anything for any installation of
>> which
>> I am aware.
>>
>> If you restarted or reinstalled sendmail did you make sure it still uses
>> procmail?
>>
>> {^_^}
>>
> I uhm, er, have no idea....
> How do I find out? I can't find anything in the Sendmail settings to
> indicate.
> I use Webmin for server management, and since you mentioned Procmail I
> took a look at the Webmin GUI for that, and found this:
> Set variable DROPPRIVS to yes
> <http://72.3.230.26:33427/procmail/edit_env.cgi?idx=0>
> <http://72.3.230.26:33427/procmail/down.cgi?idx=0>
> <http://72.3.230.26:33427/procmail/edit_recipe.cgi?new=1&before=0>
> <http://72.3.230.26:33427/procmail/edit_recipe.cgi?new=1&after=0>
> Feed to progam /usr/bin/spamc
> <http://72.3.230.26:33427/procmail/edit_recipe.cgi?idx=1> Always
> execute action
>
> So, Procmail is supposed to feed to Spamassassin. So the question
> remains, is it using Procmail.
> How do I know? If not, what else COULD it be using on the server?
> And how could it have mysteriously changed at some point without my
> doing anything? =/
>
> Thanks for the reply!
> -Liam
>
Consider asking the WebMin and SendMail folks. If sendmail calls procmail
then it should work. If something nuked the rule in sendmail that calls
procmail then it won't work. I know NOTHING about WebMin. I do not use it.
I do not plan to use it. It appears it is not transparent enough to be safe
to use, either.
{o.o}
Re: SA just stopped working
Posted by mouss <us...@free.fr>.
Matt Kettler wrote:
> It's not Linux centric, but it is to some degree *nix centric, but that will
> happen with any perl tool.
>
> Perl runs on lots of platforms, but is native to the *nix families. (ie: it
> requires special porting to run on windows, and even that doesn't support the
> whole perl language. Ditto for Netware.) That nativeness tends to lead to a
> larger *nix userbase for a perl tool.
>
> At the very least, expect to see a lot of posts from users on *nix machines.
>
> Even so, having a procmail logfile could probably be done even on windows for
> folks using cygwin. (at the very least, the # root-user prompt suggests they're
> using a *nix style shell, either on *nix, or via cygwin)
>
whether one has a procmail logfile or not is secondary here. I guessed
that he cited logs, but I wasn't absolutely certain. I think that
posters should be precise when they talk. otherwise, I could ask why my
SA isn't honoirig my Program~1\SA\hdr.cf. you would reply that this is a
windows blahblah thing, but this is not. I can have a unix path like that.
Re: SA just stopped working
Posted by Matt Kettler <mk...@evi-inc.com>.
mouss wrote:
> Matt Kettler wrote:
>> mouss wrote:
>>> Liam-PrintingAutomation wrote:
>>>> [root@s75712 log]# cat procmail
>>> ok... cat some file ....
>>>
>>>> procmail: [6329] Mon Mar 27 09:04:55 2006
>>>> procmail: Assigning "DROPPRIVS=yes"
>>>> procmail: Assuming identity of the recipient, VERBOSE=off
>>>> From Dell_Small_Business@ema10.net Mon Mar 27 09:04:55 2006
>>>> Subject: $399 Dell desktop with 15" flat panel deal.
>>>> Folder: /var/mail/sue
>>>
>>> do you really have this by doing 'cat procmail'?
>>
>>
>> Yes.. Note that he's in the log directory when doing this. Liam
>> probably has a
>> /var/log/procmail file that he's cat'ing.
>>
>> Lots of people reconfigure their syslog to better separate output,
>> maybe it
>> would work on your platform too :)
>>
>
> I'm sorry, but this is the first time I'v seen a 'cat procmail'. now I'm
> sorry. I didn't know this was a linux centric list;-p
It's not Linux centric, but it is to some degree *nix centric, but that will
happen with any perl tool.
Perl runs on lots of platforms, but is native to the *nix families. (ie: it
requires special porting to run on windows, and even that doesn't support the
whole perl language. Ditto for Netware.) That nativeness tends to lead to a
larger *nix userbase for a perl tool.
At the very least, expect to see a lot of posts from users on *nix machines.
Even so, having a procmail logfile could probably be done even on windows for
folks using cygwin. (at the very least, the # root-user prompt suggests they're
using a *nix style shell, either on *nix, or via cygwin)
Re: SA just stopped working
Posted by François Conil <co...@ece.fr>.
mouss a écrit :
> Liam-PrintingAutomation wrote:
>
>> Ah, sorry. I failed to mention what kind of server in my original
>> post. =) My bad.
>
>
> we can keep this game going a long time.
>
> my meaning was simply that people should make an effort to explain what
> they are talking about. I too can ask why my SA doesn't obey my
> C:\Program~1\Spam~1\badhdr.cf file.
>
> I am far from being perfect (and I have no desire to be so, because I
> know I can't). I just would like to see people posting without thinking
> that we're all running their platform.
No need to be such a nitpicker.
He said he was sorry, period.
F.C.
Re: SA just stopped working
Posted by Liam-PrintingAutomation <li...@printingautomation.com>.
mouss wrote:
> Liam-PrintingAutomation wrote:
>> Ah, sorry. I failed to mention what kind of server in my original
>> post. =) My bad.
>
> we can keep this game going a long time.
>
> my meaning was simply that people should make an effort to explain
> what they are talking about. I too can ask why my SA doesn't obey my
> C:\Program~1\Spam~1\badhdr.cf file.
>
> I am far from being perfect (and I have no desire to be so, because I
> know I can't). I just would like to see people posting without
> thinking that we're all running their platform.
>
Uhm, wow. Not to get the thread too sidetracked, but seriously, I made a
mistake an I apologize.
I sincerely didn't mean to assume anything. I failed to mention what
kind of server I was running, and as I said, "my bad."
When I post to newsgroups I nearly always mention from the get-go
something like "I'm running X application on a Fedora Core 4 Linux" or
"RedHat AS 4.1" or whatever.
I simply forgot when I started this thread. I seriously didn't mean to
assume anything. I as much as anyone realize you shouldn't assume
platforms. I have a Windows XP Pro, a Fedora Core 4, and a Windows 98 SE
at home, I work on a Slackware 10.2 and Fedora Core 3 at work, and have
servers running Fedora Core 2, and RedHat As 4.1, and we have a
workstation running Mac OS X.
Sorry if I opened up a can of worms. When I said "Ah, sorry," and "my
bad," I meant it!
-Liam
Re: SA just stopped working
Posted by mouss <us...@free.fr>.
Liam-PrintingAutomation wrote:
> Ah, sorry. I failed to mention what kind of server in my original post.
> =) My bad.
we can keep this game going a long time.
my meaning was simply that people should make an effort to explain what
they are talking about. I too can ask why my SA doesn't obey my
C:\Program~1\Spam~1\badhdr.cf file.
I am far from being perfect (and I have no desire to be so, because I
know I can't). I just would like to see people posting without
thinking that we're all running their platform.
Re: SA just stopped working
Posted by Liam-PrintingAutomation <li...@printingautomation.com>.
mouss wrote:
> Matt Kettler wrote:
>> mouss wrote:
>>> Liam-PrintingAutomation wrote:
>>>> [root@s75712 log]# cat procmail
>>> ok... cat some file ....
>>>
>>>> procmail: [6329] Mon Mar 27 09:04:55 2006
>>>> procmail: Assigning "DROPPRIVS=yes"
>>>> procmail: Assuming identity of the recipient, VERBOSE=off
>>>> From Dell_Small_Business@ema10.net Mon Mar 27 09:04:55 2006
>>>> Subject: $399 Dell desktop with 15" flat panel deal.
>>>> Folder: /var/mail/sue
>>>
>>> do you really have this by doing 'cat procmail'?
>>
>>
>> Yes.. Note that he's in the log directory when doing this. Liam
>> probably has a
>> /var/log/procmail file that he's cat'ing.
>>
>> Lots of people reconfigure their syslog to better separate output,
>> maybe it
>> would work on your platform too :)
>>
>
> I'm sorry, but this is the first time I'v seen a 'cat procmail'. now
> I'm sorry. I didn't know this was a linux centric list;-p
Ah, sorry. I failed to mention what kind of server in my original post.
=) My bad.
-Liam
Re: SA just stopped working
Posted by mouss <us...@free.fr>.
Matt Kettler wrote:
> mouss wrote:
>> Liam-PrintingAutomation wrote:
>>> [root@s75712 log]# cat procmail
>> ok... cat some file ....
>>
>>> procmail: [6329] Mon Mar 27 09:04:55 2006
>>> procmail: Assigning "DROPPRIVS=yes"
>>> procmail: Assuming identity of the recipient, VERBOSE=off
>>> From Dell_Small_Business@ema10.net Mon Mar 27 09:04:55 2006
>>> Subject: $399 Dell desktop with 15" flat panel deal.
>>> Folder: /var/mail/sue
>>
>> do you really have this by doing 'cat procmail'?
>
>
> Yes.. Note that he's in the log directory when doing this. Liam probably has a
> /var/log/procmail file that he's cat'ing.
>
> Lots of people reconfigure their syslog to better separate output, maybe it
> would work on your platform too :)
>
I'm sorry, but this is the first time I'v seen a 'cat procmail'. now I'm
sorry. I didn't know this was a linux centric list;-p
Re: SA just stopped working
Posted by Matt Kettler <mk...@evi-inc.com>.
mouss wrote:
> Liam-PrintingAutomation wrote:
>> [root@s75712 log]# cat procmail
>
> ok... cat some file ....
>
>> procmail: [6329] Mon Mar 27 09:04:55 2006
>> procmail: Assigning "DROPPRIVS=yes"
>> procmail: Assuming identity of the recipient, VERBOSE=off
>> From Dell_Small_Business@ema10.net Mon Mar 27 09:04:55 2006
>> Subject: $399 Dell desktop with 15" flat panel deal.
>> Folder: /var/mail/sue
>
>
> do you really have this by doing 'cat procmail'?
Yes.. Note that he's in the log directory when doing this. Liam probably has a
/var/log/procmail file that he's cat'ing.
Lots of people reconfigure their syslog to better separate output, maybe it
would work on your platform too :)
Re: SA just stopped working
Posted by mouss <us...@free.fr>.
Liam-PrintingAutomation wrote:
> [root@s75712 log]# cat procmail
ok... cat some file ....
> procmail: [6329] Mon Mar 27 09:04:55 2006
> procmail: Assigning "DROPPRIVS=yes"
> procmail: Assuming identity of the recipient, VERBOSE=off
> From Dell_Small_Business@ema10.net Mon Mar 27 09:04:55 2006
> Subject: $399 Dell desktop with 15" flat panel deal.
> Folder: /var/mail/sue
do you really have this by doing 'cat procmail'?
how about running 'rm spam'? This may work on your platform...
Re: SA just stopped working
Posted by mouss <us...@free.fr>.
Liam-PrintingAutomation wrote:
> I guess the question for me to figure out now, is why did the service
> stop running! =/
If that happens often, that would be a problem. but if it only happened
once, I don't think you should worry (This is less problematic than ntpd
exiting because the delta is too much... arghh).
Re: SA just stopped working
Posted by Liam-PrintingAutomation <li...@printingautomation.com>.
Matt Kettler wrote:
> Liam-PrintingAutomation wrote:
> exactly what use I can make of it, but it
>
>> proves that procmail is being used, no?
>> So, I don't understand. Procmailrc is being used and calling spamassassin:
>> [root@s75712 log]# cat /etc/procmailrc
>> LOGFILE=/var/log/procmail
>> VERBOSE=yes
>> DROPPRIVS=yes
>> :0fw
>> | /usr/bin/spamc
>>
>
>
> Question (which may have been covered earlier, and if it has, my bad)...
>
> Is spamd running?
>
A most excellent question! =)
How do I find out?
Well goshdangit! I KNOW I have tried restarting the "spamassassin"
service (which I hadn't before connected to being "spamd",) but I just
checked again at it appears it wasn't running:
[root@s75712 log]# /etc/rc.d/init.d/spamassassin status
spamd is stopped
So, I restarted it and tried a test message, and it came through tagged
with spamassassin headers.
I looked back at my posts, and I don't see where I mentioned I checked
before or tried restarting spamassassin (like I did for sendmail,
acknowledging that I know it shouldn't matter,) and I don't see that I'd
checked it.
My apologies; it's unforgivable that I didn't make a better effort to
see if it was running or not before I posted by problem. I've wasted
your time and electrons with my idiocy. =/
God I'm an idiot.
Sorry again. =/
I guess the question for me to figure out now, is why did the service
stop running! =/
Thanks, and sorry again. =(
-Liam
Re: SA just stopped working
Posted by Matt Kettler <mk...@evi-inc.com>.
Liam-PrintingAutomation wrote:
exactly what use I can make of it, but it
> proves that procmail is being used, no?
> So, I don't understand. Procmailrc is being used and calling spamassassin:
> [root@s75712 log]# cat /etc/procmailrc
> LOGFILE=/var/log/procmail
> VERBOSE=yes
> DROPPRIVS=yes
> :0fw
> | /usr/bin/spamc
Question (which may have been covered earlier, and if it has, my bad)...
Is spamd running?
Re: SA just stopped working
Posted by Liam-PrintingAutomation <li...@printingautomation.com>.
Peter H. Lemieux wrote:
> mouss wrote:
>> Liam-PrintingAutomation wrote:
>>>>
>>>> given what you posted, you sa seems to be ok. you now need to make
>>>> sure
>>>> your sendmail is actually calling procmail. try putting an error in
>>>> your
>
> You can tell procmail to log its actions by adding the following to
> the top of a procmailrc:
>
> LOGFILE=/path/to/logfile
> VERBOSE=yes
>
> If this a .procmailrc in a user's home directory, point the log to a
> location to which that user has write privileges, e.g.,
> /home/user/procmailog. If it's in /etc/procmailrc, it's probably
> better to write it to some place like /var/log/procmail.
OK, I added that to the top of /etc/procmailrc and it started logging:
[root@s75712 log]# cat procmail
procmail: [6329] Mon Mar 27 09:04:55 2006
procmail: Assigning "DROPPRIVS=yes"
procmail: Assuming identity of the recipient, VERBOSE=off
From Dell_Small_Business@ema10.net Mon Mar 27 09:04:55 2006
Subject: $399 Dell desktop with 15" flat panel deal.
Folder:
/var/mail/sue 32565
procmail: [6358] Mon Mar 27 09:05:52 2006
procmail: Assigning "DROPPRIVS=yes"
procmail: Assuming identity of the recipient, VERBOSE=off
From (anemailaddress)@FunniestStuff.net Mon Mar 27 09:05:52 2006
Subject: Barbell accident.
Folder:
/var/mail/merrilee 6130
procmail: [6373] Mon Mar 27 09:06:14 2006
procmail: Assigning "DROPPRIVS=yes"
procmail: Assuming identity of the recipient, VERBOSE=off
From ipcop-user-admin@lists.sourceforge.net Mon Mar 27 09:06:14 2006
Subject: Re: [IPCop-user] "Destination Host Unreachable" on Orange
Folder:
/var/mail/liam 7497
[root@s75712 log]#
That's interesting! Don't know exactly what use I can make of it, but it
proves that procmail is being used, no?
So, I don't understand. Procmailrc is being used and calling spamassassin:
[root@s75712 log]# cat /etc/procmailrc
LOGFILE=/var/log/procmail
VERBOSE=yes
DROPPRIVS=yes
:0fw
| /usr/bin/spamc
[root@s75712 log]#
and yet, the headers of the received e-mails don't show any Spamassassin
additions.
Not knowing exactly what it proves, I did what that earlier post
suggested to try:
[root@s75712 log]# echo blahblah > /tmp/bug
[root@s75712 log]# cat /tmp/bug
blahblah
[root@s75712 log]#
and
[root@s75712 log]# logger -p mail.error -t bug bug
[root@s75712 log]# tail maillog
[..]
Mar 27 09:14:50 s75712 bug: bug
[..]
That's kinda cool.
So that appears to show that logging is working.
What else can I look into?
Thanks for the replies!!
-Liam
Re: SA just stopped working
Posted by "Peter H. Lemieux" <ph...@cyways.com>.
mouss wrote:
> Liam-PrintingAutomation wrote:
>>>
>>> given what you posted, you sa seems to be ok. you now need to make sure
>>> your sendmail is actually calling procmail. try putting an error in your
You can tell procmail to log its actions by adding the following to the
top of a procmailrc:
LOGFILE=/path/to/logfile
VERBOSE=yes
If this a .procmailrc in a user's home directory, point the log to a
location to which that user has write privileges, e.g.,
/home/user/procmailog. If it's in /etc/procmailrc, it's probably better
to write it to some place like /var/log/procmail.
Re: SA just stopped working
Posted by mouss <us...@free.fr>.
Liam-PrintingAutomation wrote:
>>
>> given what you posted, you sa seems to be ok. you now need to make sure
>> your sendmail is actually calling procmail. try putting an error in your
>> procmail and see if that shouts.
> I'm sorry, I really don't understand what you mean.
> How do I put an error in Procmail?
for example by putting something incorrrect (syntactically), or an
`echo blahblah > /tmp/bug`
or
`logger -p mail.error -t bug bug`
...
use your imagination. find a way that shouts.
Also, check your MTA logs for evidence that procmail is really run.
Re: SA just stopped working
Posted by Liam-PrintingAutomation <li...@printingautomation.com>.
mouss wrote:
> Liam-PrintingAutomation a écrit :
>
>> I uhm, er, have no idea....
>> How do I find out? I can't find anything in the Sendmail settings to indicate.
>> I use Webmin for server management, and since you mentioned Procmail I took a
>> look at the Webmin GUI for that, and found this:
>> Set variable DROPPRIVS to yes
>> <http://72.3.230.26:33427/procmail/edit_env.cgi?idx=0>
>> <http://72.3.230.26:33427/procmail/down.cgi?idx=0>
>> <http://72.3.230.26:33427/procmail/edit_recipe.cgi?new=1&before=0>
>> <http://72.3.230.26:33427/procmail/edit_recipe.cgi?new=1&after=0>
>> Feed to progam /usr/bin/spamc
>> <http://72.3.230.26:33427/procmail/edit_recipe.cgi?idx=1> Always execute action
>>
>> So, Procmail is supposed to feed to Spamassassin. So the question remains, is it
>> using Procmail.
>> How do I know? If not, what else COULD it be using on the server?
>> And how could it have mysteriously changed at some point without my doing
>> anything? =/
>>
>>
>
> given what you posted, you sa seems to be ok. you now need to make sure
> your sendmail is actually calling procmail. try putting an error in your
> procmail and see if that shouts.
I'm sorry, I really don't understand what you mean.
How do I put an error in Procmail?
Thanks,
Liam
Re: SA just stopped working
Posted by mouss <us...@free.fr>.
Liam-PrintingAutomation a écrit :
> I uhm, er, have no idea....
> How do I find out? I can't find anything in the Sendmail settings to indicate.
> I use Webmin for server management, and since you mentioned Procmail I took a
> look at the Webmin GUI for that, and found this:
> Set variable DROPPRIVS to yes
> <http://72.3.230.26:33427/procmail/edit_env.cgi?idx=0>
> <http://72.3.230.26:33427/procmail/down.cgi?idx=0>
> <http://72.3.230.26:33427/procmail/edit_recipe.cgi?new=1&before=0>
> <http://72.3.230.26:33427/procmail/edit_recipe.cgi?new=1&after=0>
> Feed to progam /usr/bin/spamc
> <http://72.3.230.26:33427/procmail/edit_recipe.cgi?idx=1> Always execute action
>
> So, Procmail is supposed to feed to Spamassassin. So the question remains, is it
> using Procmail.
> How do I know? If not, what else COULD it be using on the server?
> And how could it have mysteriously changed at some point without my doing
> anything? =/
>
given what you posted, you sa seems to be ok. you now need to make sure
your sendmail is actually calling procmail. try putting an error in your
procmail and see if that shouts.
Re: SA just stopped working
Posted by Liam-PrintingAutomation <li...@printingautomation.com>.
jdow wrote:
> From: "Liam-PrintingAutomation" <li...@printingautomation.com>
>
>> I installed spamassassin not long ago on our server, and it worked
>> great!
>> Then sometime in the last couple of weeks it appears to have just
>> stopped working. No incoming e-mails are being tagged with
>> spamassassin headers anymore.
>>
>> I restarted sendmail (eh, I know that wouldn't really do anything,
>> but hey, why not,) and I have in /etc/mail/spamassassin the files
>> init.pre, spamassassin-default.rc, spamassassin-spamc.rc.
>> In init.pre I have:
>> loadplugin Mail::SpamAssassin::Plugin::URIDNSBL
>> loadplugin Mail::SpamAssassin::Plugin::Hashcash
>> loadplugin Mail::SpamAssassin::Plugin::SPF
>>
>> and in the other two files, both have:
>> # send mail through spamassassin
>> :0fw
>> | /usr/bin/spamassassin
>
>
> That is a procmail recipe not a SpamAssassin anything. Of course, neither
> of the other two files you list is an anything for any installation of
> which
> I am aware.
>
> If you restarted or reinstalled sendmail did you make sure it still uses
> procmail?
>
> {^_^}
>
I uhm, er, have no idea....
How do I find out? I can't find anything in the Sendmail settings to
indicate.
I use Webmin for server management, and since you mentioned Procmail I
took a look at the Webmin GUI for that, and found this:
Set variable DROPPRIVS to yes
<http://72.3.230.26:33427/procmail/edit_env.cgi?idx=0>
<http://72.3.230.26:33427/procmail/down.cgi?idx=0>
<http://72.3.230.26:33427/procmail/edit_recipe.cgi?new=1&before=0>
<http://72.3.230.26:33427/procmail/edit_recipe.cgi?new=1&after=0>
Feed to progam /usr/bin/spamc
<http://72.3.230.26:33427/procmail/edit_recipe.cgi?idx=1> Always
execute action
So, Procmail is supposed to feed to Spamassassin. So the question
remains, is it using Procmail.
How do I know? If not, what else COULD it be using on the server?
And how could it have mysteriously changed at some point without my
doing anything? =/
Thanks for the reply!
-Liam
Re: SA just stopped working
Posted by jdow <jd...@earthlink.net>.
From: "Liam-PrintingAutomation" <li...@printingautomation.com>
>I installed spamassassin not long ago on our server, and it worked great!
> Then sometime in the last couple of weeks it appears to have just
> stopped working. No incoming e-mails are being tagged with spamassassin
> headers anymore.
>
> I restarted sendmail (eh, I know that wouldn't really do anything, but
> hey, why not,) and I have in /etc/mail/spamassassin the files init.pre,
> spamassassin-default.rc, spamassassin-spamc.rc.
> In init.pre I have:
> loadplugin Mail::SpamAssassin::Plugin::URIDNSBL
> loadplugin Mail::SpamAssassin::Plugin::Hashcash
> loadplugin Mail::SpamAssassin::Plugin::SPF
>
> and in the other two files, both have:
> # send mail through spamassassin
> :0fw
> | /usr/bin/spamassassin
That is a procmail recipe not a SpamAssassin anything. Of course, neither
of the other two files you list is an anything for any installation of which
I am aware.
If you restarted or reinstalled sendmail did you make sure it still uses
procmail?
{^_^}
Re: SA just stopped working
Posted by Liam-PrintingAutomation <li...@printingautomation.com>.
Theo Van Dinter wrote:
>On Wed, Mar 22, 2006 at 09:12:14AM -0800, Mike Jackson wrote:
>
>
>>cat msg_to_test.txt | spamassassin -D --lint 2>&1 | more
>>Then look at the output to see if there's anything wrong.
>>
>>
>
>Just to note, there's no point in sending a message to spamassassin
>if you're doing --lint (it generates its own message). Just run
>"spamassassin -D --lint".
>
Wow, that spits out a lot of data!
Not sure what all (any) of it means, but nothing jumps out at me as an
error.
Any ideas?
Thanks!
-Liam
[root@s75712 spamassassin]# spamassassin -D --lint 2>&1
debug: SpamAssassin version 3.0.5
debug: Score set 0 chosen.
debug: running in taint mode? yes
debug: Running in taint mode, removing unsafe env vars, and resetting PATH
debug: PATH included '/usr/kerberos/sbin', keeping.
debug: PATH included '/usr/kerberos/bin', keeping.
debug: PATH included '/usr/local/sbin', keeping.
debug: PATH included '/usr/local/bin', keeping.
debug: PATH included '/sbin', keeping.
debug: PATH included '/bin', keeping.
debug: PATH included '/usr/sbin', keeping.
debug: PATH included '/usr/bin', keeping.
debug: PATH included '/usr/X11R6/bin', keeping.
debug: PATH included '/root/bin', keeping.
debug: Final PATH set to:
/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin:/root/bin
debug: diag: module installed: DBI, version 1.40
debug: diag: module installed: DB_File, version 1.809
debug: diag: module installed: Digest::SHA1, version 2.07
debug: diag: module installed: IO::Socket::UNIX, version 1.21
debug: diag: module installed: MIME::Base64, version 3.01
debug: diag: module installed: Net::DNS, version 0.48
debug: diag: module installed: Net::LDAP, version 0.31
debug: diag: module not installed: Razor2::Client::Agent ('require' failed)
debug: diag: module installed: Storable, version 2.13
debug: diag: module installed: URI, version 1.30
debug: ignore: using a test message to lint rules
debug: using "/etc/mail/spamassassin/init.pre" for site rules init.pre
debug: config: read file /etc/mail/spamassassin/init.pre
debug: using "/usr/share/spamassassin" for default rules dir
debug: config: read file /usr/share/spamassassin/10_misc.cf
debug: config: read file /usr/share/spamassassin/20_anti_ratware.cf
debug: config: read file /usr/share/spamassassin/20_body_tests.cf
debug: config: read file /usr/share/spamassassin/20_compensate.cf
debug: config: read file /usr/share/spamassassin/20_dnsbl_tests.cf
debug: config: read file /usr/share/spamassassin/20_drugs.cf
debug: config: read file /usr/share/spamassassin/20_fake_helo_tests.cf
debug: config: read file /usr/share/spamassassin/20_head_tests.cf
debug: config: read file /usr/share/spamassassin/20_html_tests.cf
debug: config: read file /usr/share/spamassassin/20_meta_tests.cf
debug: config: read file /usr/share/spamassassin/20_phrases.cf
debug: config: read file /usr/share/spamassassin/20_porn.cf
debug: config: read file /usr/share/spamassassin/20_ratware.cf
debug: config: read file /usr/share/spamassassin/20_uri_tests.cf
debug: config: read file /usr/share/spamassassin/23_bayes.cf
debug: config: read file /usr/share/spamassassin/25_body_tests_es.cf
debug: config: read file /usr/share/spamassassin/25_hashcash.cf
debug: config: read file /usr/share/spamassassin/25_spf.cf
debug: config: read file /usr/share/spamassassin/25_uribl.cf
debug: config: read file /usr/share/spamassassin/30_text_de.cf
debug: config: read file /usr/share/spamassassin/30_text_fr.cf
debug: config: read file /usr/share/spamassassin/30_text_nl.cf
debug: config: read file /usr/share/spamassassin/30_text_pl.cf
debug: config: read file /usr/share/spamassassin/50_scores.cf
debug: config: read file /usr/share/spamassassin/60_whitelist.cf
debug: using "/etc/mail/spamassassin" for site rules dir
debug: config: read file /etc/mail/spamassassin/local.cf
debug: using "/root/.spamassassin" for user state dir
debug: using "/root/.spamassassin/user_prefs" for user prefs file
debug: config: read file /root/.spamassassin/user_prefs
debug: plugin: loading Mail::SpamAssassin::Plugin::URIDNSBL from @INC
debug: plugin: registered
Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x95c7a00)
debug: plugin: loading Mail::SpamAssassin::Plugin::Hashcash from @INC
debug: plugin: registered
Mail::SpamAssassin::Plugin::Hashcash=HASH(0x9f10954)
debug: plugin: loading Mail::SpamAssassin::Plugin::SPF from @INC
debug: plugin: registered Mail::SpamAssassin::Plugin::SPF=HASH(0x9eec9d0)
debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x95c7a00)
implements 'parse_config'
debug: plugin: Mail::SpamAssassin::Plugin::Hashcash=HASH(0x9f10954)
implements 'parse_config'
debug: using "/root/.spamassassin" for user state dir
debug: bayes: no dbs present, cannot tie DB R/O:
/root/.spamassassin/bayes_toks
debug: Score set 1 chosen.
debug: ---- MIME PARSER START ----
debug: main message type: text/plain
debug: parsing normal part
debug: added part, type: text/plain
debug: ---- MIME PARSER END ----
debug: bayes: no dbs present, cannot tie DB R/O:
/root/.spamassassin/bayes_toks
debug: metadata: X-Spam-Relays-Trusted:
debug: metadata: X-Spam-Relays-Untrusted:
debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x95c7a00)
implements 'parsed_metadata'
debug: is Net::DNS::Resolver available? yes
debug: Net::DNS version: 0.48
debug: trying (3) w3.org...
debug: looking up NS for 'w3.org'
debug: NS lookup of w3.org succeeded => Dns available (set dns_available
to hardcode)
debug: is DNS available? 1
debug: decoding: no encoding detected
debug: URIDNSBL: domains to query:
debug: all '*From' addrs: ignore@compiling.spamassassin.taint.org
debug: Running tests for priority: 0
debug: running header regexp tests; score so far=0
debug: registering glue method for check_hashcash_double_spend
(Mail::SpamAssassin::Plugin::Hashcash=HASH(0x9f10954))
debug: registering glue method for check_for_spf_helo_pass
(Mail::SpamAssassin::Plugin::SPF=HASH(0x9eec9d0))
debug: SPF: message was delivered entirely via trusted relays, not required
debug: registering glue method for check_hashcash_value
(Mail::SpamAssassin::Plugin::Hashcash=HASH(0x9f10954))
debug: all '*To' addrs:
debug: registering glue method for check_for_spf_softfail
(Mail::SpamAssassin::Plugin::SPF=HASH(0x9eec9d0))
debug: SPF: message was delivered entirely via trusted relays, not required
debug: registering glue method for check_for_spf_pass
(Mail::SpamAssassin::Plugin::SPF=HASH(0x9eec9d0))
debug: registering glue method for check_for_spf_helo_softfail
(Mail::SpamAssassin::Plugin::SPF=HASH(0x9eec9d0))
debug: registering glue method for check_for_spf_fail
(Mail::SpamAssassin::Plugin::SPF=HASH(0x9eec9d0))
debug: registering glue method for check_for_spf_helo_fail
(Mail::SpamAssassin::Plugin::SPF=HASH(0x9eec9d0))
debug: running body-text per-line regexp tests; score so far=0.196
debug: running uri tests; score so far=0.196
debug: registering glue method for check_uridnsbl
(Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x95c7a00))
debug: Razor2 is not available
debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x95c7a00)
implements 'check_tick'
debug: running raw-body-text per-line regexp tests; score so far=0.196
debug: running full-text regexp tests; score so far=0.196
debug: Razor2 is not available
debug: Current PATH is:
/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin:/root/bin
debug: Pyzor is not available: pyzor not found
debug: DCCifd is not available: no r/w dccifd socket found.
debug: DCC is not available: no executable dccproc found.
debug: Running tests for priority: 500
debug: RBL: success for 1 of 1 queries
debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x95c7a00)
implements 'check_post_dnsbl'
debug: running meta tests; score so far=0.196
debug: running header regexp tests; score so far=1.765
debug: running body-text per-line regexp tests; score so far=1.765
debug: running uri tests; score so far=1.765
debug: running raw-body-text per-line regexp tests; score so far=1.765
debug: running full-text regexp tests; score so far=1.765
debug: Running tests for priority: 1000
debug: running meta tests; score so far=1.765
debug: running header regexp tests; score so far=1.765
debug: using "/root/.spamassassin" for user state dir
debug: lock: 17952 created
/root/.spamassassin/auto-whitelist.lock.s75712.printingautomation.com.17952
debug: lock: 17952 trying to get lock on
/root/.spamassassin/auto-whitelist with 0 retries
debug: lock: 17952 link to /root/.spamassassin/auto-whitelist.lock: link ok
debug: Tie-ing to DB file R/W in /root/.spamassassin/auto-whitelist
debug: auto-whitelist (db-based):
ignore@compiling.spamassassin.taint.org|ip=none scores 0/0
debug: AWL active, pre-score: 1.765, autolearn score: 1.765, mean:
undef, IP: undef
debug: DB addr list: untie-ing and unlocking.
debug: DB addr list: file locked, breaking lock.
debug: unlock: 17952 unlink /root/.spamassassin/auto-whitelist.lock
debug: Post AWL score: 1.765
debug: running body-text per-line regexp tests; score so far=1.765
debug: running uri tests; score so far=1.765
debug: running raw-body-text per-line regexp tests; score so far=1.765
debug: running full-text regexp tests; score so far=1.765
debug: is spam? score=1.765 required=4.5
debug: tests=MISSING_DATE,MISSING_SUBJECT,NO_REAL_NAME,NO_RECEIVED,NO_RELAYS
debug:
subtests=__HAS_MSGID,__MSGID_OK_DIGITS,__MSGID_OK_HOST,__SANE_MSGID,__UNUSABLE_MSGID
[root@s75712 spamassassin]#
Re: SA just stopped working
Posted by Theo Van Dinter <fe...@apache.org>.
On Wed, Mar 22, 2006 at 09:12:14AM -0800, Mike Jackson wrote:
> cat msg_to_test.txt | spamassassin -D --lint 2>&1 | more
> Then look at the output to see if there's anything wrong.
Just to note, there's no point in sending a message to spamassassin
if you're doing --lint (it generates its own message). Just run
"spamassassin -D --lint".
--
Randomly Generated Tagline:
"As a computing professional, I believe it would be unethical for me
to advise, recommend, or support the use (save possibly for personal
amusement) of any product that is or depends on any Microsoft product."
- David Wolfskill
Re: SA just stopped working
Posted by Mike Jackson <mj...@barking-dog.net>.
----- Original Message -----
From: "Liam-PrintingAutomation" <li...@printingautomation.com>
To: <us...@spamassassin.apache.org>
Sent: Wednesday, March 22, 2006 07:36
Subject: SA just stopped working
>I installed spamassassin not long ago on our server, and it worked great!
> Then sometime in the last couple of weeks it appears to have just
> stopped working. No incoming e-mails are being tagged with spamassassin
> headers anymore.
>
> I restarted sendmail (eh, I know that wouldn't really do anything, but
> hey, why not,) and I have in /etc/mail/spamassassin the files init.pre,
> spamassassin-default.rc, spamassassin-spamc.rc.
> In init.pre I have:
> loadplugin Mail::SpamAssassin::Plugin::URIDNSBL
> loadplugin Mail::SpamAssassin::Plugin::Hashcash
> loadplugin Mail::SpamAssassin::Plugin::SPF
>
> and in the other two files, both have:
> # send mail through spamassassin
> :0fw
> | /usr/bin/spamassassin
>
> Between the time it worked and I discovered it no longer working, I
> didn't make any config changes, or any server changes for that matter.
> What else should I look at to see if I can get it back up and going?
cat msg_to_test.txt | spamassassin -D --lint 2>&1 | more
Then look at the output to see if there's anything wrong.