bug report

[Rick Cooper]

It seems odd that that ever worked. Near as I can tell the local state dir
directive came in around SA V 3.2 (could not find reference in the 3.0/3.1
readme files) and has always been (default) /var/lib/spamassassin and the
MailScanner.conf notes for the setting state the default as same. From
MailScanner.conf:
 
# The rules created by the "sa-update" tool are searched for here.
# This directory contains the 3.001001/updates_spamassassin_org
# directory structure beneath it.
# Only un-comment this setting once you have proved that the sa-update
# cron job has run successfully and has created a directory structure under
# the spamassassin directory within this one and has put some *.cf files in
# there. Otherwise it will ignore all your current rules!
# The default location may be /var/opt on Solaris systems.
SpamAssassin Local State Dir = /var/lib/spamassassin

( and yes I top posted and did not convert html to text because I don't want
to manually fix the quoting)

  _____  

From: mailscanner-bounces at lists.mailscanner.info
[mailto:mailscanner-bounces at lists.mailscanner.info] On Behalf Of Noel Butler
Sent: Sunday, February 14, 2010 2:32 AM
To: Ying; MailScanner discussion
Subject: Re: bug report


Ying,

A followup to this mornings mail, just got home and had a good look at it.
This issue can be resolved by changing locale state dir from /var/lib
to /var/lib/spamassasasin   it seems it no longer likes the search path 
being just /var/lib anymore.

I know /var/lib worked as recently as a little over a month ago by looking
at logs,  and by looking at the timestamps it all stopped here the day I
upgraded
all perl modules and SA (so it seems it has not been working properly here
for
month either, yikes!),  but everything is working fine for an hour now ,
every mailscanner
score matches that given by amavisd-new, so i can thankfully get rid of that
:)

Now be it SA or one of the perl modules that saw the ending of its liking
/var/lib I have no idea as I did them here all same time, so it is likely 
that anyone else using the old /var/lib  only in that setting will have
issues upon upgrading something or other down the track.

Julian
FYI, this also resolved my  "no report template found " problem I told you
occurred with these upgrades.  I'd send this to the list but as you know I'm
marked no posting so maybe you'd like to edit me out of this and resend it
on 
as a reminder to any members still using the old  /var/lib to play it safe
and 
add spamassassin  to the end of it :)

Cheers



On Sat, 2010-02-13 at 10:29 +1000, Ying wrote: 

Rick, Hello, 

Yes I think much lost in translation, mailscanner work like this for three
years fine. 

We upgrade spamassassin to 3.3.0, this also also mean we upgrade all perl
modules needed by mailscanner, we check to make sure we have all required
modules, all look good, then start mailscanner back on and this problem
appear now. 

----- Original Message ----- 

From: Rick Cooper <mailto:rcooper at dwford.com>  

To: 'MailScanner  <mailto:mailscanner at lists.mailscanner.info> discussion' 

Sent: Thursday, February 11, 2010 2:31 AM 

Subject: RE: bug report 




--
Kind Regards,
SSA Noel Butler
L.C.P <http://counter.li.org>  No. 251002 

  _____  


This Email, including any attachments, may contain legally privileged
information, therefore remains confidential and subject to copyright
protected under international law. You may not disseminate or reveal any
part to anyone without the authors express written authority to do so. If
you are not the intended recipient, please notify the sender and delete all
relevance of this message including any attachments, immediately.
Confidentiality, copyright, and legal privilege are not waived or lost by
reason of the mistaken delivery of this message. Only PDF
<http://www.adobe.com/>  and ODF <http://en.wikipedia.org/wiki/OpenDocument>
documents are accepted, do not send Microsoft proprietary formatted
documents.

  _____  


-- 
This message has been scanned for viruses and 
dangerous content by  <http://www.mailscanner.info/> MailScanner, and is 
believed to be clean. 

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.mailscanner.info/pipermail/mailscanner/attachments/20100215/41c475e1/attachment.html