Fwd: Re: bug report

Julian Field MailScanner at ecs.soton.ac.uk
Mon Feb 15 09:31:33 GMT 2010

As Noel's posting probably never made it to the list:

-------- Original Message --------
Subject: 	Re: bug report
Date: 	Sun, 14 Feb 2010 17:31:39 +1000
From: 	Noel Butler <noel.butler at ausics.net>
Reply-To: 	MailScanner discussion <mailscanner at lists.mailscanner.info>
To: 	Ying <yingyang at exemail.com.au>, MailScanner discussion 
<mailscanner at lists.mailscanner.info>


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 
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.

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 :)


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 discussion'
>     <mailto:mailscanner at lists.mailscanner.info> 
>     *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 MailScanner, and is
believed to be clean.

-------------- next part --------------
MailScanner mailing list
mailscanner at lists.mailscanner.info

Before posting, read http://wiki.mailscanner.info/posting

Support MailScanner development - buy the book off the website! 

More information about the MailScanner mailing list