gmane.mail.spam.spamassassin.general

Re: Bug in iXhash plugin - fixed version available

Marc Perkel — 2008-12-02T04:08:43

Hi Dirk, I'm not getting any hits on the new version either. Dirk Bonengel wrote:

Re: Custom rules

Jonathan Scott — 2008-12-01T21:55:32

It really could be the problem, I thought my local.cf was readable by world but it's wasn't, after I changed it's user and group everything started working fine. amavis seems to be rather strict on this setting, atleast from my experience. root can still edit it and doesn't save it under root's user when saved. i'd suggest making all SA files amavis user and amavis group. wouldn't surprise me if it cleared it up.

Re: Custom rules

Fabrizio Regalli — 2008-12-01T21:55:33

It works! I sent a mail with www.viapaypal.com in the body: *X-Spam-Flag:* YES *X-Spam-Score:* 13.178 *X-Spam-Level:* ************* *X-Spam-Status:* Yes, score=13.178 tagged_above=undef required=6.31 tests=[BAYES_50=0.001, DKIM_SIGNED=0.001, HTML_MESSAGE=0.001, LOCAL_URI_VIAPAYPAL=5, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, TVD_SPACE_RATIO=2.219, URIBL_BLACK=1.955, URIBL_JP_SURBL=1.501] and the LOCAL_URI_VIAPAYPAL is matched! Theo, in previous version of SA, with spamassassin --lint -D, at the last line I saw the output of the rule (don't remember exact message) Now I can't see it and I thought doesn't work but it really works even if you do not see. Thanks Theo for your clarification. 2008/12/1 Theo Van Dinter apache.org>

Re: Custom rules

Theo Van Dinter — 2008-12-01T21:41:02

What are you expecting to see in "--lint -D" output for this rule? "--lint" generates an internal message which is not going to trigger the rule, so you aren't going to see anything in the "-D" output. Perhaps you want to shove a message through just "spamassassin -D" ?

Re: Custom rules

Fabrizio Regalli — 2008-12-01T21:37:36

Hi Jonathan, nice to hear this. I'm using amavisd-new also. My local.cf is owned by root, but readable from world -rw-r--r-- 1 root root 1304 Dec 1 19:00 local.cf Do you think this is the problem? 2008/12/1 Jonathan Scott xpressamerica.net>

Bug in iXhash plugin - fixed version available

Dirk Bonengel — 2008-12-01T21:33:07

Folks, as some of you already noticed I f... up the last (1.5) release of the iXhash plugin. Plain simple a wrong regular expression practically disables hash #1. I just uploaded a fixed version to ixhash.sf.net that runs the correct RE ( on a modified version of the email's body to circumvent a problem I had with my Perl's regexp engine.) Simple replace your old (1.5) plugin with the new one (1.5.1) and restart/reload SpamAssassin or whatever you use. This really shouldn't have happened. My apologies. Dirk

Re: Custom rules

Fabrizio Regalli — 2008-12-01T21:31:50

No, it gives me nothing. :~# spamassassin --lint :~# 2008/12/1 Joe Vieira clarku.edu>

Re: Custom rules

Jonathan Scott — 2008-12-01T21:28:07

Hi, it could be a number of problems. One big issue I had which took me a while to figure out was that I was using amavisd-new with a user amavis group amavis, if this is what you're using as well, or you are running SA under another user (like maiamailguard or amavis etc) make sure that the spamassassin files have ownership under that user and group, otherwise it won't be able to read those files when it's run. Just a thought. Let me know.

Re: Custom rules

Joe Vieira — 2008-12-01T21:28:08

does spamassassin --lint give you any errors? Joe Fabrizio Regalli wrote:

Custom rules

Fabrizio Regalli — 2008-12-01T21:20:50

Hello. I'm writing my custom rule uri LOCAL_URI_VIAPAYPAL /www\.viapaypal\.com\// score LOCAL_URI_VIAPAYPAL 5.0 (for add five points to e-mail contains www.viapaypal.com into body) I've add it to /etc/mail/spamassassin/local.cf but I can't see it with spamassassin --lint -D (and the rule seem doesn't work) Could someone suggest me something to check for solve this problem? Thanks in advance.

Re: Negative Scoring Rules

Matthias Leisi — 2008-12-01T21:00:58

Ray Jette schrieb: The last line should end in ...Yoder)\b/i

Re: Negative Scoring Rules

Ray Jette — 2008-12-01T20:59:02

Thanks. I changed it.

Re: Negative Scoring Rules

jdow — 2008-12-01T20:52:20

From: "Ray Jette" mestek.com> Sent: Monday, 2008, December 01 12:41 Are you REALLY sure you want the last two characters to he "\i"? The escape on the i might keep the rule from being case insensitive and lead to strange matching requirements to make the rule fire correctly all the time. {^_^}

Re: Auto-whitelist not closing file

Theo Van Dinter — 2008-12-01T20:50:53

The last time this sort of issue came up, it was traced back to a bug in DB_File. Specifically, the untie call would actually not let go of the DB. SA doesn't actually open the database files itself, it lets tie/untie (DB_File) deal with it.

Auto-whitelist not closing file

Dan Barker — 2008-12-01T20:42:05

This issue, apparently, has been a problem for me for several Spamassassin releases, but I just now figured out what may be happening. I've been closing spamd once per hour, just to make it read new local.cf, notice sa-update changes, etc., but occasionally my system can't start new tasks (usually error 0xC0000142, very occasionally 0xC0000005 - This is under Windoze, W2K Server/SP4). Closing/Opening spamd also forces closed all the file handles spamd appears to be abandoning un-closed. I'm currently running SpamAssassin 3.2.5 under Activestate perl 5.8.8.822. It appears that spamd fails to close the file handle to bayes_seen or auto-whitelist when it's done with it. spamd -x -D, filtered on "auto-whitelist" shows: --- 9 line(2) not displayed --- [1504] dbg: auto-whitelist: DB addr list: untie-ing and unlocking [1504] dbg: auto-whitelist: DB addr list: file locked, breaking lock [1504] dbg: locker: safe_unlock: unlink C:\Documents and Settings\dbarker/.spamassassin/auto-whitelist.lock --- 370 line(2) not

Re: Negative Scoring Rules

Ray Jette — 2008-12-01T20:41:14

Sorry about that. I solved it. I forgot the closing ). Thanks again.

Re: Negative Scoring Rules

Ray Jette — 2008-12-01T20:30:37

Re: Sought rules - yerp.org - 403 Forbidden errors

Ned Slider — 2008-12-01T20:11:57

Yes, I've seen that a few times over the last couple days too. Trying again later and they seem to come down fine. I manually check for updates 3 or 4 times per day as and when I'm around.

Sought rules - yerp.org - 403 Forbidden errors

Paul Griffith — 2008-12-01T19:43:09

Greetings, Anyone have any issues getting Jim Mason's sought rules updated from yerp.org? I am running SA 3.0.25 and the last successful update was Nov. 26, 2008. It looks like some bits need to be flipped on. Here is my channel.conf file: sought.rules.yerp.org Here is the error from sa-update: 22699] dbg: channel: found mirror http://yerp.org/rules/stage/ [22699] dbg: channel: selected mirror http://yerp.org/rules/stage [22699] dbg: http: GET request, http://yerp.org/rules/stage/320722012.tar.gz [22699] dbg: http: request failed, retrying: 403 Forbidden: 403 Forbidden

Forbidden

You don't have permission to access /rules/stage/320722012.tar.gz on this server.

Apache/2.2.8 (Ubuntu) DAV/2 SVN/1.4.6 PHP/5.2.4-2ubuntu5.3 with Suhosin-Patch mod_ssl/2.2.8 OpenSSL/0.9.8g Server at yerp.org Port 80

Thanks Paul

Re: Negative Scoring Rules

Karsten Bräckelmann — 2008-12-01T19:40:16

No. Well, it's technically (almost) correct. ;) No, sorry. The ? means "optional". ^^ Since you want to match entire words or phrases only, with word boundaries before and after them always, doing it like this is much easier to read: /\b(Boilers?|Twinflo|Vulcan|Yoder)\b/i Also, this accepts both, Boiler and Boilers, because the s is optional due to the following '?'. If you want the RE to be case insensitive, please note that the i modifier must not be escaped. HTH guenther

Re: [sa-list] Re: [sa-list] Re: Spamd and ipv6

SM — 2008-12-01T18:59:14

By default, spamc connects to 127.0.0.1. On a properly configured network, it will try ::1, then 127.0.0.1. There isn't a switch for all IPv4 and all IPv6 addresses. If you specify the listen on as "::", spamd will listen on all IPv6 addresses. It's actually restricted. If you don't specify an IP address with -A, spamd will disconnect you. You won't be able to specify IPv6 addresses after the -A without the patch. You can either wait for 3.3 to be released or adapt that patch for your version of SpamAssassin. Regards, -sm