You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Rob Starr <rs...@grantstream.com> on 2007/10/30 12:53:48 UTC

Re: Custom rules working, but not sa-updates

I should also mention that SA 3.1.3 was working flawlessly until the update
to 3.2.3.  I've used the newer config files and been through most of the
options, but still no luck.



Rob Starr wrote:
> 
> Hi, 
> 
> I'm using Postfix + MailScanner + MailWatch + SpamAssassin 3.2.3. 
> 
> My problem is that lots of spam is getting through because the rules 
> don't seem to be getting used, however my set of custom rules work 
> just fine (and disabling the custom ones hasn't helped).  I'm using
> Mailwatch so I can easily see which rules are being 
> hit, and which aren't. 
> 
> A lint test runs perfectly fine and reads all of the rule files without 
> error, all modules installed.  "spamassassin -t spam-sample.txt", uses 
> ALL of the rules and works fine, but any real mail going through the 
> system misses the spamassassin rules.  Also odd, is that Razor2 works 
> and the sa-update rule "RAZOR2_CHECK" always gets hit.  I've tried
> disabling 
> razor2 but no luck there. 
> 
> Just about every single email being processed hits one of these two rules
> (or any of the custom rules I have):
> RAZOR2_CHECK - Listed in Razor2 (http://razor.sf.net/) 
> RAZOR2_CF_RANGE_51_100 -Razor2 gives confidence level above 50% 
> 
> sa-update works fine by placing the latest rules in /var/lib/ 
> spamassassin/3.002003/.  I also have one custom .cf file in /etc/mail/ 
> spamassassin that always works. 
> 
> I've been troubleshooting for quite a while now and can't figure out 
> why the /var/lib/spamassassin/3.002003/ rules just aren't being used. 
> Any troubleshooting tips would be greatly appreciated.  Just let me 
> know what information you need. 
> 
> Thanks! 
> 

-- 
View this message in context: http://www.nabble.com/Custom-rules-working%2C-but-not-sa-updates-tf4711874.html#a13468319
Sent from the SpamAssassin - Users mailing list archive at Nabble.com.


Re: Custom rules working, but not sa-updates

Posted by Andy Norris <an...@tireswing.net>.
I appreciate that you would like to see it working right, Daryl. To 
that, I'd add, "me, too." But, like I said, I had to move on, and I 
hope to get back to it soon. And, by the way, I played with setting 
the update paths to all kinds of places, and all kinds of 
permissions, too. ;-) I'm sure it's something ON MY MACHINE that's 
not working. I was just trying to offer a suggestion to someone who 
seemed to be in a similar situation.

Thanks,
Andy


At 01:48 PM 2007-10-30, Daryl C. W. O'Shea wrote:
>Andy Norris wrote:
>>No, it was not a permissions issue. I'll get back to working on it 
>>soon, but, yes there were newer versions than what I was seeing on 
>>my server. There are so many posts about sa-update not working. I'm 
>>sure sa-update works, for some folks, but it wasn't for me, and I 
>>had to quit spending time on it.
>
>If you're referring to issues other than people deciding to screw 
>things up by setting their update path to use the same path as the 
>default rules directory could you please point me to the many posts 
>about sa-update not working?  I haven't seen them and would like to 
>see any issues resolved.
>
>Thanks,
>
>Daryl


Re: Custom rules working, but not sa-updates

Posted by "Daryl C. W. O'Shea" <sp...@dostech.ca>.
Andy Norris wrote:
> 
> No, it was not a permissions issue. I'll get back to working on it soon, 
> but, yes there were newer versions than what I was seeing on my server. 
> There are so many posts about sa-update not working. I'm sure sa-update 
> works, for some folks, but it wasn't for me, and I had to quit spending 
> time on it.

If you're referring to issues other than people deciding to screw things 
up by setting their update path to use the same path as the default 
rules directory could you please point me to the many posts about 
sa-update not working?  I haven't seen them and would like to see any 
issues resolved.

Thanks,

Daryl


Re: Custom rules working, but not sa-updates

Posted by Andy Norris <an...@tireswing.net>.
No, it was not a permissions issue. I'll get back to working on it 
soon, but, yes there were newer versions than what I was seeing on my 
server. There are so many posts about sa-update not working. I'm sure 
sa-update works, for some folks, but it wasn't for me, and I had to 
quit spending time on it.

Oh, and I meant "cron job"... not "crop job"... was typing on a tiny 
keyboard. Sorry.

Thanks,
Andy


At 01:09 PM 2007-10-30, Daniel J McDonald wrote:

>On Tue, 2007-10-30 at 08:35 -0500, Andy Norris wrote:
> > Hi,
> >
> > I don't know if this is relevant for you or not, but on our mail
> > server I could not get sa-update to work, either. I noticed that if
> > the directory was not there, however, it would work.
>
>Sounds like a permissions issue.
>
> >  So a down and
> > dirty approach I took was writing a crop job that removes that
> > directory just before running sa-update.
>
>So, you delete it every time, even when there are no updates?  And since
>updates occur about once or twice a month, you are downloading the same
>stuff over and over.  Plus you are missing rules at certain points of
>the cycle....
>
> >  I know this is going to be a
> > bit much for some folks on here to handle, but I had to get on with
> > life at some point!
>true, but you could just find the real problem (permissions) and fix it.
>
>--
>Daniel J McDonald, CCIE #2495, CISSP #78281, CNX
>Austin Energy
>http://www.austinenergy.com


Re: Custom rules working, but not sa-updates

Posted by "Daryl C. W. O'Shea" <sp...@dostech.ca>.
Daniel J McDonald wrote:
> On Tue, 2007-10-30 at 08:35 -0500, Andy Norris wrote:
>>  So a down and  
>> dirty approach I took was writing a crop job that removes that  
>> directory just before running sa-update.
> 
> So, you delete it every time, even when there are no updates?  And since
> updates occur about once or twice a month, you are downloading the same
> stuff over and over.  Plus you are missing rules at certain points of
> the cycle....

Is this a widespread practice?  It explains why I see *lots* of IPs 
downloading the same versions of the same rulesets at the same time(s) 
every single day.

Daryl


Re: Custom rules working, but not sa-updates

Posted by Daniel J McDonald <da...@austinenergy.com>.
On Tue, 2007-10-30 at 08:35 -0500, Andy Norris wrote:
> Hi,
> 
> I don't know if this is relevant for you or not, but on our mail  
> server I could not get sa-update to work, either. I noticed that if  
> the directory was not there, however, it would work.

Sounds like a permissions issue.  

>  So a down and  
> dirty approach I took was writing a crop job that removes that  
> directory just before running sa-update.

So, you delete it every time, even when there are no updates?  And since
updates occur about once or twice a month, you are downloading the same
stuff over and over.  Plus you are missing rules at certain points of
the cycle....

>  I know this is going to be a  
> bit much for some folks on here to handle, but I had to get on with  
> life at some point!
true, but you could just find the real problem (permissions) and fix it.

-- 
Daniel J McDonald, CCIE #2495, CISSP #78281, CNX
Austin Energy
http://www.austinenergy.com


RE: Custom rules working, but not sa-updates

Posted by Rob Starr <rs...@grantstream.com>.
Thanks Andy,

I have verified that sa-update is running and the rules folder is getting
populated with lots of files.


-----Original Message-----
From: Andy Norris [mailto:andy@tireswing.net] 
Sent: October-30-07 9:35 AM
To: Randal, Phil
Cc: Rob Starr; <us...@spamassassin.apache.org>
Subject: Re: Custom rules working, but not sa-updates

Hi,

I don't know if this is relevant for you or not, but on our mail  
server I could not get sa-update to work, either. I noticed that if  
the directory was not there, however, it would work. So a down and  
dirty approach I took was writing a crop job that removes that  
directory just before running sa-update. I know this is going to be a  
bit much for some folks on here to handle, but I had to get on with  
life at some point!

Good luck,
Andy


On Oct 30, 2007, at 7:39, "Randal, Phil"  
<pr...@herefordshire.gov.uk> wrote:

> Right, and what does the
>
>  MailScanner --debug --debug-sa
>
> output say it is using?
>
> Cheers,
>
> Phil
> --
> Phil Randal
> Network Engineer
> Herefordshire Council
> Hereford, UK
>
>> -----Original Message-----
>> From: Rob Starr [mailto:rstarr@grantstream.com]
>> Sent: 30 October 2007 12:29
>> To: users@spamassassin.apache.org
>> Subject: RE: Custom rules working, but not sa-updates
>>
>>
>> Thanks for your response Phil,
>>
>> In an attempt to resolve the issue, I'm now using MailScanner
>> 4.64.3 and
>> have started from a fresh config file, so my "Spamassassin
>> Local State Dir"
>> line also reads:
>>
>> SpamAssassin Local State Dir = # /var/lib/spamassassin
>>
>> And, as I mentioned, a lint test shows that SA is successfully  
>> reading
>> /var/lib/spamassassin/3.002003/updates_spamassassin_org.cf
>> and all of the
>> rules in the /var/lib/spamassassin/3.002003/updates_spamassassin_org/
>> folder.
>>
>> ----- Here are relavant lines from the lint test ------
>> [24215] dbg: config: read file
>> /var/lib/spamassassin/3.001003/updates_spamassassin_org.cf
>> [24215] dbg: plugin: fixed relative path:
>> /var/lib/spamassassin/3.001003/updates_spamassassin_org/10_misc.cf
>> [24215] dbg: config: using
>> "/var/lib/spamassassin/3.001003/updates_spamassassin_org/10_mi
>> sc.cf" for
>> included file
>> [24215] dbg: config: read file
>> /var/lib/spamassassin/3.001003/updates_spamassassin_org/10_mis
>> c.cf [24215]
>> dbg: plugin: fixed relative path:
>> /var/lib/spamassassin/3.001003/updates_spamassassin_org/20_adv
>> ance_fee.cf
>> [24215] dbg: config: using
>> "/var/lib/spamassassin/3.001003/updates_spamassassin_org/20_ad
>> vance_fee.cf"
>> for included file
>> [24215] dbg: config: read file
>> /var/lib/spamassassin/3.001003/updates_spamassassin_org/20_adv
>> ance_fee.cf
>> ...
>> -----
>>
>> Thanks again,
>> Rob
>>
>>
>> Randal, Phil wrote:
>>>
>>> Rob, that could be a MailScanner config problem.  You don't
>> say which
>>> version of MailScanner, alas.
>>>
>>> In /etc/MailScanner/MailScanner.conf check the
>> "Spamassassin Local State
>>> Dir" line.
>>>
>>> Mine reads:
>>>
>>> SpamAssassin Local State Dir = # /var/lib/spamassassin
>>>
>>> Cheers,
>>>
>>> Phil
>>> --
>>> Phil Randal
>>> Network Engineer
>>> Herefordshire Council
>>> Hereford, UK
>>>
>>>> -----Original Message-----
>>>> From: Rob Starr [mailto:rstarr@grantstream.com]
>>>> Sent: 30 October 2007 11:54
>>>> To: users@spamassassin.apache.org
>>>> Subject: Re: Custom rules working, but not sa-updates
>>>>
>>>>
>>>> I should also mention that SA 3.1.3 was working flawlessly
>>>> until the update
>>>> to 3.2.3.  I've used the newer config files and been through
>>>> most of the
>>>> options, but still no luck.
>>>>
>>>>
>>>>
>>>> Rob Starr wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> I'm using Postfix + MailScanner + MailWatch +
>> SpamAssassin 3.2.3.
>>>>>
>>>>> My problem is that lots of spam is getting through because
>>>> the rules
>>>>> don't seem to be getting used, however my set of custom
>> rules work
>>>>> just fine (and disabling the custom ones hasn't helped).
>> I'm using
>>>>> Mailwatch so I can easily see which rules are being
>>>>> hit, and which aren't.
>>>>>
>>>>> A lint test runs perfectly fine and reads all of the rule
>>>> files without
>>>>> error, all modules installed.  "spamassassin -t
>>>> spam-sample.txt", uses
>>>>> ALL of the rules and works fine, but any real mail going
>>>> through the
>>>>> system misses the spamassassin rules.  Also odd, is that
>>>> Razor2 works
>>>>> and the sa-update rule "RAZOR2_CHECK" always gets hit.
>> I've tried
>>>>> disabling
>>>>> razor2 but no luck there.
>>>>>
>>>>> Just about every single email being processed hits one of
>>>> these two rules
>>>>> (or any of the custom rules I have):
>>>>> RAZOR2_CHECK - Listed in Razor2 (http://razor.sf.net/)
>>>>> RAZOR2_CF_RANGE_51_100 -Razor2 gives confidence level above 50%
>>>>>
>>>>> sa-update works fine by placing the latest rules in /var/lib/
>>>>> spamassassin/3.002003/.  I also have one custom .cf file in
>>>> /etc/mail/
>>>>> spamassassin that always works.
>>>>>
>>>>> I've been troubleshooting for quite a while now and can't
>>>> figure out
>>>>> why the /var/lib/spamassassin/3.002003/ rules just aren't
>>>> being used.
>>>>> Any troubleshooting tips would be greatly appreciated.
>> Just let me
>>>>> know what information you need.
>>>>>
>>>>> Thanks!
>>>>>
>>>>
>>>> -- 
>>>> View this message in context:
>>>> http://www.nabble.com/Custom-rules-working%2C-but-not-sa-updat
>>>> es-tf4711874.html#a13468319
>>>> Sent from the SpamAssassin - Users mailing list archive at
>> Nabble.com.
>>>>
>>>>
>>>
>>>
>>
>> -- 
>> View this message in context:
>> http://www.nabble.com/Custom-rules-working%2C-but-not-sa-updat
>> es-tf4711874.html#a13487599
>> Sent from the SpamAssassin - Users mailing list archive at  
>> Nabble.com.
>>
>>



Re: Custom rules working, but not sa-updates

Posted by Andy Norris <an...@tireswing.net>.
Hi,

I don't know if this is relevant for you or not, but on our mail  
server I could not get sa-update to work, either. I noticed that if  
the directory was not there, however, it would work. So a down and  
dirty approach I took was writing a crop job that removes that  
directory just before running sa-update. I know this is going to be a  
bit much for some folks on here to handle, but I had to get on with  
life at some point!

Good luck,
Andy


On Oct 30, 2007, at 7:39, "Randal, Phil"  
<pr...@herefordshire.gov.uk> wrote:

> Right, and what does the
>
>  MailScanner --debug --debug-sa
>
> output say it is using?
>
> Cheers,
>
> Phil
> --
> Phil Randal
> Network Engineer
> Herefordshire Council
> Hereford, UK
>
>> -----Original Message-----
>> From: Rob Starr [mailto:rstarr@grantstream.com]
>> Sent: 30 October 2007 12:29
>> To: users@spamassassin.apache.org
>> Subject: RE: Custom rules working, but not sa-updates
>>
>>
>> Thanks for your response Phil,
>>
>> In an attempt to resolve the issue, I'm now using MailScanner
>> 4.64.3 and
>> have started from a fresh config file, so my "Spamassassin
>> Local State Dir"
>> line also reads:
>>
>> SpamAssassin Local State Dir = # /var/lib/spamassassin
>>
>> And, as I mentioned, a lint test shows that SA is successfully  
>> reading
>> /var/lib/spamassassin/3.002003/updates_spamassassin_org.cf
>> and all of the
>> rules in the /var/lib/spamassassin/3.002003/updates_spamassassin_org/
>> folder.
>>
>> ----- Here are relavant lines from the lint test ------
>> [24215] dbg: config: read file
>> /var/lib/spamassassin/3.001003/updates_spamassassin_org.cf
>> [24215] dbg: plugin: fixed relative path:
>> /var/lib/spamassassin/3.001003/updates_spamassassin_org/10_misc.cf
>> [24215] dbg: config: using
>> "/var/lib/spamassassin/3.001003/updates_spamassassin_org/10_mi
>> sc.cf" for
>> included file
>> [24215] dbg: config: read file
>> /var/lib/spamassassin/3.001003/updates_spamassassin_org/10_mis
>> c.cf [24215]
>> dbg: plugin: fixed relative path:
>> /var/lib/spamassassin/3.001003/updates_spamassassin_org/20_adv
>> ance_fee.cf
>> [24215] dbg: config: using
>> "/var/lib/spamassassin/3.001003/updates_spamassassin_org/20_ad
>> vance_fee.cf"
>> for included file
>> [24215] dbg: config: read file
>> /var/lib/spamassassin/3.001003/updates_spamassassin_org/20_adv
>> ance_fee.cf
>> ...
>> -----
>>
>> Thanks again,
>> Rob
>>
>>
>> Randal, Phil wrote:
>>>
>>> Rob, that could be a MailScanner config problem.  You don't
>> say which
>>> version of MailScanner, alas.
>>>
>>> In /etc/MailScanner/MailScanner.conf check the
>> "Spamassassin Local State
>>> Dir" line.
>>>
>>> Mine reads:
>>>
>>> SpamAssassin Local State Dir = # /var/lib/spamassassin
>>>
>>> Cheers,
>>>
>>> Phil
>>> --
>>> Phil Randal
>>> Network Engineer
>>> Herefordshire Council
>>> Hereford, UK
>>>
>>>> -----Original Message-----
>>>> From: Rob Starr [mailto:rstarr@grantstream.com]
>>>> Sent: 30 October 2007 11:54
>>>> To: users@spamassassin.apache.org
>>>> Subject: Re: Custom rules working, but not sa-updates
>>>>
>>>>
>>>> I should also mention that SA 3.1.3 was working flawlessly
>>>> until the update
>>>> to 3.2.3.  I've used the newer config files and been through
>>>> most of the
>>>> options, but still no luck.
>>>>
>>>>
>>>>
>>>> Rob Starr wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> I'm using Postfix + MailScanner + MailWatch +
>> SpamAssassin 3.2.3.
>>>>>
>>>>> My problem is that lots of spam is getting through because
>>>> the rules
>>>>> don't seem to be getting used, however my set of custom
>> rules work
>>>>> just fine (and disabling the custom ones hasn't helped).
>> I'm using
>>>>> Mailwatch so I can easily see which rules are being
>>>>> hit, and which aren't.
>>>>>
>>>>> A lint test runs perfectly fine and reads all of the rule
>>>> files without
>>>>> error, all modules installed.  "spamassassin -t
>>>> spam-sample.txt", uses
>>>>> ALL of the rules and works fine, but any real mail going
>>>> through the
>>>>> system misses the spamassassin rules.  Also odd, is that
>>>> Razor2 works
>>>>> and the sa-update rule "RAZOR2_CHECK" always gets hit.
>> I've tried
>>>>> disabling
>>>>> razor2 but no luck there.
>>>>>
>>>>> Just about every single email being processed hits one of
>>>> these two rules
>>>>> (or any of the custom rules I have):
>>>>> RAZOR2_CHECK - Listed in Razor2 (http://razor.sf.net/)
>>>>> RAZOR2_CF_RANGE_51_100 -Razor2 gives confidence level above 50%
>>>>>
>>>>> sa-update works fine by placing the latest rules in /var/lib/
>>>>> spamassassin/3.002003/.  I also have one custom .cf file in
>>>> /etc/mail/
>>>>> spamassassin that always works.
>>>>>
>>>>> I've been troubleshooting for quite a while now and can't
>>>> figure out
>>>>> why the /var/lib/spamassassin/3.002003/ rules just aren't
>>>> being used.
>>>>> Any troubleshooting tips would be greatly appreciated.
>> Just let me
>>>>> know what information you need.
>>>>>
>>>>> Thanks!
>>>>>
>>>>
>>>> -- 
>>>> View this message in context:
>>>> http://www.nabble.com/Custom-rules-working%2C-but-not-sa-updat
>>>> es-tf4711874.html#a13468319
>>>> Sent from the SpamAssassin - Users mailing list archive at
>> Nabble.com.
>>>>
>>>>
>>>
>>>
>>
>> -- 
>> View this message in context:
>> http://www.nabble.com/Custom-rules-working%2C-but-not-sa-updat
>> es-tf4711874.html#a13487599
>> Sent from the SpamAssassin - Users mailing list archive at  
>> Nabble.com.
>>
>>

RE: Custom rules working, but not sa-updates

Posted by "Randal, Phil" <pr...@herefordshire.gov.uk>.
"debug: using "/usr/share/spamassassin" for default rules dir"

Oh dear, that's definitely wrong.

You should have

  config: using "/var/lib/spamassassin/3.002003" for default rules dir

try setting the MailScanner.conf line to

SpamAssassin Local State Dir = # /var/lib/spamassassin

And see if that helps.

Try a

  MailScanner --lint

too in case there are other issues causing grief.

It's probably best to take this to the MailScanner mailing list.

Cheers,

Phil

--
Phil Randal
Network Engineer
Herefordshire Council
Hereford, UK  

> -----Original Message-----
> From: Rob Starr [mailto:rstarr@grantstream.com] 
> Sent: 30 October 2007 13:30
> To: users@spamassassin.apache.org
> Subject: RE: Custom rules working, but not sa-updates
> 
> 
> Boy, that's a handy command. I'll have to write that one down.
> 
> I'm getting:
> In Debugging mode, not forking...
> SpamAssassin temp dir = 
> /var/spool/MailScanner/incoming/SpamAssassin-Temp
> debug: Score set 0 chosen.
> debug: running in taint mode? no
> debug: ignore: test message to precompile patterns and load modules
> debug: using "/usr/share/spamassassin" for default rules dir
> debug: using "/etc/mail/spamassassin" for site rules dir
> debug: using "/var/spool/postfix/.spamassassin/user_prefs" 
> for user prefs
> file
> 
> MailScanner.conf currently has:
> SpamAssassin Site Rules Dir = /etc/mail/spamassassin
> SpamAssassin Local Rules Dir =
> SpamAssassin Local State Dir = /var/lib/spamassassin
> SpamAssassin Default Rules Dir =
> 
> 
> 
> Randal, Phil wrote:
> > 
> > Right, and what does the
> > 
> >   MailScanner --debug --debug-sa
> > 
> > output say it is using?
> > 
> > Cheers,
> > 
> > Phil
> > --
> > Phil Randal
> > Network Engineer
> > Herefordshire Council
> > Hereford, UK  
> > 
> >> -----Original Message-----
> >> From: Rob Starr [mailto:rstarr@grantstream.com] 
> >> Sent: 30 October 2007 12:29
> >> To: users@spamassassin.apache.org
> >> Subject: RE: Custom rules working, but not sa-updates
> >> 
> >> 
> >> Thanks for your response Phil,
> >> 
> >> In an attempt to resolve the issue, I'm now using MailScanner 
> >> 4.64.3 and
> >> have started from a fresh config file, so my "Spamassassin 
> >> Local State Dir"
> >> line also reads:
> >> 
> >> SpamAssassin Local State Dir = # /var/lib/spamassassin
> >> 
> >> And, as I mentioned, a lint test shows that SA is 
> successfully reading
> >> /var/lib/spamassassin/3.002003/updates_spamassassin_org.cf 
> >> and all of the
> >> rules in the 
> /var/lib/spamassassin/3.002003/updates_spamassassin_org/
> >> folder.
> >> 
> >> ----- Here are relavant lines from the lint test ------
> >> [24215] dbg: config: read file
> >> /var/lib/spamassassin/3.001003/updates_spamassassin_org.cf
> >> [24215] dbg: plugin: fixed relative path:
> >> /var/lib/spamassassin/3.001003/updates_spamassassin_org/10_misc.cf
> >> [24215] dbg: config: using
> >> "/var/lib/spamassassin/3.001003/updates_spamassassin_org/10_mi
> >> sc.cf" for
> >> included file
> >> [24215] dbg: config: read file
> >> /var/lib/spamassassin/3.001003/updates_spamassassin_org/10_mis
> >> c.cf [24215]
> >> dbg: plugin: fixed relative path:
> >> /var/lib/spamassassin/3.001003/updates_spamassassin_org/20_adv
> >> ance_fee.cf
> >> [24215] dbg: config: using
> >> "/var/lib/spamassassin/3.001003/updates_spamassassin_org/20_ad
> >> vance_fee.cf"
> >> for included file
> >> [24215] dbg: config: read file
> >> /var/lib/spamassassin/3.001003/updates_spamassassin_org/20_adv
> >> ance_fee.cf 
> >> ...
> >> -----
> >> 
> >> Thanks again,
> >> Rob
> >> 
> >> 
> >> Randal, Phil wrote:
> >> > 
> >> > Rob, that could be a MailScanner config problem.  You don't 
> >> say which
> >> > version of MailScanner, alas.
> >> > 
> >> > In /etc/MailScanner/MailScanner.conf check the 
> >> "Spamassassin Local State
> >> > Dir" line.
> >> > 
> >> > Mine reads:
> >> > 
> >> > SpamAssassin Local State Dir = # /var/lib/spamassassin
> >> > 
> >> > Cheers,
> >> > 
> >> > Phil
> >> > --
> >> > Phil Randal
> >> > Network Engineer
> >> > Herefordshire Council
> >> > Hereford, UK  
> >> > 
> >> >> -----Original Message-----
> >> >> From: Rob Starr [mailto:rstarr@grantstream.com] 
> >> >> Sent: 30 October 2007 11:54
> >> >> To: users@spamassassin.apache.org
> >> >> Subject: Re: Custom rules working, but not sa-updates
> >> >> 
> >> >> 
> >> >> I should also mention that SA 3.1.3 was working flawlessly 
> >> >> until the update
> >> >> to 3.2.3.  I've used the newer config files and been through 
> >> >> most of the
> >> >> options, but still no luck.
> >> >> 
> >> >> 
> >> >> 
> >> >> Rob Starr wrote:
> >> >> > 
> >> >> > Hi, 
> >> >> > 
> >> >> > I'm using Postfix + MailScanner + MailWatch + 
> >> SpamAssassin 3.2.3. 
> >> >> > 
> >> >> > My problem is that lots of spam is getting through because 
> >> >> the rules 
> >> >> > don't seem to be getting used, however my set of custom 
> >> rules work 
> >> >> > just fine (and disabling the custom ones hasn't helped). 
> >>  I'm using
> >> >> > Mailwatch so I can easily see which rules are being 
> >> >> > hit, and which aren't. 
> >> >> > 
> >> >> > A lint test runs perfectly fine and reads all of the rule 
> >> >> files without 
> >> >> > error, all modules installed.  "spamassassin -t 
> >> >> spam-sample.txt", uses 
> >> >> > ALL of the rules and works fine, but any real mail going 
> >> >> through the 
> >> >> > system misses the spamassassin rules.  Also odd, is that 
> >> >> Razor2 works 
> >> >> > and the sa-update rule "RAZOR2_CHECK" always gets hit.  
> >> I've tried
> >> >> > disabling 
> >> >> > razor2 but no luck there. 
> >> >> > 
> >> >> > Just about every single email being processed hits one of 
> >> >> these two rules
> >> >> > (or any of the custom rules I have):
> >> >> > RAZOR2_CHECK - Listed in Razor2 (http://razor.sf.net/) 
> >> >> > RAZOR2_CF_RANGE_51_100 -Razor2 gives confidence level 
> above 50% 
> >> >> > 
> >> >> > sa-update works fine by placing the latest rules in /var/lib/ 
> >> >> > spamassassin/3.002003/.  I also have one custom .cf file in 
> >> >> /etc/mail/ 
> >> >> > spamassassin that always works. 
> >> >> > 
> >> >> > I've been troubleshooting for quite a while now and can't 
> >> >> figure out 
> >> >> > why the /var/lib/spamassassin/3.002003/ rules just aren't 
> >> >> being used. 
> >> >> > Any troubleshooting tips would be greatly appreciated.  
> >> Just let me 
> >> >> > know what information you need. 
> >> >> > 
> >> >> > Thanks! 
> >> >> > 
> >> >> 
> >> >> -- 
> >> >> View this message in context: 
> >> >> http://www.nabble.com/Custom-rules-working%2C-but-not-sa-updat
> >> >> es-tf4711874.html#a13468319
> >> >> Sent from the SpamAssassin - Users mailing list archive at 
> >> Nabble.com.
> >> >> 
> >> >> 
> >> > 
> >> > 
> >> 
> >> -- 
> >> View this message in context: 
> >> http://www.nabble.com/Custom-rules-working%2C-but-not-sa-updat
> >> es-tf4711874.html#a13487599
> >> Sent from the SpamAssassin - Users mailing list archive at 
> Nabble.com.
> >> 
> >> 
> > 
> > 
> 
> -- 
> View this message in context: 
> http://www.nabble.com/Custom-rules-working%2C-but-not-sa-updat
> es-tf4711874.html#a13488515
> Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
> 
> 

RE: Custom rules working, but not sa-updates

Posted by Rob Starr <rs...@grantstream.com>.
Boy, that's a handy command. I'll have to write that one down.

I'm getting:
In Debugging mode, not forking...
SpamAssassin temp dir = /var/spool/MailScanner/incoming/SpamAssassin-Temp
debug: Score set 0 chosen.
debug: running in taint mode? no
debug: ignore: test message to precompile patterns and load modules
debug: using "/usr/share/spamassassin" for default rules dir
debug: using "/etc/mail/spamassassin" for site rules dir
debug: using "/var/spool/postfix/.spamassassin/user_prefs" for user prefs
file

MailScanner.conf currently has:
SpamAssassin Site Rules Dir = /etc/mail/spamassassin
SpamAssassin Local Rules Dir =
SpamAssassin Local State Dir = /var/lib/spamassassin
SpamAssassin Default Rules Dir =



Randal, Phil wrote:
> 
> Right, and what does the
> 
>   MailScanner --debug --debug-sa
> 
> output say it is using?
> 
> Cheers,
> 
> Phil
> --
> Phil Randal
> Network Engineer
> Herefordshire Council
> Hereford, UK  
> 
>> -----Original Message-----
>> From: Rob Starr [mailto:rstarr@grantstream.com] 
>> Sent: 30 October 2007 12:29
>> To: users@spamassassin.apache.org
>> Subject: RE: Custom rules working, but not sa-updates
>> 
>> 
>> Thanks for your response Phil,
>> 
>> In an attempt to resolve the issue, I'm now using MailScanner 
>> 4.64.3 and
>> have started from a fresh config file, so my "Spamassassin 
>> Local State Dir"
>> line also reads:
>> 
>> SpamAssassin Local State Dir = # /var/lib/spamassassin
>> 
>> And, as I mentioned, a lint test shows that SA is successfully reading
>> /var/lib/spamassassin/3.002003/updates_spamassassin_org.cf 
>> and all of the
>> rules in the /var/lib/spamassassin/3.002003/updates_spamassassin_org/
>> folder.
>> 
>> ----- Here are relavant lines from the lint test ------
>> [24215] dbg: config: read file
>> /var/lib/spamassassin/3.001003/updates_spamassassin_org.cf
>> [24215] dbg: plugin: fixed relative path:
>> /var/lib/spamassassin/3.001003/updates_spamassassin_org/10_misc.cf
>> [24215] dbg: config: using
>> "/var/lib/spamassassin/3.001003/updates_spamassassin_org/10_mi
>> sc.cf" for
>> included file
>> [24215] dbg: config: read file
>> /var/lib/spamassassin/3.001003/updates_spamassassin_org/10_mis
>> c.cf [24215]
>> dbg: plugin: fixed relative path:
>> /var/lib/spamassassin/3.001003/updates_spamassassin_org/20_adv
>> ance_fee.cf
>> [24215] dbg: config: using
>> "/var/lib/spamassassin/3.001003/updates_spamassassin_org/20_ad
>> vance_fee.cf"
>> for included file
>> [24215] dbg: config: read file
>> /var/lib/spamassassin/3.001003/updates_spamassassin_org/20_adv
>> ance_fee.cf 
>> ...
>> -----
>> 
>> Thanks again,
>> Rob
>> 
>> 
>> Randal, Phil wrote:
>> > 
>> > Rob, that could be a MailScanner config problem.  You don't 
>> say which
>> > version of MailScanner, alas.
>> > 
>> > In /etc/MailScanner/MailScanner.conf check the 
>> "Spamassassin Local State
>> > Dir" line.
>> > 
>> > Mine reads:
>> > 
>> > SpamAssassin Local State Dir = # /var/lib/spamassassin
>> > 
>> > Cheers,
>> > 
>> > Phil
>> > --
>> > Phil Randal
>> > Network Engineer
>> > Herefordshire Council
>> > Hereford, UK  
>> > 
>> >> -----Original Message-----
>> >> From: Rob Starr [mailto:rstarr@grantstream.com] 
>> >> Sent: 30 October 2007 11:54
>> >> To: users@spamassassin.apache.org
>> >> Subject: Re: Custom rules working, but not sa-updates
>> >> 
>> >> 
>> >> I should also mention that SA 3.1.3 was working flawlessly 
>> >> until the update
>> >> to 3.2.3.  I've used the newer config files and been through 
>> >> most of the
>> >> options, but still no luck.
>> >> 
>> >> 
>> >> 
>> >> Rob Starr wrote:
>> >> > 
>> >> > Hi, 
>> >> > 
>> >> > I'm using Postfix + MailScanner + MailWatch + 
>> SpamAssassin 3.2.3. 
>> >> > 
>> >> > My problem is that lots of spam is getting through because 
>> >> the rules 
>> >> > don't seem to be getting used, however my set of custom 
>> rules work 
>> >> > just fine (and disabling the custom ones hasn't helped). 
>>  I'm using
>> >> > Mailwatch so I can easily see which rules are being 
>> >> > hit, and which aren't. 
>> >> > 
>> >> > A lint test runs perfectly fine and reads all of the rule 
>> >> files without 
>> >> > error, all modules installed.  "spamassassin -t 
>> >> spam-sample.txt", uses 
>> >> > ALL of the rules and works fine, but any real mail going 
>> >> through the 
>> >> > system misses the spamassassin rules.  Also odd, is that 
>> >> Razor2 works 
>> >> > and the sa-update rule "RAZOR2_CHECK" always gets hit.  
>> I've tried
>> >> > disabling 
>> >> > razor2 but no luck there. 
>> >> > 
>> >> > Just about every single email being processed hits one of 
>> >> these two rules
>> >> > (or any of the custom rules I have):
>> >> > RAZOR2_CHECK - Listed in Razor2 (http://razor.sf.net/) 
>> >> > RAZOR2_CF_RANGE_51_100 -Razor2 gives confidence level above 50% 
>> >> > 
>> >> > sa-update works fine by placing the latest rules in /var/lib/ 
>> >> > spamassassin/3.002003/.  I also have one custom .cf file in 
>> >> /etc/mail/ 
>> >> > spamassassin that always works. 
>> >> > 
>> >> > I've been troubleshooting for quite a while now and can't 
>> >> figure out 
>> >> > why the /var/lib/spamassassin/3.002003/ rules just aren't 
>> >> being used. 
>> >> > Any troubleshooting tips would be greatly appreciated.  
>> Just let me 
>> >> > know what information you need. 
>> >> > 
>> >> > Thanks! 
>> >> > 
>> >> 
>> >> -- 
>> >> View this message in context: 
>> >> http://www.nabble.com/Custom-rules-working%2C-but-not-sa-updat
>> >> es-tf4711874.html#a13468319
>> >> Sent from the SpamAssassin - Users mailing list archive at 
>> Nabble.com.
>> >> 
>> >> 
>> > 
>> > 
>> 
>> -- 
>> View this message in context: 
>> http://www.nabble.com/Custom-rules-working%2C-but-not-sa-updat
>> es-tf4711874.html#a13487599
>> Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
>> 
>> 
> 
> 

-- 
View this message in context: http://www.nabble.com/Custom-rules-working%2C-but-not-sa-updates-tf4711874.html#a13488515
Sent from the SpamAssassin - Users mailing list archive at Nabble.com.


RE: Custom rules working, but not sa-updates

Posted by "Randal, Phil" <pr...@herefordshire.gov.uk>.
Right, and what does the

  MailScanner --debug --debug-sa

output say it is using?

Cheers,

Phil
--
Phil Randal
Network Engineer
Herefordshire Council
Hereford, UK  

> -----Original Message-----
> From: Rob Starr [mailto:rstarr@grantstream.com] 
> Sent: 30 October 2007 12:29
> To: users@spamassassin.apache.org
> Subject: RE: Custom rules working, but not sa-updates
> 
> 
> Thanks for your response Phil,
> 
> In an attempt to resolve the issue, I'm now using MailScanner 
> 4.64.3 and
> have started from a fresh config file, so my "Spamassassin 
> Local State Dir"
> line also reads:
> 
> SpamAssassin Local State Dir = # /var/lib/spamassassin
> 
> And, as I mentioned, a lint test shows that SA is successfully reading
> /var/lib/spamassassin/3.002003/updates_spamassassin_org.cf 
> and all of the
> rules in the /var/lib/spamassassin/3.002003/updates_spamassassin_org/
> folder.
> 
> ----- Here are relavant lines from the lint test ------
> [24215] dbg: config: read file
> /var/lib/spamassassin/3.001003/updates_spamassassin_org.cf
> [24215] dbg: plugin: fixed relative path:
> /var/lib/spamassassin/3.001003/updates_spamassassin_org/10_misc.cf
> [24215] dbg: config: using
> "/var/lib/spamassassin/3.001003/updates_spamassassin_org/10_mi
> sc.cf" for
> included file
> [24215] dbg: config: read file
> /var/lib/spamassassin/3.001003/updates_spamassassin_org/10_mis
> c.cf [24215]
> dbg: plugin: fixed relative path:
> /var/lib/spamassassin/3.001003/updates_spamassassin_org/20_adv
> ance_fee.cf
> [24215] dbg: config: using
> "/var/lib/spamassassin/3.001003/updates_spamassassin_org/20_ad
> vance_fee.cf"
> for included file
> [24215] dbg: config: read file
> /var/lib/spamassassin/3.001003/updates_spamassassin_org/20_adv
> ance_fee.cf 
> ...
> -----
> 
> Thanks again,
> Rob
> 
> 
> Randal, Phil wrote:
> > 
> > Rob, that could be a MailScanner config problem.  You don't 
> say which
> > version of MailScanner, alas.
> > 
> > In /etc/MailScanner/MailScanner.conf check the 
> "Spamassassin Local State
> > Dir" line.
> > 
> > Mine reads:
> > 
> > SpamAssassin Local State Dir = # /var/lib/spamassassin
> > 
> > Cheers,
> > 
> > Phil
> > --
> > Phil Randal
> > Network Engineer
> > Herefordshire Council
> > Hereford, UK  
> > 
> >> -----Original Message-----
> >> From: Rob Starr [mailto:rstarr@grantstream.com] 
> >> Sent: 30 October 2007 11:54
> >> To: users@spamassassin.apache.org
> >> Subject: Re: Custom rules working, but not sa-updates
> >> 
> >> 
> >> I should also mention that SA 3.1.3 was working flawlessly 
> >> until the update
> >> to 3.2.3.  I've used the newer config files and been through 
> >> most of the
> >> options, but still no luck.
> >> 
> >> 
> >> 
> >> Rob Starr wrote:
> >> > 
> >> > Hi, 
> >> > 
> >> > I'm using Postfix + MailScanner + MailWatch + 
> SpamAssassin 3.2.3. 
> >> > 
> >> > My problem is that lots of spam is getting through because 
> >> the rules 
> >> > don't seem to be getting used, however my set of custom 
> rules work 
> >> > just fine (and disabling the custom ones hasn't helped). 
>  I'm using
> >> > Mailwatch so I can easily see which rules are being 
> >> > hit, and which aren't. 
> >> > 
> >> > A lint test runs perfectly fine and reads all of the rule 
> >> files without 
> >> > error, all modules installed.  "spamassassin -t 
> >> spam-sample.txt", uses 
> >> > ALL of the rules and works fine, but any real mail going 
> >> through the 
> >> > system misses the spamassassin rules.  Also odd, is that 
> >> Razor2 works 
> >> > and the sa-update rule "RAZOR2_CHECK" always gets hit.  
> I've tried
> >> > disabling 
> >> > razor2 but no luck there. 
> >> > 
> >> > Just about every single email being processed hits one of 
> >> these two rules
> >> > (or any of the custom rules I have):
> >> > RAZOR2_CHECK - Listed in Razor2 (http://razor.sf.net/) 
> >> > RAZOR2_CF_RANGE_51_100 -Razor2 gives confidence level above 50% 
> >> > 
> >> > sa-update works fine by placing the latest rules in /var/lib/ 
> >> > spamassassin/3.002003/.  I also have one custom .cf file in 
> >> /etc/mail/ 
> >> > spamassassin that always works. 
> >> > 
> >> > I've been troubleshooting for quite a while now and can't 
> >> figure out 
> >> > why the /var/lib/spamassassin/3.002003/ rules just aren't 
> >> being used. 
> >> > Any troubleshooting tips would be greatly appreciated.  
> Just let me 
> >> > know what information you need. 
> >> > 
> >> > Thanks! 
> >> > 
> >> 
> >> -- 
> >> View this message in context: 
> >> http://www.nabble.com/Custom-rules-working%2C-but-not-sa-updat
> >> es-tf4711874.html#a13468319
> >> Sent from the SpamAssassin - Users mailing list archive at 
> Nabble.com.
> >> 
> >> 
> > 
> > 
> 
> -- 
> View this message in context: 
> http://www.nabble.com/Custom-rules-working%2C-but-not-sa-updat
> es-tf4711874.html#a13487599
> Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
> 
> 

RE: Custom rules working, but not sa-updates

Posted by Rob Starr <rs...@grantstream.com>.
Thanks for your response Phil,

In an attempt to resolve the issue, I'm now using MailScanner 4.64.3 and
have started from a fresh config file, so my "Spamassassin Local State Dir"
line also reads:

SpamAssassin Local State Dir = # /var/lib/spamassassin

And, as I mentioned, a lint test shows that SA is successfully reading
/var/lib/spamassassin/3.002003/updates_spamassassin_org.cf and all of the
rules in the /var/lib/spamassassin/3.002003/updates_spamassassin_org/
folder.

----- Here are relavant lines from the lint test ------
[24215] dbg: config: read file
/var/lib/spamassassin/3.001003/updates_spamassassin_org.cf
[24215] dbg: plugin: fixed relative path:
/var/lib/spamassassin/3.001003/updates_spamassassin_org/10_misc.cf
[24215] dbg: config: using
"/var/lib/spamassassin/3.001003/updates_spamassassin_org/10_misc.cf" for
included file
[24215] dbg: config: read file
/var/lib/spamassassin/3.001003/updates_spamassassin_org/10_misc.cf [24215]
dbg: plugin: fixed relative path:
/var/lib/spamassassin/3.001003/updates_spamassassin_org/20_advance_fee.cf
[24215] dbg: config: using
"/var/lib/spamassassin/3.001003/updates_spamassassin_org/20_advance_fee.cf"
for included file
[24215] dbg: config: read file
/var/lib/spamassassin/3.001003/updates_spamassassin_org/20_advance_fee.cf 
...
-----

Thanks again,
Rob


Randal, Phil wrote:
> 
> Rob, that could be a MailScanner config problem.  You don't say which
> version of MailScanner, alas.
> 
> In /etc/MailScanner/MailScanner.conf check the "Spamassassin Local State
> Dir" line.
> 
> Mine reads:
> 
> SpamAssassin Local State Dir = # /var/lib/spamassassin
> 
> Cheers,
> 
> Phil
> --
> Phil Randal
> Network Engineer
> Herefordshire Council
> Hereford, UK  
> 
>> -----Original Message-----
>> From: Rob Starr [mailto:rstarr@grantstream.com] 
>> Sent: 30 October 2007 11:54
>> To: users@spamassassin.apache.org
>> Subject: Re: Custom rules working, but not sa-updates
>> 
>> 
>> I should also mention that SA 3.1.3 was working flawlessly 
>> until the update
>> to 3.2.3.  I've used the newer config files and been through 
>> most of the
>> options, but still no luck.
>> 
>> 
>> 
>> Rob Starr wrote:
>> > 
>> > Hi, 
>> > 
>> > I'm using Postfix + MailScanner + MailWatch + SpamAssassin 3.2.3. 
>> > 
>> > My problem is that lots of spam is getting through because 
>> the rules 
>> > don't seem to be getting used, however my set of custom rules work 
>> > just fine (and disabling the custom ones hasn't helped).  I'm using
>> > Mailwatch so I can easily see which rules are being 
>> > hit, and which aren't. 
>> > 
>> > A lint test runs perfectly fine and reads all of the rule 
>> files without 
>> > error, all modules installed.  "spamassassin -t 
>> spam-sample.txt", uses 
>> > ALL of the rules and works fine, but any real mail going 
>> through the 
>> > system misses the spamassassin rules.  Also odd, is that 
>> Razor2 works 
>> > and the sa-update rule "RAZOR2_CHECK" always gets hit.  I've tried
>> > disabling 
>> > razor2 but no luck there. 
>> > 
>> > Just about every single email being processed hits one of 
>> these two rules
>> > (or any of the custom rules I have):
>> > RAZOR2_CHECK - Listed in Razor2 (http://razor.sf.net/) 
>> > RAZOR2_CF_RANGE_51_100 -Razor2 gives confidence level above 50% 
>> > 
>> > sa-update works fine by placing the latest rules in /var/lib/ 
>> > spamassassin/3.002003/.  I also have one custom .cf file in 
>> /etc/mail/ 
>> > spamassassin that always works. 
>> > 
>> > I've been troubleshooting for quite a while now and can't 
>> figure out 
>> > why the /var/lib/spamassassin/3.002003/ rules just aren't 
>> being used. 
>> > Any troubleshooting tips would be greatly appreciated.  Just let me 
>> > know what information you need. 
>> > 
>> > Thanks! 
>> > 
>> 
>> -- 
>> View this message in context: 
>> http://www.nabble.com/Custom-rules-working%2C-but-not-sa-updat
>> es-tf4711874.html#a13468319
>> Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
>> 
>> 
> 
> 

-- 
View this message in context: http://www.nabble.com/Custom-rules-working%2C-but-not-sa-updates-tf4711874.html#a13487599
Sent from the SpamAssassin - Users mailing list archive at Nabble.com.


RE: Custom rules working, but not sa-updates

Posted by "Randal, Phil" <pr...@herefordshire.gov.uk>.
Rob, that could be a MailScanner config problem.  You don't say which
version of MailScanner, alas.

In /etc/MailScanner/MailScanner.conf check the "Spamassassin Local State
Dir" line.

Mine reads:

SpamAssassin Local State Dir = # /var/lib/spamassassin

Cheers,

Phil
--
Phil Randal
Network Engineer
Herefordshire Council
Hereford, UK  

> -----Original Message-----
> From: Rob Starr [mailto:rstarr@grantstream.com] 
> Sent: 30 October 2007 11:54
> To: users@spamassassin.apache.org
> Subject: Re: Custom rules working, but not sa-updates
> 
> 
> I should also mention that SA 3.1.3 was working flawlessly 
> until the update
> to 3.2.3.  I've used the newer config files and been through 
> most of the
> options, but still no luck.
> 
> 
> 
> Rob Starr wrote:
> > 
> > Hi, 
> > 
> > I'm using Postfix + MailScanner + MailWatch + SpamAssassin 3.2.3. 
> > 
> > My problem is that lots of spam is getting through because 
> the rules 
> > don't seem to be getting used, however my set of custom rules work 
> > just fine (and disabling the custom ones hasn't helped).  I'm using
> > Mailwatch so I can easily see which rules are being 
> > hit, and which aren't. 
> > 
> > A lint test runs perfectly fine and reads all of the rule 
> files without 
> > error, all modules installed.  "spamassassin -t 
> spam-sample.txt", uses 
> > ALL of the rules and works fine, but any real mail going 
> through the 
> > system misses the spamassassin rules.  Also odd, is that 
> Razor2 works 
> > and the sa-update rule "RAZOR2_CHECK" always gets hit.  I've tried
> > disabling 
> > razor2 but no luck there. 
> > 
> > Just about every single email being processed hits one of 
> these two rules
> > (or any of the custom rules I have):
> > RAZOR2_CHECK - Listed in Razor2 (http://razor.sf.net/) 
> > RAZOR2_CF_RANGE_51_100 -Razor2 gives confidence level above 50% 
> > 
> > sa-update works fine by placing the latest rules in /var/lib/ 
> > spamassassin/3.002003/.  I also have one custom .cf file in 
> /etc/mail/ 
> > spamassassin that always works. 
> > 
> > I've been troubleshooting for quite a while now and can't 
> figure out 
> > why the /var/lib/spamassassin/3.002003/ rules just aren't 
> being used. 
> > Any troubleshooting tips would be greatly appreciated.  Just let me 
> > know what information you need. 
> > 
> > Thanks! 
> > 
> 
> -- 
> View this message in context: 
> http://www.nabble.com/Custom-rules-working%2C-but-not-sa-updat
> es-tf4711874.html#a13468319
> Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
> 
>