Re: Custom rules working, but not sa-updates

o. ;-) 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 is

Re: Custom rules working, but not sa-updates

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

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

Re: How do I whitelist this list?

-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/s

Re: How do I whitelist this list?

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 thi

yet more whitelisting clarification...

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

WhiteListing question

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, A

Re: whitelist frustrations

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

whitelist frustrations

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 tiresw

RE: Unsubscribe?

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

RE: need a rule to whitelist spamassassin users group

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 t

RE: need a rule to whitelist spamassassin users group

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

Re: need a rule to whitelist spamassassin users group

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 >

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

Re: connection to spamd refused...

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

connection to spamd refused...

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 f

Bayes... lint

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 ma

Re: BayesStore.pm

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.

BayesStore.pm

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

2.64 -> 3.0.1 (and Bayes) Help

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

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"

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

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

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

Install 3.0 issue

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, N

Whitelisting question

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

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