Re: Custom rules working, but not sa-updates

[Andy Norris]

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

[Andy Norris]

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

[Andy Norris]

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"  
<[EMAIL PROTECTED]> 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:[EMAIL PROTECTED]
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:[EMAIL PROTECTED]
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: How do I whitelist this list?

[Andy Norris]

Sorry about the oversite. I saw this email this morning after a 
not-very-good night's sleep at a motel. Struck close to my heart, as I just 
could not get the whitelist_from_rcvd to work on my box. Very frustrating, 
and a lot of time spent. I finally resorted to the MailScanner way. But I'm 
tuned in to this thread for anyone what wants to help him figure out the 
whitelist_from_rcvd trick. I haven't gotten any phishing attacks the way 
I've got it now, but want to do the whitelist_from_rcvd for some of the 
mail that comes through.

Game on!
Andy
At 09:33 am 2005-03-22, Martin Hepworth wrote:
Andy
Robert uses procmail and spamd/spamc so your MailScanner setup (and mine!) 
won't work.

--
Martin Hepworth
Snr Systems Administrator
Solid State Logic
Tel: +44 (0)1865 842300
Andy Norris wrote:
Hi Robert,
I put this in the (on my machine) 
/etc/MailScanner/rules/spam.whitelist.rules:
From:   jiscmail.ac.uk  yes # MailScanner mailing list
From:   spamassassin.apache.org yes # SpamAssassin mailing list
Those are tabs, and not spaces.
I tried a bunch of other things... but this works on our server.
Have a great day,
Andy

At 08:20 am 2005-03-22, Robert Markin wrote:
Hey everybody,
RH9
SA 3.0.0 (invoked by procmail spamc/spamd)
Sendmail 8
Procmail
I tried to search for this on GMANE but was unsuccessful.
I would like to know how some of you guys are whitelisiting this actual 
mailing list.  I have the following in my local.cf, but I still get 
quite a few emails tagged mostly because of the "cut & paste" content.


whitelist_from [EMAIL PROTECTED]
whitelist_from [EMAIL PROTECTED]
whitelist_from mail.apache.org
whitelist_from_rcvd [EMAIL PROTECTED]
whitelist_from_rcvd [EMAIL PROTECTED]
whitelist_from_rcvd mail.apache.org

I find that it make the list a little hard to follow when a portion of 
the responses go into my spam trap.

Any help would be appreciated,
Robert
**
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.
This footnote confirms that this email message has been swept
for the presence of computer viruses and is believed to be clean.
**

Re: How do I whitelist this list?

[Andy Norris]

Hi Robert,
I put this in the (on my machine) /etc/MailScanner/rules/spam.whitelist.rules:
From:   jiscmail.ac.uk  yes # MailScanner mailing list
From:   spamassassin.apache.org yes # SpamAssassin mailing list
Those are tabs, and not spaces.
I tried a bunch of other things... but this works on our server.
Have a great day,
Andy
At 08:20 am 2005-03-22, Robert Markin wrote:
Hey everybody,
RH9
SA 3.0.0 (invoked by procmail spamc/spamd)
Sendmail 8
Procmail
I tried to search for this on GMANE but was unsuccessful.
I would like to know how some of you guys are whitelisiting this actual 
mailing list.  I have the following in my local.cf, but I still get quite 
a few emails tagged mostly because of the "cut & paste" content.


whitelist_from [EMAIL PROTECTED]
whitelist_from [EMAIL PROTECTED]
whitelist_from mail.apache.org
whitelist_from_rcvd [EMAIL PROTECTED]
whitelist_from_rcvd [EMAIL PROTECTED]
whitelist_from_rcvd mail.apache.org

I find that it make the list a little hard to follow when a portion of the 
responses go into my spam trap.

Any help would be appreciated,
Robert

yet more whitelisting clarification...

[Andy Norris]

The following mail headers show that the message was flagged as spam. But I 
have been trying oh so hard to get the mail to the spamassassin users list 
and the mailscanner users list whitelisted. Any help is appreciated. 
Thanks, Andy

I have this in a file "TS_WhiteList.cf" in my rules directory (I know this 
directory is being read through --lint -D):

whitelist_from_rcvd  [EMAIL PROTECTED]  apache.org
I have these headers to work with:
X-ClientAddr: 209.237.227.199
Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm
list-help: 
list-unsubscribe: 
list-post: 
List-Id: 
Delivered-To: mailing list users@spamassassin.apache.org
X-ASF-Spam-Status: No, hits=0.1 required=10.0
tests=HTML_30_40,HTML_MESSAGE,HTML_TITLE_EMPTY
X-Spam-Check-By: apache.org
X-IronPort-AV: i="3.90,94,1107752400";
   d="p7s'?scan'208,217"; a="5686655:sNHT85450912"
Date: Thu, 17 Feb 2005 11:58:04 -0500
From: Thomas Bolioli <[EMAIL PROTECTED]>
User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206)
X-Accept-Language: en-us, en
To: SpamAssassin Users 
Subject: [SPAM] Re: surbl not reporting on any incoming email
X-Virus-Checked: Checked
X-TireSwing-MailScanner-Information: Please contact the ISP for more 
information
X-TireSwing-MailScanner: Found to be clean
X-TireSwing-MailScanner-SpamCheck: spam, SpamAssassin (score=6.67,
required 5, HTML_30_40 1.00, HTML_MESSAGE 1.00,
HTML_MISSING_CTYPE 1.00, HTML_TITLE_EMPTY 1.00,
SARE_HTML_NO_BODY1 1.67, SB_NSP_VOLUME_SPIKE 1.00)
X-TireSwing-MailScanner-SpamScore: 6
X-MailScanner-From: 
[EMAIL PROTECTED]

WhiteListing question

[Andy Norris]

Hi,
I have some email coming through with v3.0.1 that has high scores but the 
report says whitelisted. I've looked in 60_whitelist.cf and my own rules 
file and don't see any rules that would whitelist these emails. Is there 
any way to get the report to describe WHY it was whitelisted?

Thanks,
Andy

Re: whitelist frustrations

[Andy Norris]

Thanks Alan,
I'm running spamassassin through MailScanner. So I'm not running spamd. Is 
this a wrinkle in the scheme of things?

Andy
At 11:25 pm 2004-12-23, alan premselaar wrote:
Andy Norris wrote:
Okay, if someone's feeling really holiday generous, maybe they can help 
me out here... I'm having some problems whitelisting some mailing lists 
(this one, for instance!) and some other mail...
As an example, I have these headers:
X-Persona: 
Return-Path: <[EMAIL PROTECTED]>
Received: from tireswing.arsalon.net ([EMAIL PROTECTED])
by tireswing.net (8.12.10/8.12.10) with ESMTP id iBNM59rw022817
for <[EMAIL PROTECTED]>; Thu, 23 Dec 2004 16:05:09 -0600
X-ClientAddr: 63.146.24.84
Received: from ezwsmtp03.xm-radio.com (ezwsmtp03.xm-radio.com [63.146.24.84])
by tireswing.arsalon.net (8.12.10/8.12.10) with ESMTP id iBNM4ZMN022796
for <[EMAIL PROTECTED]>; Thu, 23 Dec 2004 16:04:35 -0600
Received: from CAMPAIGN ([63.146.24.84]) by ezwsmtp03.xm-radio.com with 
Microsoft SMTPSVC(5.0.2195.5329);
Thu, 23 Dec 2004 16:54:55 -0500
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Message-Id: <[EMAIL PROTECTED]>
Subject: [SPAM] XM Signal - Your Guide to XM On and Off the Air
Date: Thu, 23 Dec 2004 16:54:55 -0500
MIME-Version: 1.0
Reply-To: [EMAIL PROTECTED]
Content-Type: multipart/alternative; boundary="Boundary.."
X-OriginalArrivalTime: 23 Dec 2004 21:54:55.0382 (UTC) 
FILETIME=[09BAAB60:01C4E93A]
X-TireSwing-MailScanner-Information: Please contact the ISP for more 
information
X-TireSwing-MailScanner: Found to be clean
X-TireSwing-MailScanner-SpamCheck: spam, SpamAssassin (score=7.244,
required 5, autolearn=disabled, BODY_BLAMES_YOU_1 1.11,
BODY_OBFU_SEX 2.12, HTML_70_80 1.00, HTML_MESSAGE 1.00,
HTML_MISSING_CTYPE 1.00, URI_DEAL_ADJ 1.01)
X-TireSwing-MailScanner-SpamScore: sss
X-MailScanner-From: [EMAIL PROTECTED]

I want to add this to the whitelist. So I have this rule in a custom rule 
set (I KNOW these rules should be firing, as some of the other rules in 
this file are hitting on test messages):
whitelist_from_rcvd  [EMAIL PROTECTED]  ezwsmtp03.xm-radio.com
What am I doing wrong here? This rule is completely ignored.
Thanks for any guidance, and happy holidays,
Andy
Andy,
  how are you calling SpamAssassin from sendmail?  does it get called 
when the message is originally received from the remote host, or does it 
get called after the message is passed back to the localhost?

Have you tried running 'spamassassin -D < that_message' (no quotes)?
that should give you some pretty useful debug information.
the one thing I can think of off the top of my head (although I'm not sure 
about it) is that if it's getting called after the message is passed back 
into your SMTP server, perhaps spamassassin is thinking that the message 
is being delivered via localhost instead of ezwsmtp03.xm-radio.com and 
therefore not meeting the criteria requirements of that whitelist 
entry.  Like I said, I haven't tested this theory... just an idea off the 
top of my head.

hope this helps
alan

whitelist frustrations

[Andy Norris]

Okay, if someone's feeling really holiday generous, maybe they can help me 
out here... I'm having some problems whitelisting some mailing lists (this 
one, for instance!) and some other mail...

As an example, I have these headers:
X-Persona: 
Return-Path: <[EMAIL PROTECTED]>
Received: from tireswing.arsalon.net ([EMAIL PROTECTED])
	by tireswing.net (8.12.10/8.12.10) with ESMTP id iBNM59rw022817
	for <[EMAIL PROTECTED]>; Thu, 23 Dec 2004 16:05:09 -0600
X-ClientAddr: 63.146.24.84
Received: from ezwsmtp03.xm-radio.com (ezwsmtp03.xm-radio.com [63.146.24.84])
	by tireswing.arsalon.net (8.12.10/8.12.10) with ESMTP id iBNM4ZMN022796
	for <[EMAIL PROTECTED]>; Thu, 23 Dec 2004 16:04:35 -0600
Received: from CAMPAIGN ([63.146.24.84]) by ezwsmtp03.xm-radio.com with 
Microsoft SMTPSVC(5.0.2195.5329);
	Thu, 23 Dec 2004 16:54:55 -0500
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Message-Id: <[EMAIL PROTECTED]>
Subject: [SPAM] XM Signal - Your Guide to XM On and Off the Air
Date: Thu, 23 Dec 2004 16:54:55 -0500
MIME-Version: 1.0
Reply-To: [EMAIL PROTECTED]
Content-Type: multipart/alternative; boundary="Boundary.."
X-OriginalArrivalTime: 23 Dec 2004 21:54:55.0382 (UTC) 
FILETIME=[09BAAB60:01C4E93A]
X-TireSwing-MailScanner-Information: Please contact the ISP for more 
information
X-TireSwing-MailScanner: Found to be clean
X-TireSwing-MailScanner-SpamCheck: spam, SpamAssassin (score=7.244,
	required 5, autolearn=disabled, BODY_BLAMES_YOU_1 1.11,
	BODY_OBFU_SEX 2.12, HTML_70_80 1.00, HTML_MESSAGE 1.00,
	HTML_MISSING_CTYPE 1.00, URI_DEAL_ADJ 1.01)
X-TireSwing-MailScanner-SpamScore: sss
X-MailScanner-From: [EMAIL PROTECTED]


I want to add this to the whitelist. So I have this rule in a custom rule 
set (I KNOW these rules should be firing, as some of the other rules in 
this file are hitting on test messages):

whitelist_from_rcvd  [EMAIL PROTECTED]  ezwsmtp03.xm-radio.com
What am I doing wrong here? This rule is completely ignored.
Thanks for any guidance, and happy holidays,
Andy

RE: Unsubscribe?

[Andy Norris]

Happens all the time at all levels of gov't. And maybe worse with DOD 
stuff. I've worked with small government and DOD contractors. When it comes 
to Perl v. $30,000 the $30,000 wins. Or MySQL v. Microsofts SQL Server... 
Microsoft wins.

A combination of "not my money", and nobody wanting to put their neck out 
to make a decision. Easier to write the million-dollar checks and forget 
about it... Very troubling.

Sorry to venture further into the OT... :-) But, as a programmer who 
primarily works to integrate top-heavy, kludgy and expensive products... 
it's disheartening to say the least.

Andy
At 02:32 pm 2004-12-21, Peter P. Benac wrote:
If I understand you Mail Address correct aren't the Tax Payers the ones
paying the bills.  While I don't live in your County or State I would have
to wonder why the people you work for NEED to spend the taxpayers money on
something they already have for free.
Don't they have a better way of spending the money like maybe on Education,
Law Enforcement, EMS Services, or Fire Services... Just a thought!!
Regards,
Pete

Peter P. Benac, CCNA
Celtic Spirit Network Solutions
Providing Network and Systems Project Management and Installation and Web
Hosting.
Phone: 919-618-2557
Web: http://www.emacolet.com
Need quick reliable Systems or Network Management advice visit
http://www.nmsusers.org
To have principles...
 First have courage.. With principles comes integrity!!!

-Original Message-
From: William Holman [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 21, 2004 15:08
To: users@spamassassin.apache.org
Subject: Unsubscribe?
I've been over-ruled by those who pay the bills, so I can't use SpamAssassin
since it's "open source"
How do I unsubscribe from the lists?
Thank-you!

RE: need a rule to whitelist spamassassin users group

[Andy Norris]

In that case, this leads to another question -- how, then, to reliably 
whitelist eBay? I would imagine they are a big target of forgers? I tried

def_whitelist_from_rcvd  [EMAIL PROTECTED]  ebay.com
but that didn't work. Now I just have
whitelist_from  [EMAIL PROTECTED]  yes
With IP addresses is there a greater chance of the server (theirs) 
crashing, and now the whitelist doesn't account for the backup mail server? 
Or if a company uses more than one mail server... getting all the IPs? Is 
this just something I should email support at eBay for and see if they've 
got something of a canned response for this?

Any ideas why my first whitelist_from_rcvd rule might not have worked? It's 
in a custom rules file I have (TireSwing.cf)... I linted, and all seemed fine??

Thanks,
Andy
At 11:32 am 2004-12-14, Rob McEwen wrote:
Wouldn't the best options be to whitelist the sending server's IP address
(209.237.227.199).
"FROM" values can be forged, both in the e-mail and in the SMTP envelope.
(Of course, we'd be in big trouble if the apache server were hacked or virus
infected... but I'm assuming that the security there is top notch...)
Rob McEwen

RE: need a rule to whitelist spamassassin users group

[Andy Norris]

thanks Candee,
I will do this for now,
Andy
At 10:14 am 2004-12-14, you wrote:
whitelist_tousers@spamassassin.apache.org
Will do it.
-Original Message-
From: Andy Norris [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 14, 2004 10:47 AM
To: users@spamassassin.apache.org
Subject: need a rule to whitelist spamassassin users group
As the subject implies... what would be a good rule to use to make sure
all this talk about spam doesn't end up in my spam trap?
(I also need to whitelist the mailscanner list messages.)
I'm just cutting my teeth on the rules writing gig. My first was to get
all those jackrabb1t vlbrat0r5 out of my inbox ;-)

Thanks very much,
Andy

Re: need a rule to whitelist spamassassin users group

[Andy Norris]

More to learn for me. I need to figure out how, then, not to pass list mail 
through the scanner.

Thanks,
Andy
At 10:17 am 2004-12-14, you wrote:
On Tuesday 14 December 2004 15:46, Andy Norris might have typed:
> As the subject implies... what would be a good rule to use to make sure all
> this talk about spam doesn't end up in my spam trap?
Don't pass list mail through your scanning engine.  Best whitelist there is,
and it won't poison your Bayes.

need a rule to whitelist spamassassin users group

[Andy Norris]

As the subject implies... what would be a good rule to use to make sure all 
this talk about spam doesn't end up in my spam trap?

(I also need to whitelist the mailscanner list messages.)
I'm just cutting my teeth on the rules writing gig. My first was to get all 
those jackrabb1t vlbrat0r5 out of my inbox ;-)

Thanks very much,
Andy

Re: connection to spamd refused...

[Andy Norris]

My understanding is that spamd should not be running when spamassassin is 
used in conjunction with MailScanner as MailScanner uses spamassassin 
directly, and not as a daemon?

So is this a MailScanner issue, then?
Thanks Mike,
Andy
At 01:44 pm 2004-12-10, you wrote:
Is spamd running?
On Fri, 10 Dec 2004, Andy Norris wrote:
>
> Sorry to bother again, but I feel we must be getting closer...
>
> This in the logs (/var/log/maillog) now...(!)
>
> Dec 10 13:44:40 tireswing spamc[22597]: connect() to spamd at 127.0.0.1
> failed, retrying (1/3): Connection refused
> Dec 10 13:44:41 tireswing spamc[22597]: connect() to spamd at 127.0.0.1
> failed, retrying (2/3): Connection refused
> Dec 10 13:44:42 tireswing spamc[22597]: connect() to spamd at 127.0.0.1
> failed, retrying (3/3): Connection refused
>
> Any hints what to look for here? This is getting very frustrating, as the
> first few messages are scanned by SA, but after a while it starts to 
either
> time out or refuse connection, then we're at virtually no spam filtering.
>

--
Mike Burger
http://www.bubbanfriends.org
Visit the Dog Pound II BBS
telnet://dogpound2.citadel.org or http://dogpound2.citadel.org
To be notified of updates to the web site, visit
http://www.bubbanfriends.org/mailman/listinfo/site-update, or send a
message to:
[EMAIL PROTECTED]
with a message of:
subscribe

connection to spamd refused...

[Andy Norris]

Sorry to bother again, but I feel we must be getting closer...
This in the logs (/var/log/maillog) now...(!)
Dec 10 13:44:40 tireswing spamc[22597]: connect() to spamd at 127.0.0.1 
failed, retrying (1/3): Connection refused
Dec 10 13:44:41 tireswing spamc[22597]: connect() to spamd at 127.0.0.1 
failed, retrying (2/3): Connection refused
Dec 10 13:44:42 tireswing spamc[22597]: connect() to spamd at 127.0.0.1 
failed, retrying (3/3): Connection refused

Any hints what to look for here? This is getting very frustrating, as the 
first few messages are scanned by SA, but after a while it starts to either 
time out or refuse connection, then we're at virtually no spam filtering.

Bayes... lint

[Andy Norris]

bayes: bayes db version 0 is not able to be used, aborting! at 
/usr/lib/perl5/site_perl/5.8.0/Mail/SpamAssassin/BayesStore/DBM.pm line 160.
bayes: bayes db version 0 is not able to be used, aborting! at 
/usr/lib/perl5/site_perl/5.8.0/Mail/SpamAssassin/BayesStore/DBM.pm line 160.

???
Is this a matter of the conf not knowing where to find the Bayes DB?
Trying to weed out the lint... this is a straggler. I'm hoping this is the 
cause of SpamAssassin timing out under MailScanner???

Thanks for any pointers,
Andy

Re: BayesStore.pm

[Andy Norris]

Hi Matt,
Thanks for your help. I did run sa-learn --sync.
Also, where do I find the command line that launches spamd (I'm using 
sendmail)?

Thanks again,
Andy
At 11:52 pm 2004-11-22, Matt Kettler wrote:
At 10:09 PM 11/22/2004 -0600, Andy Norris wrote:
I have attempted to upgrade from 2.64 to 3.0.1, and the service will not 
start. I did pay attention to the upgrade document.

When I attempt to start the service, I get:
Starting spamd: The -a option has been removed. Please look at the 
use_auto_whitelist config option instead.
remove -a from your command line to spamd.
No need to add the config option, it defaults to on, but if you ever need 
to disable it, set use_auto_whitelist 0 in your local.cf.


When I spamassassin --lint, I get:
bayes: bayes db version 0 is not able to be used, aborting! at 
/usr/lib/perl5/site_perl/5.8.0/Mail/SpamAssassin/BayesStore/DBM.pm line 160.
bayes: bayes db version 0 is not able to be used, aborting! at 
/usr/lib/perl5/site_perl/5.8.0/Mail/SpamAssassin/BayesStore/DBM.pm line 160.
run sa-learn --sync, as per the instructions in UPGRADE.

BayesStore.pm

[Andy Norris]

Hi All,
I have attempted to upgrade from 2.64 to 3.0.1, and the service will not 
start. I did pay attention to the upgrade document.

When I attempt to start the service, I get:
Starting spamd: The -a option has been removed. Please look at the 
use_auto_whitelist config option instead.

When I spamassassin --lint, I get:
bayes: bayes db version 0 is not able to be used, aborting! at 
/usr/lib/perl5/site_perl/5.8.0/Mail/SpamAssassin/BayesStore/DBM.pm line 160.
bayes: bayes db version 0 is not able to be used, aborting! at 
/usr/lib/perl5/site_perl/5.8.0/Mail/SpamAssassin/BayesStore/DBM.pm line 160.

Thanks for light anyone can shed on this situation for me!
Andy Norris

2.64 -> 3.0.1 (and Bayes) Help

[Andy Norris]

Hi All,
If this is in a FAQ or in the history, please point me to it, ridicule me, 
and go on about your day. :-)

We have a Linux server running Ensim. We had SpamAssassin 2.60. Upgraded to 
2.64. Then we tried to upgrade to 3.0.0. SpamAssassin would not start. (I 
did the Bayes sa-learn stuff in the Upgrade file.) We went back to 2.6.4, 
and Bayes was broken at that point. This was over a month ago.

As of Wednesday, we started noticing a lot of resources going to spamd 
processes. We had not added any new rule sets or changed anything in the 
previous week, so we have been very perplexed with this behavior on our server.

What we would absolutely love to do is have a clean install of 3.0.1 with 
Bayes functioning properly.

If anyone has suggestions, or has been through this and survived, we would 
be very interested in learning from you.

Thanks very much,
Andy Norris 

2.64 -> 3.0.1 (and Bayes) Help

[Andy Norris]

Hi All,
If this is in a FAQ or in the history, please point me to it, ridicule me, 
and go on about your day. :-)

We have a Linux server running Ensim. We had SpamAssassin 2.60. Upgraded to 
2.64. Then we tried to upgrade to 3.0.0. SpamAssassin would not start. (I 
did the Bayes sa-learn stuff in the Upgrade file.) We went back to 2.6.4, 
and Bayes was broken at that point. This was over a month ago.

As of Wednesday, we started noticing a lot of resources going to spamd 
processes. We had not added any new rule sets or changed anything in the 
previous week, so we have been very perplexed with this behavior on our server.

What we would absolutely love to do is have a clean install of 3.0.1 with 
Bayes functioning properly.

If anyone has suggestions, or has been through this and survived, we would 
be very interested in learning from you.

Thanks very much,
Andy Norris

RE: Install 3.0 issue // "-a option has been removed"

[Andy Norris]

Well, I wanted to thank everyone for their help. I've rolled our 
installation back to 2.64, and I think we'll wait until 3.1 or so... 
Hopefully it will be a bit more straightforward in the upgrade process?

Thanks again,
Andy Norris
At 01:14 am 2004-09-27, Andy Norris wrote:
The good news: That worked! We've got version 3.0.0 on our machine. Thanks 
very much for your help!

The bad news: Starting spamd: The -a option has been removed.  Please look 
at the use_auto_whitelist config option instead.

Starting spamassassin fails.
I should know better than to start something like this late late. It's 
just not going to go smoothly.

Thanks again,
Andy Norris

At 12:16 am 2004-09-27, Michele Neylon :: Blacknight Solutions wrote:
Andy Norris wrote:
> Hi,
>
> While attempting to install 3.0 via MCPAN, everything seemed to go
> okay until:
>
> Makefile:54: *** missing separator. Stop.
>/usr/bin/make  -- NOT OK
> Running make test
>Can't test without successful make
> Running make install
>make had returned bad status, install seems impossible
>
> Now, I know, NOTHING's impossible.
>
> If this is beyond the scope of this list, I understand. But
> if anyone has any tips, I'm all ears. We're at 2.64 right now.
>
> Thanks,
>
> Andy
Type this before running MCPAN:
export LANG=C
Michele
Mr Michele Neylon
Blacknight Internet Solutions Ltd
Hosting, co-location & domains
http://www.blacknight.ie/
Tel. +353 59 9137101
--
Email scanned by Blacknight for viruses and dangerous content.
Visit http://www.blacknight.ie for more information

RE: Install 3.0 issue // "-a option has been removed"

[Andy Norris]

The good news: That worked! We've got version 3.0.0 on our machine. Thanks 
very much for your help!

The bad news: Starting spamd: The -a option has been removed.  Please look 
at the use_auto_whitelist config option instead.

Starting spamassassin fails.
I should know better than to start something like this late late. It's just 
not going to go smoothly.

Thanks again,
Andy Norris

At 12:16 am 2004-09-27, Michele Neylon :: Blacknight Solutions wrote:
Andy Norris wrote:
> Hi,
>
> While attempting to install 3.0 via MCPAN, everything seemed to go
> okay until:
>
> Makefile:54: *** missing separator. Stop.
>/usr/bin/make  -- NOT OK
> Running make test
>Can't test without successful make
> Running make install
>make had returned bad status, install seems impossible
>
> Now, I know, NOTHING's impossible.
>
> If this is beyond the scope of this list, I understand. But
> if anyone has any tips, I'm all ears. We're at 2.64 right now.
>
> Thanks,
>
> Andy
Type this before running MCPAN:
export LANG=C
Michele
Mr Michele Neylon
Blacknight Internet Solutions Ltd
Hosting, co-location & domains
http://www.blacknight.ie/
Tel. +353 59 9137101
--
Email scanned by Blacknight for viruses and dangerous content.
Visit http://www.blacknight.ie for more information

Install 3.0 issue

[Andy Norris]

Hi,
While attempting to install 3.0 via MCPAN, everything seemed to go okay until:
Makefile:54: *** missing separator. Stop.
  /usr/bin/make  -- NOT OK
Running make test
  Can't test without successful make
Running make install
  make had returned bad status, install seems impossible
Now, I know, NOTHING's impossible.
If this is beyond the scope of this list, I understand. But if anyone has 
any tips, I'm all ears. We're at 2.64 right now.

Thanks,
Andy

Whitelisting question

[Andy Norris]

We're migrating from one server to another. Both now have the same versions 
of SpamAssassin (2.64) and MailScanner running.

We had all our whitelisting on the old server going on in 
/etc/MailScanner/rules/spam.whitelist.rules.

Those listed in that file on our new server are not being recognized. I've 
restarted the spamd service, and have even rebooted.

I am adding those listings on the new server to the file 
/usr/share/spamassassin/60_whitelist.cf. I'm pulling at straws at this 
point as people having their newsletters flagged as spam get madder at me 
day by day!

Am I on the right path, or is there a secret I should know -- a gotcha -- 
that would make one install of the same version on the same OS (RedHat) so 
vastly different from one server to another?

Thanks very much,
Andy Norris

Upgrading 2.55 -> 2.64

[Andy Norris]

Sorry if this is old news, but we just got on a new dedicated server, and 
it's stuck at v2.55. Our old server had 2.64, and some of our settings 
didn't make it over in the move.

Please point me in the right direction for upgrading to 2.64. We're running 
Redhat with an Ensim control panel.

Your help is greatly appreciated,
Andy