bayes 101
I just did an install of spampd on my debian box and am working my way through the different configurations... First, I found that /var/cache/spampd/awl had the wrong permissions so I changed that and I stopped getting errors. Interestingly, I have AWL disabled. But I guess it likes to check anyways. That seems reasonable. Second, I enabled bayes with bayes_auto_learn also enabled. Nothing else just yet. I'm not into the per-user stuff or anything like that (won't work with spampd anyways). But I'm not seeing anything in the system logs to indicate that anything bayes-ish is going on. I can't yet check the actual message because I'm still running it between dummy stubs (postfix smtp-source and smtp-sink). But I haven't anything in /var/cache/spampd/bayes which is what my bayes_path is set to. I realize I can't get anything working until I get to a couple hundred emails, but I should see the database file in this directory, right?
Re: bayes 101
Tom Allison wrote: I just did an install of spampd on my debian box and am working my way through the different configurations... First, I found that /var/cache/spampd/awl had the wrong permissions so I changed that and I stopped getting errors. Interestingly, I have AWL disabled. But I guess it likes to check anyways. That seems reasonable. [5411] info: config: SpamAssassin failed to parse line, /var/cache/spampd/bayes is not valid for bayes_path, skipping: bayes_path /var/cache/spampd/bayes debug helped. But what does it mean?
Re: bayes 101
Tom Allison wrote: Tom Allison wrote: I just did an install of spampd on my debian box and am working my way through the different configurations... First, I found that /var/cache/spampd/awl had the wrong permissions so I changed that and I stopped getting errors. Interestingly, I have AWL disabled. But I guess it likes to check anyways. That seems reasonable. [5411] info: config: SpamAssassin failed to parse line, /var/cache/spampd/bayes is not valid for bayes_path, skipping: bayes_path /var/cache/spampd/bayes debug helped. But what does it mean? Is there a directory named /var/cache/spampd/bayes/? If so, remove it, or change your bayes_path to /var/cache/spampd/bayes/bayes bayes_path, despite it's name, is NOT a path. It's a path AND partial filename.
Re: bayes 101
Matt Kettler wrote: Tom Allison wrote: Tom Allison wrote: I just did an install of spampd on my debian box and am working my way through the different configurations... First, I found that /var/cache/spampd/awl had the wrong permissions so I changed that and I stopped getting errors. Interestingly, I have AWL disabled. But I guess it likes to check anyways. That seems reasonable. [5411] info: config: SpamAssassin failed to parse line, /var/cache/spampd/bayes is not valid for bayes_path, skipping: bayes_path /var/cache/spampd/bayes debug helped. But what does it mean? Is there a directory named /var/cache/spampd/bayes/? If so, remove it, or change your bayes_path to /var/cache/spampd/bayes/bayes bayes_path, despite it's name, is NOT a path. It's a path AND partial filename. !DSPAM:45b38a7c119741622578420! OK, I removed the bayes directory such that /var/cache/spampd is a directory but there is nothing 'bayes' in that directory (no file, no dir) cd /var/cache/spampd rm -rf bayes /etc/spampd.conf: bayes_path /var/cache/spampd/bayes restart and [6651] dbg: bayes: no dbs present, cannot tie DB R/O: /var/cache/spampd/bayes_toks Looks like I'm either missing permissions or it doesn't want to create this file. Permissions are set to: /var/cache/spampd# ls -la total 20 drwxrwxr-x 2 spampd spampd 4096 2007-01-21 11:36 . drwxr-xr-x 16 root root4096 2007-01-21 10:01 .. -rw--- 1 spampd spampd 12288 2007-01-21 10:27 awl and the /var/cache/spampd directory has: drwxrwxr-x 2 spampd spampd 4096 2007-01-21 11:36 spampd From what I get out of Mail::SpamAssassin::Conf the bayes_path setting for this configuration is correct. but I'm not seeing the _toks, _seen files getting generated. grr..
Re: bayes 101
On Sunday 21 January 2007 16:44, Matt Kettler wrote: Tom Allison wrote: [5411] info: config: SpamAssassin failed to parse line, /var/cache/spampd/bayes is not valid for bayes_path, skipping: bayes_path /var/cache/spampd/bayes debug helped. But what does it mean? Is there a directory named /var/cache/spampd/bayes/? If so, remove it, or change your bayes_path to /var/cache/spampd/bayes/bayes Should that really be a problem? The bayes module should be able to use /var/cache/spampd/bayes_* despite the directory /var/cache/spampd/bayes being there. Would it be a bad idea to change the code such that bayes_path can optionally name a directory? Either by including a trailing slash or by there actually being a directory with the name in question. In these cases the files would simply be called toks, seen, and journal, without a prefix. -- Magnus Holmgren[EMAIL PROTECTED] (No Cc of list mail needed, thanks) Exim is better at being younger, whereas sendmail is better for Scrabble (50 point bonus for clearing your rack) -- Dave Evans pgp99XBTFCPmS.pgp Description: PGP signature
unofficial SpamAssassin 3.2.0 not-a-prerelease tarball available
Hi all -- there's an extremely unofficial SpamAssassin 3.2.0 tarball available at: http://people.apache.org/~jm/devel/Mail-SpamAssassin-3.2.0-pre1.tar.bz2 http://people.apache.org/~jm/devel/Mail-SpamAssassin-3.2.0-pre1.tar.gz http://people.apache.org/~jm/devel/Mail-SpamAssassin-3.2.0-pre1.zip md5sum of archive files: 67b0b64d4a4023ccf62d8a79e12a1965 Mail-SpamAssassin-3.2.0-pre1.tar.bz2 958bf78ae2f94a5e7f0df8253f87a08f Mail-SpamAssassin-3.2.0-pre1.tar.gz c933a39d166e66f8bc0d960a3a281505 Mail-SpamAssassin-3.2.0-pre1.zip sha1sum of archive files: cd0427c52ae0d8a5abde15fc3775d6505936fc8a Mail-SpamAssassin-3.2.0-pre1.tar.bz2 46dd38b0667ffbb0c91dbae5a8d80c40a0c3b79d Mail-SpamAssassin-3.2.0-pre1.tar.gz 77d16f8c73fc5e1c19be24ee542c14739ca8b22f Mail-SpamAssassin-3.2.0-pre1.zip This is *not* an official release -- or even a prerelease -- but it'll be similar to the code we will be running the mass-checks with, later this week. If you'd like to try it out, that'd be great... thanks! As usual, upgrade notes can be found in the INSTALL and UPGRADE files in the distribution. --j.
Re: bayes 101
OK, I removed the bayes directory such that /var/cache/spampd is a directory but there is nothing 'bayes' in that directory (no file, no dir) cd /var/cache/spampd rm -rf bayes /etc/spampd.conf: bayes_path /var/cache/spampd/bayes restart and [6651] dbg: bayes: no dbs present, cannot tie DB R/O: /var/cache/spampd/bayes_toks Looks like I'm either missing permissions or it doesn't want to create this file. Permissions are set to: /var/cache/spampd# ls -la total 20 drwxrwxr-x 2 spampd spampd 4096 2007-01-21 11:36 . drwxr-xr-x 16 root root4096 2007-01-21 10:01 .. -rw--- 1 spampd spampd 12288 2007-01-21 10:27 awl and the /var/cache/spampd directory has: drwxrwxr-x 2 spampd spampd 4096 2007-01-21 11:36 spampd From what I get out of Mail::SpamAssassin::Conf the bayes_path setting for this configuration is correct. but I'm not seeing the _toks, _seen files getting generated. grr.. as the user in question, try 'sa-learn --sync' Gary V _ Laugh, share and connect with Windows Live Messenger http://clk.atdmt.com/MSN/go/msnnkwme002001msn/direct/01/?href=http://imagine-msn.com/messenger/launch80/default.aspx?locale=en-ussource=hmtagline
Header processsing not working.
I seem to have a problem processing headers in spamassassin. First, on every single mail I receive, i get a MISSING_SUBJECT condition, and the mail does have a valid subject. Second, I can never make a match in the subject line. In the local.cf, I have the following: ... header HEALTH_SUBJSubject =~ /health/i describe HEALTH_SUBJSubject contains health score HEALTH_SUBJ 3 body HEALTH_BDY/health/i describe HEALTH_BDYbody contains health score HEALTH_BDY 2.5 ... When receiving a mail with the word health in the subject, I do not get a match on HEALTH_SUBJ, however, I do get a match on HEALTH_BDY, even though the word only appears in the subject line, not in the message body. Am I severely misunderstanding something ? Such as definitions of header (subject) and body ? The Scenario here is SuSE 10. SpamAssassin is 3.1.7 (initially tested with 3.1.1, same result). SpamAssassin is invoked from postfix 2.2.10 via amavisd-new 2.4.0. Any help highly appreciated - tnx in advance. Regards Joern W. Andersen
Re: Header processsing not working.
On Sun, Jan 21, 2007 at 09:30:48PM +0100, J. W. Andersen wrote: Am I severely misunderstanding something ? Such as definitions of header (subject) and body ? It sounds more like your system isn't properly passing the message to SA. The Scenario here is SuSE 10. SpamAssassin is 3.1.7 (initially tested with 3.1.1, same result). SpamAssassin is invoked from postfix 2.2.10 via amavisd-new 2.4.0. Test using the spamassassin script. If it works there, your problem is not SA related. -- Randomly Selected Tagline: I think animal testing is a terrible idea; they get all nervous and give the wrong answers.- Unknown pgpN33U2KTbIT.pgp Description: PGP signature
Re: Header processsing not working.
Theo Van Dinter wrote: On Sun, Jan 21, 2007 at 09:30:48PM +0100, J. W. Andersen wrote: Am I severely misunderstanding something ? Such as definitions of header (subject) and body ? It sounds more like your system isn't properly passing the message to SA. As all my body tests seem to work OK, I guess the messages *are* passed to SA. Unless there is reason to believe, that postfix or amavis should block the header part, and let body part through ? The Scenario here is SuSE 10. SpamAssassin is 3.1.7 (initially tested with 3.1.1, same result). SpamAssassin is invoked from postfix 2.2.10 via amavisd-new 2.4.0. Test using the spamassassin script. If it works there, your problem is not SA related. I could not find a description of the mentioned test - or the script, for that matter, anywhere. Could you give me some hints ? Regards, Joern
restart from scratch with 3.1.7 ???
Greetings My SA 3.1.7 installs run as user spamd My /home/spamd/.spamassassin directory looks like this -rw--- 1 spamd spamd 5210112 Jan 21 14:25 auto-whitelist -rw--- 1 spamd spamd 60864 Jan 21 14:25 bayes_journal -rw--- 1 spamd spamd 2711552 Jan 21 14:18 bayes_seen -rw--- 1 spamd spamd 5390336 Jan 21 14:18 bayes_toks Now, lately I am getting quite a bit of BAYES_00 hits and from the simple searching and reading I have done it tells me that I may need to start over from scratch as my config was not fully mature at the beginning a year ago and so the AWL probably has some bad info here and there. Should I just stop the spamassassin processes, delete the 4 files above and restart the spamassassin processes and let it go at that, repopulating itself on the fly by itself ??? Or is there a better way? I have populated internal and trusted network with info and AWL is on as is bayes and dns_available is yes Do you need more info? Thanks in advance - rh -- Robert - Abba Communications Computer Internet Services (509) 624-7159 - www.abbacomm.net
Re: Header processsing not working.
On Sun, Jan 21, 2007 at 10:14:51PM +0100, J. W. Andersen wrote: It sounds more like your system isn't properly passing the message to SA. As all my body tests seem to work OK, I guess the messages *are* passed to SA. Unless there is reason to believe, that postfix or amavis should block the header part, and let body part through ? For example, if the first line that SA sees does not look like a mbox/mbx separator or header, SA decides there is no header and everything is body. Test using the spamassassin script. If it works there, your problem is not SA related. I could not find a description of the mentioned test - or the script, for that matter, anywhere. Could you give me some hints ? spamassassin is the commandline perl script that lets you run a message through. ie: spamassassin -D message_file will run a message through in debug mode so you can see what's going on. If you don't have a script called spamassassin installed, then your SA install is broken. -- Randomly Selected Tagline: Quigley's Law: Whoever has any authority over you, no matter how small, will atttempt to use it. pgpFfze9OahOX.pgp Description: PGP signature
debug output
When using Mail::SpamAssassin with new( {debug = 'all'} ) or similar
How do you capture the output from the debug to syslog or other logging file?
I can run it via a command line but if I run Mail::SpamAssassin under a
daemon/fork process similar to Net::Server::PreForkSimple I can't seem to
capture the logging. Any tips?
Re: debug output
On Sun, Jan 21, 2007 at 07:17:14PM -0500, Tom Allison wrote:
When using Mail::SpamAssassin with new( {debug = 'all'} ) or similar
How do you capture the output from the debug to syslog or other logging
file?
Take a look at Mail::SpamAssassin::Logger. ie:
Mail::SpamAssassin::Logger::add(method = 'file', filename = /tmp/foo);
Mail::SpamAssassin::Logger::remove('stderr');
--
Randomly Selected Tagline:
Experience is that marvelous thing that enables you to recognize a
mistake when you make it again.- Unknown
pgpLXGjtdyxJ2.pgp
Description: PGP signature
Re: debug output
Theo Van Dinter wrote:
On Sun, Jan 21, 2007 at 07:17:14PM -0500, Tom Allison wrote:
When using Mail::SpamAssassin with new( {debug = 'all'} ) or similar
How do you capture the output from the debug to syslog or other logging
file?
Take a look at Mail::SpamAssassin::Logger. ie:
Mail::SpamAssassin::Logger::add(method = 'file', filename = /tmp/foo);
Mail::SpamAssassin::Logger::remove('stderr');
Kind of a dumb question...
But call this directly from my main script eg:
Mail::SpamAssassin::Logger::add(method = 'file', filename = '/var/log/syslog')
??
Re: debug output
On Sun, Jan 21, 2007 at 07:43:11PM -0500, Tom Allison wrote: But call this directly from my main script eg: Mail::SpamAssassin::Logger::add(method = 'file', filename = '/var/log/syslog') ?? Yes, but I wouldn't log to the same file that syslog is going to write to... Just use the syslog method for that. -- Randomly Selected Tagline: What if we take you with us? Put you on trial? Zathras not of this time. You take, Zathras die. You leave, Zathras die. Either way, it is bad for Zathras. - B4 Commander Zathras on Babylon 5 (Babylon Squared) pgp2IYs3KDYfo.pgp Description: PGP signature
scan internal email? SA and exchange server?
I can scan incoming spam by MX record on my external box before it gets to exchange.server. I can can outgoing email by setting the external box as smarthost in exchange. How do I scan internal to internal, exchange server only email? It never seems to leave the exchange server. -- Michael Scheidell, CTO SECNAP Network Security / www.secnap.com [EMAIL PROTECTED] / 1+561-999-5000, x 1131 - This email has been scanned and certified safe by SpammerTrap(tm) For Information please see http://www.spammertrap.com -
RE: scan internal email? SA and exchange server?
I can scan incoming spam by MX record on my external box before it gets to exchange.server. I can can outgoing email by setting the external box as smarthost in exchange. How do I scan internal to internal, exchange server only email? It never seems to leave the exchange server. If your clients connect directly to the Exchange server there would be no reason for mail addressed to local recipients to leave the box. -- Michael Scheidell, CTO I imagine you only have two choices. Either install spamassassin on the Exchange server, e.g.: http://www.christopherlewis.com/ESA/ExchangeSpamAssassin.htm http://wiki.apache.org/spamassassin/InstallingOnWindows or configure your clients to use your external box as their outgoing SMTP server (which may or may not be an option depending on how you connect to Exchange). I am guessing this is only an option if your clients are set up as POP3 or IMAP clients. Note that I have no direct experience with Exchange or SA on Windows. The links provided are simply the first two I found. I'm not even certain the ESA_sink scans internal mail. The main point is I only see these two possible solutions. Gary V _ Search for grocery stores. Find gratitude. Turn a simple search into something more. http://click4thecause.live.com/search/charity/default.aspx?source=hmemtagline_gratitudeFORM=WLMTAG
Re: scan internal email? SA and exchange server?
On Sun, 21 Jan 2007 22:00:26 -0500 Michael Scheidell [EMAIL PROTECTED] wrote: I can scan incoming spam by MX record on my external box before it gets to exchange.server. I can can outgoing email by setting the external box as smarthost in exchange. How do I scan internal to internal, exchange server only email? It never seems to leave the exchange server. I believe you would have to be running SA on the Exchange server. Otherwise you would have to send the message off to something external then back in. Have you ever checked out the ESA Sink? http://www.christopherlewis.com/ESA/ExchangeSpamAssassin.htm Don't know if this is what you are looking for or not. I haven't used Exchange in over eight years.
Re: scan internal email? SA and exchange server?
My question is: why would you want to scan internal-only email? Are your users sending spam to other users? If so, have an Acceptable Use Policy that forbids such things and then if it happens you can take appropriate action against your user. On Sun, Jan 21, 2007 at 09:55:12PM -0700, Gary V wrote: I can scan incoming spam by MX record on my external box before it gets to exchange.server. I can can outgoing email by setting the external box as smarthost in exchange. How do I scan internal to internal, exchange server only email? It never seems to leave the exchange server. If your clients connect directly to the Exchange server there would be no reason for mail addressed to local recipients to leave the box. -- Michael Scheidell, CTO I imagine you only have two choices. Either install spamassassin on the Exchange server, e.g.: http://www.christopherlewis.com/ESA/ExchangeSpamAssassin.htm http://wiki.apache.org/spamassassin/InstallingOnWindows or configure your clients to use your external box as their outgoing SMTP server (which may or may not be an option depending on how you connect to Exchange). I am guessing this is only an option if your clients are set up as POP3 or IMAP clients. Note that I have no direct experience with Exchange or SA on Windows. The links provided are simply the first two I found. I'm not even certain the ESA_sink scans internal mail. The main point is I only see these two possible solutions. Gary V _ Search for grocery stores. Find gratitude. Turn a simple search into something more. http://click4thecause.live.com/search/charity/default.aspx?source=hmemtagline_gratitudeFORM=WLMTAG -- Randomly Selected Tagline: It's as easy as 3.1415926535897932384626433832795028841. pgpyvwc3e9NQ9.pgp Description: PGP signature
Re: scan internal email? SA and exchange server?
Sorry for the repeat and response to my own message. Must have skipped over the tail end of Gary's response. Must read more thorough next time. On Mon, 22 Jan 2007 05:02:25 + [EMAIL PROTECTED] wrote: On Sun, 21 Jan 2007 22:00:26 -0500 Michael Scheidell [EMAIL PROTECTED] wrote: I can scan incoming spam by MX record on my external box before it gets to exchange.server. I can can outgoing email by setting the external box as smarthost in exchange. How do I scan internal to internal, exchange server only email? It never seems to leave the exchange server. I believe you would have to be running SA on the Exchange server. Otherwise you would have to send the message off to something external then back in. Have you ever checked out the ESA Sink? http://www.christopherlewis.com/ESA/ExchangeSpamAssassin.htm Don't know if this is what you are looking for or not. I haven't used Exchange in over eight years.
RE: scan internal email? SA and exchange server?
How do I scan internal to internal, exchange server only email? It never seems to leave the exchange server. If your clients connect directly to the Exchange server there would be no reason for mail addressed to local recipients to leave the box. -- Michael Scheidell, CTO I imagine you only have two choices. Either install spamassassin on the Exchange server, e.g.: http://www.christopherlewis.com/ESA/ExchangeSpamAssassin.htm http://wiki.apache.org/spamassassin/InstallingOnWindows or configure your clients to use your external box as their outgoing SMTP server (which may or may not be an option depending on how you connect to Exchange). I am guessing this is only an option if your clients are set up as POP3 or IMAP clients. Note that I have no direct experience with Exchange or SA on Windows. The links provided are simply the first two I found. I'm not even certain the ESA_sink scans internal mail. The main point is I only see these two possible solutions. I suppose there is another (convoluted) way to do it. If your external filter is called filter.example.com you could have users send mail to [EMAIL PROTECTED] instead of [EMAIL PROTECTED] and then (on the filter) rewrite the addresses to [EMAIL PROTECTED] Gary V _ Valentines Day -- Shop for gifts that spell L-O-V-E at MSN Shopping http://shopping.msn.com/content/shp/?ctId=8323,ptnrid=37,ptnrdata=24095tcode=wlmtagline
