Re: GEO IP Truble after upgrade to 3.4.1
You can likely just disable Geo::IP anyway. See
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=6824
On 3/2/2018 1:06 AM, Maurizio Caloro wrote:
Hello together
I have little Geo::IP Trouble
Yesterday i have upgraded Spamassassin to 3.4.1 on debian_version 8.10
3.16.51-3+deb8u1
If i start me service this GeiIP Plugin have some error messages
Mar 02 06:44:15 Servername spamd[22306]: plugin: failed to parse
plugin (from @INC): Can't locate object method "lib_version" via
package "Geo::IP" at
/usr/local/share/perl/5.20.2/Mail/SpamAssassin/Plugin/URILocalBL.pm
line 117.
Mar 02 06:44:15 Servername spamd[22306]: Compilation failed in require
at (eval 102) line 1.
But me version of Geo ::IP are updated
cpan[1]> install Geo::IP
Reading '/root/.cpan/Metadata'
Database was generated on Thu, 01 Mar 2018 22:55:21 GMT
Geo::IP is up to date (1.51).
URILocalBL.pm Line 117
But witch Version of GeoIP Library i have running on me machines ?
# need GeoIP C library 1.6.3 and GeoIP perl API 1.4.4 or later to
avoid messages leaking - Bug 7153
my $gic_wanted = version->parse('v1.6.3');
my $gic_have = version->parse(Geo::IP->lib_version());
my $gip_wanted = version->parse('v1.4.4');
my $gip_have = version->parse($Geo::IP::VERSION);
Thanks for any possible help !
Regards
Mauri
GEO IP Truble after upgrade to 3.4.1
Hello together
I have little Geo::IP Trouble
Yesterday i have upgraded Spamassassin to 3.4.1 on debian_version 8.10
3.16.51-3+deb8u1
If i start me service this GeiIP Plugin have some error messages
Mar 02 06:44:15 Servername spamd[22306]: plugin: failed to parse plugin
(from @INC): Can't locate object method "lib_version" via package "Geo::IP"
at /usr/local/share/perl/5.20.2/Mail/SpamAssassin/Plugin/URILocalBL.pm line
117.
Mar 02 06:44:15 Servername spamd[22306]: Compilation failed in require at
(eval 102) line 1.
But me version of Geo ::IP are updated
cpan[1]> install Geo::IP
Reading '/root/.cpan/Metadata'
Database was generated on Thu, 01 Mar 2018 22:55:21 GMT
Geo::IP is up to date (1.51).
URILocalBL.pm Line 117
But witch Version of GeoIP Library i have running on me machines ?
# need GeoIP C library 1.6.3 and GeoIP perl API 1.4.4 or later to avoid
messages leaking - Bug 7153
my $gic_wanted = version->parse('v1.6.3');
my $gic_have = version->parse(Geo::IP->lib_version());
my $gip_wanted = version->parse('v1.4.4');
my $gip_have = version->parse($Geo::IP::VERSION);
Thanks for any possible help !
Regards
Mauri
RE: Pyzor errors after upgrade
From: Chris cpoll...@embarqmail.com Sent: Monday, September 01, 2014 10:25 PM To: users@spamassassin.apache.org Subject: Pyzor errors after upgrade System is Ubuntu 14.04 LTS I use fetchmail linked with procmail. Once mail is tossed to my other folders what's left is run through SA and tossed either into my Inbox or my Spam folder. Yesterday morning I upgraded to the newest version of Pyzor using this command: pip install --upgrade pyzor Since then I've been seeing this in my syslog: Aug 31 10:02:43 localhost spamd[2645]: pyzor: check failed: internal error, python traceback seen in response Aug 31 10:07:02 localhost spamd[2645]: pyzor: check failed: internal error, python traceback seen in response Aug 31 10:35:38 localhost spamd[2645]: pyzor: check failed: internal error, python traceback seen in response The version of Pyzor shown is: /usr/local/bin/pyzor 0.8.0 Permissions on the ~/.pyzor/servers files and directory is: drwxr-x--- 2 chris chris 4096 Jul 17 09:28 .pyzor -rw-r- 1 chris chris 23 Jul 17 09:28 servers Any assistance would be appreciated even a 2x4 upside the head. I'm not sure how to get to the python traceback that's mentioned. Same thing happened to me a while back. This is in my local.cf: ifplugin Mail::SpamAssassin::Plugin::Pyzor pyzor_path /usr/local/bin/pyzor pyzor_options --homedir /etc/mail/spamassassin endif The --homedir line above solved the problem for me. Not sure why since my permissions seemed to be good too. Be sure to move the 'servers' file to /etc/mail/spamassassin. Chris -- Chris 31.11°N 97.89°W (Elev. 1092 ft) 22:14:39 up 2 days, 18 min, 2 users, load average: 0.05, 0.10, 0.22 Ubuntu 14.04 LTS, kernel 3.13.0-35-generic
Re: Pyzor errors after upgrade
On Mon, 2014-09-01 at 21:17 -0700, John Hardin wrote: On Mon, 1 Sep 2014, Chris wrote: System is Ubuntu 14.04 LTS I use fetchmail linked with procmail. Permissions on the ~/.pyzor/servers files and directory is: drwxr-x--- 2 chris chris 4096 Jul 17 09:28 .pyzor -rw-r- 1 chris chris 23 Jul 17 09:28 servers Are you using this with spamc/spamd, or spamassassin-per-message? If the former, what user is spamd running as? Morning John, I'm using it with spamc which is called by a procmail recipe in my home directory which I would 'assume' makes it being run as user 'chris'. -- Chris 31.11°N 97.89°W (Elev. 1092 ft) 07:34:29 up 2 days, 9:37, 3 users, load average: 0.17, 0.15, 0.12 Ubuntu 14.04 LTS, kernel 3.13.0-35-generic
Re: Pyzor errors after upgrade
On Tue, 2 Sep 2014, Chris wrote: On Mon, 2014-09-01 at 21:17 -0700, John Hardin wrote: On Mon, 1 Sep 2014, Chris wrote: System is Ubuntu 14.04 LTS I use fetchmail linked with procmail. Permissions on the ~/.pyzor/servers files and directory is: drwxr-x--- 2 chris chris 4096 Jul 17 09:28 .pyzor -rw-r- 1 chris chris 23 Jul 17 09:28 servers Are you using this with spamc/spamd, or spamassassin-per-message? If the former, what user is spamd running as? Morning John, I'm using it with spamc which is called by a procmail recipe in my home directory which I would 'assume' makes it being run as user 'chris'. spamc is running as chris, spamd (the daemon) is probably running as a system account with (1) a different notion of what ~ refers to, and (2) no permissions to access chris' home directory. See the other answer that was posted; you may need to explicitly set the path to the pyzor config files to a shared (vs. per-user) location. -- John Hardin KA7OHZhttp://www.impsec.org/~jhardin/ jhar...@impsec.orgFALaholic #11174 pgpk -a jhar...@impsec.org key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79 --- False is the idea of utility that sacrifices a thousand real advantages for one imaginary or trifling inconvenience; that would take fire from men because it burns, and water because one may drown in it; that has no remedy for evils except destruction. The laws that forbid the carrying of arms are laws of such a nature. They disarm only those who are neither inclined nor determined to commit crime. -- Cesare Beccaria, quoted by Thomas Jefferson --- 15 days until the 227th anniversary of the signing of the U.S. Constitution
Re: Pyzor errors after upgrade
On Tue, 2014-09-02 at 07:20 -0700, John Hardin wrote: On Tue, 2 Sep 2014, Chris wrote: On Mon, 2014-09-01 at 21:17 -0700, John Hardin wrote: On Mon, 1 Sep 2014, Chris wrote: System is Ubuntu 14.04 LTS I use fetchmail linked with procmail. Permissions on the ~/.pyzor/servers files and directory is: drwxr-x--- 2 chris chris 4096 Jul 17 09:28 .pyzor -rw-r- 1 chris chris 23 Jul 17 09:28 servers Are you using this with spamc/spamd, or spamassassin-per-message? If the former, what user is spamd running as? Morning John, I'm using it with spamc which is called by a procmail recipe in my home directory which I would 'assume' makes it being run as user 'chris'. spamc is running as chris, spamd (the daemon) is probably running as a system account with (1) a different notion of what ~ refers to, and (2) no permissions to access chris' home directory. See the other answer that was posted; you may need to explicitly set the path to the pyzor config files to a shared (vs. per-user) location. John, I think you're referring to this: ifplugin Mail::SpamAssassin::Plugin::Pyzor pyzor_path /usr/local/bin/pyzor pyzor_options --homedir /home/chris/.pyzor endif I added this to my local.cf and it appears to be working now. At least this showed up at the end of a spam report: PYZOR Results are Reported 3 times. -- Chris 31.11°N 97.89°W (Elev. 1092 ft) 12:05:40 up 2 days, 14:09, 1 user, load average: 0.26, 0.27, 0.22 Ubuntu 14.04 LTS, kernel 3.13.0-35-generic
Re: Pyzor errors after upgrade
On Tue, 2014-09-02 at 07:20 -0700, John Hardin wrote: On Tue, 2 Sep 2014, Chris wrote: On Mon, 2014-09-01 at 21:17 -0700, John Hardin wrote: On Mon, 1 Sep 2014, Chris wrote: System is Ubuntu 14.04 LTS I use fetchmail linked with procmail. Permissions on the ~/.pyzor/servers files and directory is: drwxr-x--- 2 chris chris 4096 Jul 17 09:28 .pyzor -rw-r- 1 chris chris 23 Jul 17 09:28 servers Are you using this with spamc/spamd, or spamassassin-per-message? If the former, what user is spamd running as? Morning John, I'm using it with spamc which is called by a procmail recipe in my home directory which I would 'assume' makes it being run as user 'chris'. spamc is running as chris, spamd (the daemon) is probably running as a system account with (1) a different notion of what ~ refers to, and (2) no permissions to access chris' home directory. See the other answer that was posted; you may need to explicitly set the path to the pyzor config files to a shared (vs. per-user) location. Additionally John when running 'spamassassin -D -r on my spam folder it does seen to be working ok now: Sep 2 12:08:43.528 [22850] dbg: pyzor: pyzor is available: /usr/local/bin/pyzor Sep 2 12:08:43.528 [22850] dbg: dns: entering helper-app run mode Sep 2 12:08:43.529 [22850] dbg: pyzor: opening pipe: /usr/local/bin/pyzor --homedir /home/chris/.pyzor report /tmp/.spamassassin22850mid5cVtmp Sep 2 12:08:43.530 [22870] dbg: util: setuid: ruid=1000 euid=1000 Sep 2 12:08:43.965 [22850] dbg: pyzor: [22870] reporter finished successfully Sep 2 12:08:43.965 [22850] dbg: dns: leaving helper-app run mode Sep 2 12:08:43.966 [22850] info: reporter: spam reported to Pyzor -- Chris 31.11°N 97.89°W (Elev. 1092 ft) 12:10:04 up 2 days, 14:13, 2 users, load average: 0.21, 0.25, 0.23 Ubuntu 14.04 LTS, kernel 3.13.0-35-generic
Re: Pyzor errors after upgrade
On Tue, 2 Sep 2014, Chris wrote: On Tue, 2014-09-02 at 07:20 -0700, John Hardin wrote: On Tue, 2 Sep 2014, Chris wrote: On Mon, 2014-09-01 at 21:17 -0700, John Hardin wrote: On Mon, 1 Sep 2014, Chris wrote: System is Ubuntu 14.04 LTS I use fetchmail linked with procmail. Permissions on the ~/.pyzor/servers files and directory is: drwxr-x--- 2 chris chris 4096 Jul 17 09:28 .pyzor -rw-r- 1 chris chris 23 Jul 17 09:28 servers Are you using this with spamc/spamd, or spamassassin-per-message? If the former, what user is spamd running as? Morning John, I'm using it with spamc which is called by a procmail recipe in my home directory which I would 'assume' makes it being run as user 'chris'. spamc is running as chris, spamd (the daemon) is probably running as a system account with (1) a different notion of what ~ refers to, and (2) no permissions to access chris' home directory. See the other answer that was posted; you may need to explicitly set the path to the pyzor config files to a shared (vs. per-user) location. John, I think you're referring to this: ifplugin Mail::SpamAssassin::Plugin::Pyzor pyzor_path /usr/local/bin/pyzor pyzor_options --homedir /home/chris/.pyzor endif That's what I was referring to. I added this to my local.cf and it appears to be working now. At least this showed up at the end of a spam report: PYZOR Results are Reported 3 times. The fact that spamd can see into your home directory suggests you're running spamd as root. I was allowing for it being run as a less-privileged user. -- John Hardin KA7OHZhttp://www.impsec.org/~jhardin/ jhar...@impsec.orgFALaholic #11174 pgpk -a jhar...@impsec.org key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79 --- Maxim II: A Sergeant in motion outranks a Lieutenant who doesn't know what's going on. Maxim III: An ordnance technician at a dead run outranks everybody. --- 15 days until the 227th anniversary of the signing of the U.S. Constitution
Re: Pyzor errors after upgrade
On Tue, 2014-09-02 at 10:30 -0700, John Hardin wrote: On Tue, 2 Sep 2014, Chris wrote: On Tue, 2014-09-02 at 07:20 -0700, John Hardin wrote: On Tue, 2 Sep 2014, Chris wrote: On Mon, 2014-09-01 at 21:17 -0700, John Hardin wrote: On Mon, 1 Sep 2014, Chris wrote: System is Ubuntu 14.04 LTS I use fetchmail linked with procmail. Permissions on the ~/.pyzor/servers files and directory is: drwxr-x--- 2 chris chris 4096 Jul 17 09:28 .pyzor -rw-r- 1 chris chris 23 Jul 17 09:28 servers Are you using this with spamc/spamd, or spamassassin-per-message? If the former, what user is spamd running as? Morning John, I'm using it with spamc which is called by a procmail recipe in my home directory which I would 'assume' makes it being run as user 'chris'. spamc is running as chris, spamd (the daemon) is probably running as a system account with (1) a different notion of what ~ refers to, and (2) no permissions to access chris' home directory. See the other answer that was posted; you may need to explicitly set the path to the pyzor config files to a shared (vs. per-user) location. John, I think you're referring to this: ifplugin Mail::SpamAssassin::Plugin::Pyzor pyzor_path /usr/local/bin/pyzor pyzor_options --homedir /home/chris/.pyzor endif That's what I was referring to. I added this to my local.cf and it appears to be working now. At least this showed up at the end of a spam report: PYZOR Results are Reported 3 times. The fact that spamd can see into your home directory suggests you're running spamd as root. I was allowing for it being run as a less-privileged user. Would it be better if I changed the pyzor home dir to /etc/mail/spamassassin and put the 'servers' file there? -- Chris 31.11°N 97.89°W (Elev. 1092 ft) 13:08:03 up 2 days, 15:11, 1 user, load average: 0.20, 0.22, 0.17 Ubuntu 14.04 LTS, kernel 3.13.0-35-generic
Re: Pyzor errors after upgrade
On Tue, 2 Sep 2014, Chris wrote: ifplugin Mail::SpamAssassin::Plugin::Pyzor pyzor_path /usr/local/bin/pyzor pyzor_options --homedir /home/chris/.pyzor endif Would it be better if I changed the pyzor home dir to /etc/mail/spamassassin and put the 'servers' file there? In general that's a better way to do it. The alternative would be if (for example) spamd was running under a dedicated daemon user amavis, then you could leave the pyzor home dir under ~amavis. But you don't really want to have system config files living under real user directories. -- John Hardin KA7OHZhttp://www.impsec.org/~jhardin/ jhar...@impsec.orgFALaholic #11174 pgpk -a jhar...@impsec.org key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79 --- Vista: because the audio experience is *far* more important than network throughput. --- 15 days until the 227th anniversary of the signing of the U.S. Constitution
Re: Pyzor errors after upgrade
On Tue, 2014-09-02 at 11:27 -0700, John Hardin wrote: On Tue, 2 Sep 2014, Chris wrote: ifplugin Mail::SpamAssassin::Plugin::Pyzor pyzor_path /usr/local/bin/pyzor pyzor_options --homedir /home/chris/.pyzor endif Would it be better if I changed the pyzor home dir to /etc/mail/spamassassin and put the 'servers' file there? In general that's a better way to do it. The alternative would be if (for example) spamd was running under a dedicated daemon user amavis, then you could leave the pyzor home dir under ~amavis. But you don't really want to have system config files living under real user directories. Hmm, after making the change in my local.cf and restarting SA I went and took my afternoon nap. Coming back and checking my hourly syslog snippits I saw: Sep 2 13:11:32 localhost spamd[26055]: pyzor: check failed: internal error, python traceback seen in response Sep 2 13:11:46 localhost spamd[26055]: pyzor: check failed: internal error, python traceback seen in response Sep 2 13:14:07 localhost spamd[26055]: pyzor: check failed: internal error, python traceback seen in response Sep 2 13:53:52 localhost spamd[26055]: pyzor: check failed: internal error, python traceback seen in response I had changed my local.cf to read: ifplugin Mail::SpamAssassin::Plugin::Pyzor pyzor_path /usr/local/bin/pyzor pyzor_options --homedir /etc/mail/spamassassin endif and put the servers file as noted above by itself. That was possibly incorrect as I copied the .pyzor folder over from my home to /etc/mail/spamassassin and added /.pyzor after the pyzor homedir path I had. Just happened to have a new spam in my spam folder and ran spamassassin -D -r on it and it looks like it's working again: Sep 2 15:10:34.025 [30796] dbg: pyzor: pyzor is available: /usr/local/bin/pyzor Sep 2 15:10:34.025 [30796] dbg: dns: entering helper-app run mode Sep 2 15:10:34.025 [30796] dbg: pyzor: opening pipe: /usr/local/bin/pyzor --homedir /etc/mail/spamassassin/.pyzor report /tmp/.spamassassin30796Fg233vtmp Sep 2 15:10:34.028 [30799] dbg: util: setuid: ruid=1000 euid=1000 Sep 2 15:10:34.254 [30796] dbg: pyzor: [30799] reporter finished successfully Sep 2 15:10:34.254 [30796] dbg: dns: leaving helper-app run mode Sep 2 15:10:34.255 [30796] info: reporter: spam reported to Pyzor Hopefully putting the whole .pyzor folder there corrected the issue. Chris -- Chris 31.11°N 97.89°W (Elev. 1092 ft) 15:11:49 up 2 days, 17:15, 3 users, load average: 0.17, 0.23, 0.22 Ubuntu 14.04 LTS, kernel 3.13.0-35-generic
Pyzor errors after upgrade
System is Ubuntu 14.04 LTS I use fetchmail linked with procmail. Once mail is tossed to my other folders what's left is run through SA and tossed either into my Inbox or my Spam folder. Yesterday morning I upgraded to the newest version of Pyzor using this command: pip install --upgrade pyzor Since then I've been seeing this in my syslog: Aug 31 10:02:43 localhost spamd[2645]: pyzor: check failed: internal error, python traceback seen in response Aug 31 10:07:02 localhost spamd[2645]: pyzor: check failed: internal error, python traceback seen in response Aug 31 10:35:38 localhost spamd[2645]: pyzor: check failed: internal error, python traceback seen in response The version of Pyzor shown is: /usr/local/bin/pyzor 0.8.0 Permissions on the ~/.pyzor/servers files and directory is: drwxr-x--- 2 chris chris 4096 Jul 17 09:28 .pyzor -rw-r- 1 chris chris 23 Jul 17 09:28 servers Any assistance would be appreciated even a 2x4 upside the head. I'm not sure how to get to the python traceback that's mentioned. Chris -- Chris 31.11°N 97.89°W (Elev. 1092 ft) 22:14:39 up 2 days, 18 min, 2 users, load average: 0.05, 0.10, 0.22 Ubuntu 14.04 LTS, kernel 3.13.0-35-generic
Re: Pyzor errors after upgrade
On Mon, 1 Sep 2014, Chris wrote: System is Ubuntu 14.04 LTS I use fetchmail linked with procmail. Permissions on the ~/.pyzor/servers files and directory is: drwxr-x--- 2 chris chris 4096 Jul 17 09:28 .pyzor -rw-r- 1 chris chris 23 Jul 17 09:28 servers Are you using this with spamc/spamd, or spamassassin-per-message? If the former, what user is spamd running as? -- John Hardin KA7OHZhttp://www.impsec.org/~jhardin/ jhar...@impsec.orgFALaholic #11174 pgpk -a jhar...@impsec.org key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79 --- ...much of our country's counterterrorism security spending is not designed to protect us from the terrorists, but instead to protect our public officials from criticism when another attack occurs. -- Bruce Schneier --- 823 days since the first successful private support mission to ISS (SpaceX)
Re: How do I reenable AWL on spamassassin 3.3 after upgrade from 3.1
Den 2012-07-26 17:26, Nißl Reinhard skrev: reading the manuals, I've discovered that the AWL plugin isn't loaded anymore in spamassassin 3.3. Therefore I put the following lines into local.cf: On Fri, 27 Jul 2012 02:57:26 +0200 Benny Pedersen wrote: oh no, do not put loadlugin into *.cf files its wrong pr design, but so much wiki and bad behavior still continues Speaking Hawaiian? (wiki == quick) Or does the wiki actually suggest this behavior? On 07/26/2012 06:14 PM, RW wrote: It seems inelegant, but is there a practical reason why this shouldn't be done. Some optional plugins such as Botnet and iXhash load themselves from their own .cf files. Yes, there is a practical reason. In short, .pre files are read before .cf files, allowing all rules access to all plugins. If a plugin was loaded in a .cf file, it would not be available to .cf files that load earlier. There is a very careful ordering to the loading of files to ensure that newer versions and overrides are correctly loaded. Others should correct me if I have this wrong* 1. Load /etc/spamassassin/*.pre 2. If /var/lib/spamassassin/[version] exists: (a) Load its *.pre files and then its *.cf files (b) Otherwise, load *.pre then *.cf in /usr/share/spamassassin 3. Load /etc/spamassassin/*.cf 4. Parse in order of loading 5. If an include line is encountered, interrupt everything and (a) load the named file (b) parse the named file Files within a directory are sourced by asciibetical order (same as `ls`). Sub-directories are NOT examined. Each individual file is read from top to bottom, pausing for include directives as noted above (this is how the updates area can have a hierarchy). This lets /etc/spamassassin/local.cf (or wherever your system puts it) run last, thus allowing you to trump scores and definitions. Because of the loading order, third party plugins and configs whose installations suggest /etc/spamassassin should have file names that asciibetically precede local.cf, ideally starting with two digits and an underscore, mimicking the SA upstream (e.g. 20_drugs.cf). Getting back to your question, this means that if Botnet or iXhash are depended on before they are loaded, the dependent rule won't load correctly. The default install of iXhash doesn't have a problem here because it's a self-contained item, so it loads the plugin and then uses it later on in the same file. This is not advisable because when you then go in to add additional rules for that plugin, say by adding rules querying the third-party iXhash repository from Spam-Eating Monkey in external.cf, it won't work because the iXhash plugin isn't loaded until iXhash.cf. Furthermore, it prevents third-party sa-update channels from using the plugin since they are loaded in step 2 while local.cf is loaded in step 3. It also makes maintenance (and troubleshooting) harder, though SpamAssassin will take it. (There are lots of things SA can do that are ill advised, like meta rules that use the ternary operator.) The .pre files that live in /etc are kind of stuck named like that (including init.pre, which is essentially v300.pre) due to their location (otherwise, upgrading would require wiping them, which is taboo in the Unix world). I'd suggest installing an empty local.pre were it not for the fact that this would come /before/ the others. Maybe a z_local.pre file? * Footnote: Methodology. This should reveal the load order (but not the parse order): spamassassin --lint -D config 21 |egrep -o '/.*\.(pre|cf)$' |uniq signature.asc Description: OpenPGP digital signature
AW: How do I reenable AWL on spamassassin 3.3 after upgrade from 3.1
Hi Benny, attached is the output of the below mentioned command. As far as I read it, the AWL plugin gets loaded. Bye. -- Reinhard Nißl, TB3, -198 -Ursprüngliche Nachricht- Von: Benny Pedersen [mailto:m...@junc.org] Gesendet: Freitag, 27. Juli 2012 02:57 An: users@spamassassin.apache.org Betreff: Re: How do I reenable AWL on spamassassin 3.3 after upgrade from 3.1 Den 2012-07-26 17:26, Nißl Reinhard skrev: reading the manuals, I've discovered that the AWL plugin isn't loaded anymore in spamassassin 3.3. Therefore I put the following lines into local.cf: oh no, do not put loadlugin into *.cf files its wrong pr design, but so much wiki and bad behavior still continues for a start: spamassassin 21 -D --lint | less see this list, it also answers why loadplugin does not go into *.cf files hopefully recheck your *.pre files loadplugin Mail::SpamAssassin::Plugin::AWL use_auto_whitelist 1 but the file auto-whitelist hasn't been touched since the upgrade from 3.1 to 3.3 (to be precisely: spamassassin-3.3.2). What am I still doing wrong? nothing just reading the wroung homepage lint.txt.xz Description: lint.txt.xz
How do I reenable AWL on spamassassin 3.3 after upgrade from 3.1
Hi, reading the manuals, I've discovered that the AWL plugin isn't loaded anymore in spamassassin 3.3. Therefore I put the following lines into local.cf: loadplugin Mail::SpamAssassin::Plugin::AWL use_auto_whitelist 1 but the file auto-whitelist hasn't been touched since the upgrade from 3.1 to 3.3 (to be precisely: spamassassin-3.3.2). What am I still doing wrong? Bye. -- Reinhard Nißl, TB3, -198
Re: How do I reenable AWL on spamassassin 3.3 after upgrade from 3.1
Den 2012-07-26 17:26, Nißl Reinhard skrev: reading the manuals, I've discovered that the AWL plugin isn't loaded anymore in spamassassin 3.3. Therefore I put the following lines into local.cf: oh no, do not put loadlugin into *.cf files its wrong pr design, but so much wiki and bad behavior still continues for a start: spamassassin 21 -D --lint | less see this list, it also answers why loadplugin does not go into *.cf files hopefully recheck your *.pre files loadplugin Mail::SpamAssassin::Plugin::AWL use_auto_whitelist 1 but the file auto-whitelist hasn't been touched since the upgrade from 3.1 to 3.3 (to be precisely: spamassassin-3.3.2). What am I still doing wrong? nothing just reading the wroung homepage
Re: How do I reenable AWL on spamassassin 3.3 after upgrade from 3.1
On Fri, 27 Jul 2012 02:57:26 +0200 Benny Pedersen wrote: Den 2012-07-26 17:26, Nißl Reinhard skrev: reading the manuals, I've discovered that the AWL plugin isn't loaded anymore in spamassassin 3.3. Therefore I put the following lines into local.cf: oh no, do not put loadlugin into *.cf files its wrong pr design, but so much wiki and bad behavior still continues It seems inelegant, but is there a practical reason why this shouldn't be done. Some optional plugins such as Botnet and iXhash load themselves from their own .cf files.
Re: How do I reenable AWL on spamassassin 3.3 after upgrade from 3.1
Den 2012-07-27 03:14, RW skrev: It seems inelegant, but is there a practical reason why this shouldn't be done. Some optional plugins such as Botnet and iXhash load themselves from their own .cf files. did --lint not show it ?
Re: sa-update doesn't work anymore after upgrade to spamassassin-3.3.2-4.el4.rfx
Den 2012-03-18 14:44, Bernard Lheureux skrev: I get ; DiG 9.2.4 -t txt 2.3.3.updates.spamassassin.org ;; global options: printcmd ;; connection timed out; no servers could be reached But the DNS resolution works correctly, what does that mean ? dig +trace 2.2.3.updates.spamassassin.org it could mean that you are forward dns hijacked, if trace works, remove forward in named.conf 9.2.4 is old
sa-update doesn't work anymore after upgrade to spamassassin-3.3.2-4.el4.rfx
On a CentOS 4.9-x86 box I user for years, sa-update doesnt want to work anymore since I've upgraded from 3.1.3 this seems to be related to a DNS problem, but I can't find what I need to adapt to fix it, could you help me ? All that I get in DBG mode is: Mar 18 14:27:47.241 [15822] dbg: channel: attempting channel updates.spamassassin.org Mar 18 14:27:47.243 [15822] dbg: channel: update directory /var/lib/spamassassin/3.003002/updates_spamassassin_org Mar 18 14:27:47.244 [15822] dbg: channel: channel cf file /var/lib/spamassassin/3.003002/updates_spamassassin_org.cf Mar 18 14:27:47.245 [15822] dbg: channel: channel pre file /var/lib/spamassassin/3.003002/updates_spamassassin_org.pre Mar 18 14:27:47.246 [15822] dbg: channel: metadata version = 1162027 Mar 18 14:28:17.257 [15822] dbg: dns: query failed: 2.3.3.updates.spamassassin.org = SERVFAIL As long as I can see DNS is working correctly and I've also tried to use Google DNSes without success... What could I do to fix this asap ? Thanks for your help... -- (°- Bernard Lheureux Gestionnaire des MailingLists ML, TechML, LinuxML //\ http://www.bbsoft4.org/Mailinglists.htm ** MailTo:r...@bbsoft4.org v_/_ http://www.bbsoft4.org/ * http://www.portalinux.org/
Re: sa-update doesn't work anymore after upgrade to spamassassin-3.3.2-4.el4.rfx
On 3/18/2012 9:30 AM, Bernard Lheureux wrote: On a CentOS 4.9-x86 box I user for years, sa-update doesnt want to work anymore since I've upgraded from 3.1.3 this seems to be related to a DNS problem, but I can't find what I need to adapt to fix it, could you help me ? Definitely sounds like DNS. If you type dig -t txt 2.3.3.updates.spamassassin.org, what do you get? Regards, KAM
Re: sa-update doesn't work anymore after upgrade to spamassassin-3.3.2-4.el4.rfx
On 03/18/2012 02:33 PM, Kevin A. McGrail wrote: On 3/18/2012 9:30 AM, Bernard Lheureux wrote: On a CentOS 4.9-x86 box I user for years, sa-update doesnt want to work anymore since I've upgraded from 3.1.3 this seems to be related to a DNS problem, but I can't find what I need to adapt to fix it, could you help me ? Definitely sounds like DNS. If you type dig -t txt 2.3.3.updates.spamassassin.org, what do you get? Regards, KAM I get ; DiG 9.2.4 -t txt 2.3.3.updates.spamassassin.org ;; global options: printcmd ;; connection timed out; no servers could be reached But the DNS resolution works correctly, what does that mean ? -- (°- Bernard Lheureux Gestionnaire des MailingLists ML, TechML, LinuxML //\ http://www.bbsoft4.org/Mailinglists.htm ** MailTo:r...@bbsoft4.org v_/_ http://www.bbsoft4.org/ * http://www.portalinux.org/
Re: sa-update doesn't work anymore after upgrade to spamassassin-3.3.2-4.el4.rfx
On 3/18/12 9:44 AM, Bernard Lheureux wrote: I get ; DiG 9.2.4 -t txt 2.3.3.updates.spamassassin.org ;; global options: printcmd ;; connection timed out; no servers could be reached But the DNS resolution works correctly, what does that mean ? it means the DNS resolution isn't working correctly. you should get something like this: dig -t txt 2.3.3.updates.spamassassin.org ; DiG 9.3.5-P2 -t txt 2.3.3.updates.spamassassin.org ;; global options: printcmd ;; Got answer: ;; -HEADER- opcode: QUERY, status: NOERROR, id: 37105 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 3 ;; QUESTION SECTION: ;2.3.3.updates.spamassassin.org.INTXT ;; ANSWER SECTION: 2.3.3.updates.spamassassin.org.3600 INTXT1293136 ;; AUTHORITY SECTION: spamassassin.org.3600INNSa.auth-ns.sonic.net. spamassassin.org.3600INNSb.auth-ns.sonic.net. spamassassin.org.3600INNSc.auth-ns.sonic.net. spamassassin.org.3600INNSns.hyperreal.org. ;; ADDITIONAL SECTION: a.auth-ns.sonic.net.37091INA209.204.159.20 b.auth-ns.sonic.net.37091INA184.173.92.18 c.auth-ns.sonic.net.37091INA69.9.186.104 ;; Query time: 117 msec ;; SERVER: 10.70.1.2#53(10.70.1.2) ;; WHEN: Sun Mar 18 09:54:41 2012 ;; MSG SIZE rcvd: 208 -- Michael Scheidell, CTO o: 561-999-5000 d: 561-948-2259 *| *SECNAP Network Security Corporation * Best Mobile Solutions Product of 2011 * Best Intrusion Prevention Product * Hot Company Finalist 2011 * Best Email Security Product * Certified SNORT Integrator __ This email has been scanned and certified safe by SpammerTrap(r). For Information please see http://www.spammertrap.com/ __
Re: sa-update doesn't work anymore after upgrade to spamassassin-3.3.2-4.el4.rfx
I get ; DiG 9.2.4 -t txt 2.3.3.updates.spamassassin.org ;; global options: printcmd ;; connection timed out; no servers could be reached But the DNS resolution works correctly, what does that mean ? It means DNS is not working correctly for you. Here's an old ISP in my areas's DNS server. What do you get? dig -t txt 2.3.3.updates.spamassassin.org @ns.erols.com ;; QUESTION SECTION: ;2.3.3.updates.spamassassin.org.IN TXT ;; ANSWER SECTION: 2.3.3.updates.spamassassin.org. 3600 IN TXT 1293136 ;; AUTHORITY SECTION: spamassassin.org. 86400 IN NS ns.hyperreal.org. spamassassin.org. 86400 IN NS c.auth-ns.sonic.net. spamassassin.org. 86400 IN NS a.auth-ns.sonic.net. spamassassin.org. 86400 IN NS b.auth-ns.sonic.net. ;; ADDITIONAL SECTION: a.auth-ns.sonic.net.49101 IN A 209.204.159.20 a.auth-ns.sonic.net.49101 IN 2001:5a8:0:3::1 b.auth-ns.sonic.net.49101 IN A 184.173.92.18 b.auth-ns.sonic.net.49101 IN 2607:f0d0:1102:f::2 c.auth-ns.sonic.net.49101 IN A 69.9.186.104 c.auth-ns.sonic.net.49101 IN 2001:48c8:1:1::2 ;; Query time: 22 msec ;; SERVER: 207.172.3.8#53(207.172.3.8) ;; WHEN: Sun Mar 18 09:45:41 2012 ;; MSG SIZE rcvd: 292
Re: sa-update doesn't work anymore after upgrade to spamassassin-3.3.2-4.el4.rfx
On 03/18/2012 02:59 PM, Kevin A. McGrail wrote: Could this be related to a firewall rule that should be blocking it ? Which ports should I open to ensure it works not only port 53 udp and tcp ? I get ; DiG 9.2.4 -t txt 2.3.3.updates.spamassassin.org ;; global options: printcmd ;; connection timed out; no servers could be reached But the DNS resolution works correctly, what does that mean ? It means DNS is not working correctly for you. Here's an old ISP in my areas's DNS server. What do you get? dig -t txt 2.3.3.updates.spamassassin.org @ns.erols.com ;; QUESTION SECTION: ;2.3.3.updates.spamassassin.org. IN TXT ;; ANSWER SECTION: 2.3.3.updates.spamassassin.org. 3600 IN TXT "1293136" ;; AUTHORITY SECTION: spamassassin.org. 86400 IN NS ns.hyperreal.org. spamassassin.org. 86400 IN NS c.auth-ns.sonic.net. spamassassin.org. 86400 IN NS a.auth-ns.sonic.net. spamassassin.org. 86400 IN NS b.auth-ns.sonic.net. ;; ADDITIONAL SECTION: a.auth-ns.sonic.net. 49101 IN A 209.204.159.20 a.auth-ns.sonic.net. 49101 IN 2001:5a8:0:3::1 b.auth-ns.sonic.net. 49101 IN A 184.173.92.18 b.auth-ns.sonic.net. 49101 IN 2607:f0d0:1102:f::2 c.auth-ns.sonic.net. 49101 IN A 69.9.186.104 c.auth-ns.sonic.net. 49101 IN 2001:48c8:1:1::2 ;; Query time: 22 msec ;; SERVER: 207.172.3.8#53(207.172.3.8) ;; WHEN: Sun Mar 18 09:45:41 2012 ;; MSG SIZE rcvd: 292 -- M$-Internet Exploder est le cancer de l'Internet, voyez pourquoi ici: http://www.aful.org/ressources/documentations/msie-problemes-securite -- (- Bernard Lheureux Gestionnaire des MailingLists ML, TechML, LinuxML //\ http://www.bbsoft4.org/Mailinglists.htm ** MailTo:r...@bbsoft4.org v_/_ http://www.bbsoft4.org/ * http://www.portalinux.org/
Re: sa-update doesn't work anymore after upgrade to spamassassin-3.3.2-4.el4.rfx
On 03/18/2012 04:24 PM, Bernard Lheureux wrote: I found why, that was related to my firewall, now everything is OK... I simply had to disable the outgoing rules for DNS-OUT, because OUT is allowed from all, and now all is OK Thanks a lot to all of you ! On 03/18/2012 03:40 PM, Kevin A. McGrail wrote: Which ports should I open to ensure it works not only port 53 udp and tcp ? I'm assuming dig -t txt 2.3.3.updates.spamassassin.org @ns.erols.com doesn't work for you either. http://systembash.com/content/dns-server-firewall-open-ports/ Has a good list of ports but it's basically 53 tcp/udp and every single upper port because of the back channel. If your firewall automatically recognizes and opens back channels, you might be ok. My FW is a Watchguard Firebox III/700 and ALL is open for OUTGOING, then I don't think this could be caused by this... But I cannot find why this answers always: [root@myserver ~]# dig -t txt 2.3.3.updates.spamassassin.org ; DiG 9.3.6-P1-RedHat-9.3.6-20.P1.el5 -t txt 2.3.3.updates.spamassassin.org ;; global options: printcmd ;; connection timed out; no servers could be reached I use my own Bind9 DNS server which is running OK for a long time ago... And the 2 forwarders on this server are the 2 DNSes of my ISP what could be wrong ? Do you know if I could try to use public DNS as forwarders ? If yes, which ones ? -- (°- Bernard Lheureux Gestionnaire des MailingLists ML, TechML, LinuxML //\ http://www.bbsoft4.org/Mailinglists.htm ** MailTo:r...@bbsoft4.org v_/_ http://www.bbsoft4.org/ * http://www.portalinux.org/ -- M$-Internet Exploder est le cancer de l'Internet, voyez pourquoi ici: http://www.aful.org/ressources/documentations/msie-problemes-securite -- (°- Bernard Lheureux Gestionnaire des MailingLists ML, TechML, LinuxML //\ http://www.bbsoft4.org/Mailinglists.htm ** MailTo:r...@bbsoft4.org v_/_ http://www.bbsoft4.org/ * http://www.portalinux.org/
Re: sa-update doesn't work anymore after upgrade to spamassassin-3.3.2-4.el4.rfx
18.3.2012 17:24, Bernard Lheureux kirjoitti: I use my own Bind9 DNS server which is running OK for a long time ago... And the 2 forwarders on this server are the 2 DNSes of my ISP what could be wrong ? Do you know if I could try to use public DNS as forwarders ? If yes, which ones ? Try namebench and find it out! http://code.google.com/p/namebench/ it may be available in your repo if you use Linux. -- Think twice before speaking, but don't say think think click click. signature.asc Description: OpenPGP digital signature
Excessive junk mail even after upgrade/update
I have recently inherited a web server with roughly 50 clients. Last week I started getting complaints about excessive amounts of junk mail being delivered. I upgraded my SpamAssassin Rules, Clam AV, MailScanner, and SpamAssassin Engine (3.2.5 à 3.3.1), in that order. At first, this seemed to work. Customers reported only receiving a few junk mail the following day; however, since then, they have begun receiving hundreds of junk messages again each day. My server is running RHEL5 and the Ensim Pro 10.3 Interface, if that makes a difference. My first question is, how can I verify that I installed SpamAssassin correctly and that it is scanning and marking messages properly. The server shows the service as running, but this is all I have found so far to indicate whether it is working or not. Second, are there any steps that I should have taken after the installs, or perhaps did I install things in the wrong order? Lastly, I have to manually start the service from the console each time the server is rebooted. It used to start automatically, and allowed me to restart the service from the Web GUI if needed. How can I get it to start automatically again? If I try to start it from the GUI, it returns an error of Unknown option and provides a list of switch options. I know it's trying to start the correct service from the options listed, but what might be causing it not to starting? I am still relatively new to web administration; so, any help is greatly appreciated. Thank you, Mike Gibson Sr. Network Engineer Select Tel Systems, Inc. 229.434.0540 Select Tel Systems On Time, Done Right, Guaranteed! (229) 434-0540
Re: Excessive junk mail even after upgrade/update
On 1/4/11 9:53 AM, Mike Gibson wrote: I have recently inherited a web server with roughly 50 clients. Last week I started getting complaints about excessive amounts of junk mail being delivered. I upgraded my SpamAssassin Rules, Clam AV, MailScanner, and SpamAssassin Engine (3.2.5 à 3.3.1), in that order. At first, this seemed to work. Customers reported only receiving a few junk mail the following day; however, since then, they have begun receiving hundreds of junk messages again each day. My server is running RHEL5 and the Ensim Pro 10.3 Interface, if that makes a difference. My first question is, how can I verify that I installed SpamAssassin correctly and that it is scanning and marking messages properly. The server shows the service as running, but this is all I have found so far to indicate whether it is working or not. you say this is controlled by a web gui? you would need to discuss this most likely with someone familiar with that web gui. as for verifying what worked, you need to see the FULL headers of the email the client received. (for help, see our 'missed spam' faq, somewhere on http://www.secnap.com/support) also, understand that SA does NOT block spam. it only 'MARKS it'. if your users are getting spam with '***SPAM***' in the subject line, then SA is working. -- Michael Scheidell, CTO o: 561-999-5000 d: 561-948-2259 ISN: 1259*1300 *| *SECNAP Network Security Corporation * Certified SNORT Integrator * 2008-9 Hot Company Award Winner, World Executive Alliance * Five-Star Partner Program 2009, VARBusiness * Best in Email Security,2010: Network Products Guide * King of Spam Filters, SC Magazine 2008 __ This email has been scanned and certified safe by SpammerTrap(r). For Information please see http://www.secnap.com/products/spammertrap/ __
Re: Excessive junk mail even after upgrade/update
On Tue, 4 Jan 2011 09:53:05 -0500 Mike Gibson mi...@seltel.com wrote: I have recently inherited a web server with roughly 50 clients. Last week I started getting complaints about excessive amounts of junk mail being delivered. spamassassin should be the last line of defence, you should be using blocklists and, if possible, greylisting. I upgraded my SpamAssassin Rules, Clam AV, MailScanner, and SpamAssassin Engine (3.2.5 à 3.3.1), in that order. You should run sa-update *after* updating spamassassin. 3.3.1 doesn't come with any rules at all and 3.2.5 rules wont be used. My first question is, how can I verify that I installed SpamAssassin correctly and that it is scanning and marking messages properly. It should show up in the mail logs, you can also send a test message. http://en.wikipedia.org/wiki/GTUBE The server shows the service as running, but this is all I have found so far to indicate whether it is working or not. MailScanner uses SpamAssassin as a perl library, so you don't need spamd if that's what you meant by service. Lastly, I have to manually start the service from the console each time the server is rebooted. It used to start automatically, and allowed me to restart the service from the Web GUI if needed. How can I get it to start automatically again? Search on red hat init.d
RE: After upgrade the SA to 3.3.1, Mail scanning stop working partially
On Wed, 2010-08-25 at 08:10 +0530, Suhag Desai wrote:
Aug 25 08:07:12 spd spamd[3776]: spamd: clean message (4.0/5.0) for clamav:46
in 10.7 seconds, 2792 bytes.
Aug 25 08:07:12 spd spamd[3776]: spamd: result: . 4 -
ALL_TRUSTED,HTML_MESSAGE,LOCAL_DEMONSTRATION_RULE,MIME_HTML_MOSTLY,TVD_SPACE_RATIO
scantime=10.7,size=2792,user=clamav,uid=46,required_score=5.0,rhost=spd,raddr=127.0.0.1,rport=59296,mid=00fb01cb43fe$5e706710$1b5135...@com,autolearn=no
It seems that it consider test.cf file (LOCAL_DEMONSTRATION_RULE) while
processing the mail..but still not consider it as a mail...
SA uses a scoring system. The fact a single rule hit has a score equal
the required_score threshold is irrelevant. The *sum* of all hit rules'
scores is what determines a message to be spam or ham.
ALL_TRUSTED has a score of -1. The other rules account for 0.001 each
(network tests enabled, no Bayes because it hasn't been trained
sufficient.)
So the overall score for that test message is 4.0 (rounded), exactly as
the log shows. Below the required_score threshold.
There is nothing wrong with your SA, it works just as expected.
After upgrade the SpamAssassin Server version to 3.3.1, my mail
scanning stop working partially.
Let me explain in details. When I set the required score to 5.0, mail
scanning is not working properly. When I send the mail with “test123”
with required score 5, SA not consider it spam but when I set the
required score to 4, SA consider it spam the same mail. I have check
the same with many other test.
What do the X-Spam headers read SA generates?
You are using a test rule with a score of 5.0, which is the same as the
required_score threshold. Odds are, there are other rules firing on the
message a well.
If the sum of these other rules is less than 0, but greater than -1,
you'd get exactly what you just described.
q.e.d. :)
--
char *t=\10pse\0r\0dtu...@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4;
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;il;i++){ i%8? c=1:
(c=*++x); c128 (s+=h); if (!(h=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}
RE: After upgrade the SA to 3.3.1, Mail scanning stop working partially
Below is my full local.cf. I already run 'spamassassin --lint' No other rules
are conflicting with test.cf.
[r...@spd spamassassin]# cat local.cf
# This is the right place to customize your installation of SpamAssassin.
#
# See 'perldoc Mail::SpamAssassin::Conf' for details of what can be
# tweaked.
#
# Only a small subset of options are listed below
#
# Add *SPAM* to the Subject header of spam e-mails
#
rewrite_header Subject SPAM-123
# Save spam messages as a message/rfc822 MIME attachment instead of
# modifying the original message (0: off, 2: use text/plain instead)
#
report_safe 1
# Set which networks or hosts are considered 'trusted' by your mail
# server (i.e. not spammers)
#
# trusted_networks 212.17.35.
# Set file-locking method (flock is not safe over NFS, but is faster)
#
# lock_method flock
# Set the threshold at which a message is considered spam (default: 5.0)
#
required_score 5.0
# Use Bayesian classifier (default: 1)
#
use_bayes 1
# Bayesian classifier auto-learning (default: 1)
#
bayes_auto_learn 1
# Set headers which may provide inappropriate cues to the Bayesian
# classifier
#
# bayes_ignore_header X-Bogosity
# bayes_ignore_header X-Spam-Flag
# bayes_ignore_header X-Spam-Status
# Some shortcircuiting, if the plugin is enabled
#
ifplugin Mail::SpamAssassin::Plugin::Shortcircuit
#
# default: strongly-whitelisted mails are *really* whitelisted now, if the
# shortcircuiting plugin is active, causing early exit to save CPU load.
# Uncomment to turn this on
#
# shortcircuit USER_IN_WHITELIST on
# shortcircuit USER_IN_DEF_WHITELIST on
# shortcircuit USER_IN_ALL_SPAM_TO on
# shortcircuit SUBJECT_IN_WHITELISTon
# the opposite; blacklisted mails can also save CPU
#
# shortcircuit USER_IN_BLACKLIST on
# shortcircuit USER_IN_BLACKLIST_TOon
# shortcircuit SUBJECT_IN_BLACKLISTon
# if you have taken the time to correctly specify your trusted_networks,
# this is another good way to save CPU
#
# shortcircuit ALL_TRUSTED on
# and a well-trained bayes DB can save running rules, too
#
# shortcircuit BAYES_99spam
# shortcircuit BAYES_00ham
endif # Mail::SpamAssassin::Plugin::Shortcircuit
below is the spamd logfile entries..
Aug 25 08:07:01 spd spamd[3776]: spamd: connection from spd [127.0.0.1] at port
59296
Aug 25 08:07:01 spd spamd[3776]: spamd: setuid to clamav succeeded
Aug 25 08:07:01 spd spamd[3776]: spamd: processing message
00fb01cb43fe$5e706710$1b5135...@com for clamav:46
Aug 25 08:07:12 spd spamd[3776]: spamd: clean message (4.0/5.0) for clamav:46
in 10.7 seconds, 2792 bytes.
Aug 25 08:07:12 spd spamd[3776]: spamd: result: . 4 -
ALL_TRUSTED,HTML_MESSAGE,LOCAL_DEMONSTRATION_RULE,MIME_HTML_MOSTLY,TVD_SPACE_RATIO
scantime=10.7,size=2792,user=clamav,uid=46,required_score=5.0,rhost=spd,raddr=127.0.0.1,rport=59296,mid=00fb01cb43fe$5e706710$1b5135...@com,autolearn=no
Aug 25 08:07:12 spd spamd[3775]: prefork: child states: II
It seems that it consider test.cf file (LOCAL_DEMONSTRATION_RULE) while
processing the mail..but still not consider it as a mail...
-Original Message-
From: Karsten Bräckelmann [mailto:guent...@rudersport.de]
Sent: Monday, August 23, 2010 7:40 PM
To: users@spamassassin.apache.org
Subject: Re: After upgrade the SA to 3.3.1, Mail scanning stop working partially
On Mon, 2010-08-23 at 08:16 +0530, Suhag Desai wrote:
After upgrade the SpamAssassin Server version to 3.3.1, my mail
scanning stop working partially.
Below is the setting for local.cf
rewrite_header Subject SPAM
report_safe 1
required_score 5.0
use_bayes 1
bayes_auto_learn 1
endif # Mail::SpamAssassin::Plugin::Shortcircuit
Is that the exact content of your local.cf? That doesn't even pass lint
testing. Did you do 'spamassassin --lint'?
Let me explain in details. When I set the required score to 5.0, mail
scanning is not working properly. When I send the mail with “test123”
with required score 5, SA not consider it spam but when I set the
required score to 4, SA consider it spam the same mail. I have check
the same with many other test.
What do the X-Spam headers read SA generates?
You are using a test rule with a score of 5.0, which is the same as the
required_score threshold. Odds are, there are other rules firing on the
message a well.
If the sum of these other rules is less than 0, but greater than -1,
you'd get exactly what you just described.
Below is the log
@40004c71e02d1471a28c simscan:[4698]:CLEAN
(-1.00/12.00):5.3640s:test123:192.168.10.70:s...@test.com:d...@test.com
@40004c71e02f35bee364 tcpserver: end 4698 status 0
@40004c71e02f35bf0e5c tcpserver: status: 0/100
There is no SA logs in there.
--
char *t=\10pse\0r\0dtu...@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4;
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;il;i++){ i%8? c=1:
(c=*++x); c128 (s+=h); if (!(h=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}
Re: After upgrade the SA to 3.3.1, Mail scanning stop working partially
On 8/22/10 9:46 PM, Suhag Desai spde...@ncode.in wrote: After upgrade the SpamAssassin Server version to 3.3.1, my mail scanning stop working partially. This is a known bug. https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6419 -- Daniel J McDonald, CCIE # 2495, CISSP # 78281
RE: After upgrade the SA to 3.3.1, Mail scanning stop working partially
Still not clear from the link -Original Message- From: Daniel McDonald [mailto:dan.mcdon...@austinenergy.com] Sent: Monday, August 23, 2010 5:46 PM To: spamassassin Subject: Re: After upgrade the SA to 3.3.1, Mail scanning stop working partially On 8/22/10 9:46 PM, Suhag Desai spde...@ncode.in wrote: After upgrade the SpamAssassin Server version to 3.3.1, my mail scanning stop working partially. This is a known bug. https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6419 -- Daniel J McDonald, CCIE # 2495, CISSP # 78281
Re: After upgrade the SA to 3.3.1, Mail scanning stop working partially
On Mon, 2010-08-23 at 07:16 -0500, Daniel McDonald wrote:
After upgrade the SpamAssassin Server version to 3.3.1, my mail scanning
stop
working partially.
This is a known bug.
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6419
It is rather unlikely, this would be the reason.
That bug is just an inconsistency between reporting (non-spam) and
rounding (5.0/5.0) when using spamd for scores 4.95 = score 5.0.
Oh, and it has not been introduced in 3.3, but similarly affects 3.2.
--
char *t=\10pse\0r\0dtu...@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4;
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;il;i++){ i%8? c=1:
(c=*++x); c128 (s+=h); if (!(h=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}
Re: After upgrade the SA to 3.3.1, Mail scanning stop working partially
On Mon, 2010-08-23 at 08:16 +0530, Suhag Desai wrote:
After upgrade the SpamAssassin Server version to 3.3.1, my mail
scanning stop working partially.
Below is the setting for local.cf
rewrite_header Subject SPAM
report_safe 1
required_score 5.0
use_bayes 1
bayes_auto_learn 1
endif # Mail::SpamAssassin::Plugin::Shortcircuit
Is that the exact content of your local.cf? That doesn't even pass lint
testing. Did you do 'spamassassin --lint'?
Let me explain in details. When I set the required score to 5.0, mail
scanning is not working properly. When I send the mail with “test123”
with required score 5, SA not consider it spam but when I set the
required score to 4, SA consider it spam the same mail. I have check
the same with many other test.
What do the X-Spam headers read SA generates?
You are using a test rule with a score of 5.0, which is the same as the
required_score threshold. Odds are, there are other rules firing on the
message a well.
If the sum of these other rules is less than 0, but greater than -1,
you'd get exactly what you just described.
Below is the log
@40004c71e02d1471a28c simscan:[4698]:CLEAN
(-1.00/12.00):5.3640s:test123:192.168.10.70:s...@test.com:d...@test.com
@40004c71e02f35bee364 tcpserver: end 4698 status 0
@40004c71e02f35bf0e5c tcpserver: status: 0/100
There is no SA logs in there.
--
char *t=\10pse\0r\0dtu...@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4;
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;il;i++){ i%8? c=1:
(c=*++x); c128 (s+=h); if (!(h=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}
After upgrade the SA to 3.3.1, Mail scanning stop working partially
After upgrade the SpamAssassin Server version to 3.3.1, my mail scanning stop working partially. Below is the test.cf file for checking whether SA working as per the given score. [r...@spd SPECS]# cd /etc/mail/spamassassin/ [r...@spd spamassassin]# cat test.cf body LOCAL_DEMONSTRATION_RULE /test123/ score LOCAL_DEMONSTRATION_RULE 5 describe LOCAL_DEMONSTRATION_RULE This is a simple test rule Below is the setting for local.cf rewrite_header Subject SPAM report_safe 1 required_score 5.0 use_bayes 1 bayes_auto_learn 1 endif # Mail::SpamAssassin::Plugin::Shortcircuit Let me explain in details. When I set the required score to 5.0, mail scanning is not working properly. When I send the mail with test123 with required score 5, SA not consider it spam but when I set the required score to 4, SA consider it spam the same mail. I have check the same with many other test. It seems that SA take the score 4 to consider the mail as a SPAM and rewrite the subject with *SPAM*** Below is the log @40004c71e02720670564 tcpserver: status: 1/100 @40004c71e02720b8462c tcpserver: pid 4698 from 192.168.10.70 @40004c71e02720cb1a7c tcpserver: ok 4698 spd:192.168.30.195:25 :192.168.10.70::61253 @40004c71e027385ebf7c CHKUSER accepted sender: from s...@test.com:s...@test.com: remote SPDESAI:unknown:192.168.10.70 rcpt : sender accepted @40004c71e02739b381dc CHKUSER accepted rcpt: from s...@test.com:s...@test.com: remote SPDESAI:unknown:192.168.10.70 rcpt d...@test.com : found existing recipient @40004c71e02739b94a54 policy_check: local s...@test.com - local d...@test.com (AUTHENTICATED SENDER) @40004c71e02739bf3dc4 policy_check: policy allows transmission @40004c71e02d1471a28c simscan:[4698]:CLEAN (-1.00/12.00):5.3640s:test123:192.168.10.70:s...@test.com:d...@test.com @40004c71e02f35bee364 tcpserver: end 4698 status 0 @40004c71e02f35bf0e5c tcpserver: status: 0/100
Re: Fuzzyocr and rule errors after upgrade to 3.3.0
John Wilcock wrote on Thu, 28 Jan 2010 08:31:07 +0100: Presumably because you didn't run sa-update while the ruleset was missing from the update... Hm, it *is* missing. But maybe not from the compiled rules, well. Kai -- Get your web at Conactive Internet Services: http://www.conactive.com
Re: Fuzzyocr and rule errors after upgrade to 3.3.0
Ed Kasky wrote on Tue, 26 Jan 2010 22:30:23 -0800: FuzzyOcr is it mentioned in the release notes? check back with the author of this plugin if it is compatible with 3.3.0 Also - is anyone else getting a lot of warning: score set for non-existent rule errors? I ran sa-update after teand continue to get a slew of them... It probably means that you set scores for rules that don't exist anymore. Kai -- Get your web at Conactive Internet Services: http://www.conactive.com
Re: Fuzzyocr and rule errors after upgrade to 3.3.0
At 03:31 AM Wednesday, 1/27/2010, you wrote -= Ed Kasky wrote on Tue, 26 Jan 2010 22:30:23 -0800: FuzzyOcr is it mentioned in the release notes? check back with the author of this plugin if it is compatible with 3.3.0 Also - is anyone else getting a lot of warning: score set for non-existent rule errors? I ran sa-update after teand continue to get a slew of them... It probably means that you set scores for rules that don't exist anymore. Forgot to check local.cf - I had set them all but 1 which was in 70_sare_header.cf. I checked the FuzzyOcr site but no mention yet of 3.3.0 so I just disabled logging to file. Thanks! Ed ... Randomly Generated Quote (163 of 1582): Not everything that counts can be counted, and not everything that can be counted counts. (Sign hanging in Einstein's office at Princeton)
Re: Fuzzyocr and rule errors after upgrade to 3.3.0
Le 27/01/2010 07:30, Ed Kasky a écrit : Also - is anyone else getting a lot of warning: score set for non-existent rule errors? I ran sa-update after teand continue to get a slew of them... Me too... 463 of them, to be exact. With the exception of ACCESSDB where the score is set to 0 anyway, all the affected rules were in 72_active.cf or 80_additional.cf in 3.2.5. However, these two files don't seem to exist in /var/lib/spamassassin/3.003000/updates_spamassassin_org/ John. -- -- Over 4000 webcams from ski resorts around the world - www.snoweye.com -- Translate your technical documents and web pages- www.tradoc.fr
Re: Fuzzyocr and rule errors after upgrade to 3.3.0
John Wilcock wrote on Wed, 27 Jan 2010 15:27:17 +0100: Me too... 463 of them, to be exact. Do you want to say that you changed the score of 463 rules? However, these two files don't seem to exist in /var/lib/spamassassin/3.003000/updates_spamassassin_org/ Indeed, that's why you are getting this error. Kai -- Get your web at Conactive Internet Services: http://www.conactive.com
Re: Fuzzyocr and rule errors after upgrade to 3.3.0
Le 27/01/2010 17:31, Kai Schaetzl a écrit : John Wilcock wrote on Wed, 27 Jan 2010 15:27:17 +0100: Me too... 463 of them, to be exact. Do you want to say that you changed the score of 463 rules? No, absolutely not. On this test box I haven't changed the scores of any rules. There are absolutely no local score statements (and no local rules either, for that matter). However, these two files don't seem to exist in /var/lib/spamassassin/3.003000/updates_spamassassin_org/ Indeed, that's why you are getting this error. Yes, I'm well aware of that! To state the problem again, 463 of the scores in the 50_scores.cf from 3.3.0 sa-update refer to rules that used to be in 72_active.cf or 80_additional.cf in 3.2.5, but that neither of these two files are anywhere to be found in the 3.3.0 sa-update. Either someone forgot to delete all these rules, or (more likely IMO) someone forgot to include 72_active.cf and 80_additional.cf in the sa-update files. John. -- -- Over 4000 webcams from ski resorts around the world - www.snoweye.com -- Translate your technical documents and web pages- www.tradoc.fr
Re: Fuzzyocr and rule errors after upgrade to 3.3.0
On Wed, Jan 27, 2010 at 16:43, John Wilcock j...@tradoc.fr wrote: To state the problem again, 463 of the scores in the 50_scores.cf from 3.3.0 sa-update refer to rules that used to be in 72_active.cf or 80_additional.cf in 3.2.5, but that neither of these two files are anywhere to be found in the 3.3.0 sa-update. Either someone forgot to delete all these rules, or (more likely IMO) someone forgot to include 72_active.cf and 80_additional.cf in the sa-update files. I think you're dead right. It appears one of the build scripts does the wrong thing with the 3.3.0 release, and cut an update missing those files. :( I've just cut a new update which should fix it, and opened a bug to fix the build procedure... -- --j.
Re: Fuzzyocr and rule errors after upgrade to 3.3.0
Le 27/01/2010 18:57, Justin Mason a écrit : Either someone forgot to delete all these rules, or (more likely IMO) someone forgot to include 72_active.cf and 80_additional.cf in the sa-update files. I think you're dead right. It appears one of the build scripts does the wrong thing with the 3.3.0 release, and cut an update missing those files. :( I've just cut a new update which should fix it, and opened a bug to fix the build procedure... sa-update has now pulled down a 72_active.cf file, and lint now only gives 5 score set for non-existent rule warnings instead of 463. Thanks Justin. John. -- -- Over 4000 webcams from ski resorts around the world - www.snoweye.com -- Translate your technical documents and web pages- www.tradoc.fr
Re: Fuzzyocr and rule errors after upgrade to 3.3.0
On 1/27/2010 1:02 PM, John Wilcock wrote: Le 27/01/2010 18:57, Justin Mason a écrit : Either someone forgot to delete all these rules, or (more likely IMO) someone forgot to include 72_active.cf and 80_additional.cf in the sa-update files. I think you're dead right. It appears one of the build scripts does the wrong thing with the 3.3.0 release, and cut an update missing those files. :( I've just cut a new update which should fix it, and opened a bug to fix the build procedure... sa-update has now pulled down a 72_active.cf file, and lint now only gives 5 score set for non-existent rule warnings instead of 463. How long does it normally take for mirrors to see such changes? My sa-update is not grabbing the missing files yet.
RE: Fuzzyocr and rule errors after upgrade to 3.3.0
Thank you guys! I'm now down to just 5 non-existent rule warnings as well: Jan 27 10:18:13.473 [19398] dbg: config: warning: score set for non-existent rule SHORTCIRCUIT Jan 27 10:18:13.473 [19398] dbg: config: warning: score set for non-existent rule SUBJ_RE_NUM Jan 27 10:18:13.473 [19398] dbg: config: warning: score set for non-existent rule FM_VIAGRA_SPAM1114 Jan 27 10:18:13.473 [19398] dbg: config: warning: score set for non-existent rule AXB_HELO_LH_HOME Jan 27 10:18:13.474 [19398] dbg: config: warning: score set for non-existent rule ACCESSDB I presume we are all missing the same rules... Jeff -Original Message- From: John Wilcock [mailto:j...@tradoc.fr] Sent: Wednesday, January 27, 2010 10:03 AM To: users@spamassassin.apache.org Subject: Re: Fuzzyocr and rule errors after upgrade to 3.3.0 Le 27/01/2010 18:57, Justin Mason a écrit : Either someone forgot to delete all these rules, or (more likely IMO) someone forgot to include 72_active.cf and 80_additional.cf in the sa-update files. I think you're dead right. It appears one of the build scripts does the wrong thing with the 3.3.0 release, and cut an update missing those files. :( I've just cut a new update which should fix it, and opened a bug to fix the build procedure... sa-update has now pulled down a 72_active.cf file, and lint now only gives 5 score set for non-existent rule warnings instead of 463. Thanks Justin. John. -- -- Over 4000 webcams from ski resorts around the world - www.snoweye.com -- Translate your technical documents and web pages- www.tradoc.fr
Re: Fuzzyocr and rule errors after upgrade to 3.3.0
John Wilcock wrote on Wed, 27 Jan 2010 17:43:56 +0100: someone forgot to include 72_active.cf and 80_additional.cf in the sa-update files. Now I understand. However, why am I not getting these warnings with a spamassassin --lint? Kai -- Get your web at Conactive Internet Services: http://www.conactive.com
Re: Fuzzyocr and rule errors after upgrade to 3.3.0
At 10:02 AM Wednesday, 1/27/2010, John Wilcock wrote -= Le 27/01/2010 18:57, Justin Mason a écrit : Either someone forgot to delete all these rules, or (more likely IMO) someone forgot to include 72_active.cf and 80_additional.cf in the sa-update files. I think you're dead right. It appears one of the build scripts does the wrong thing with the 3.3.0 release, and cut an update missing those files. :( I've just cut a new update which should fix it, and opened a bug to fix the build procedure... sa-update has now pulled down a 72_active.cf file, and lint now only gives 5 score set for non-existent rule warnings instead of 463. Thanks Justin. And I thought it was just me ;-) Actually - it went down to about 7 or 8 here after I ran sa-update around 10:00pm pacific Ed ~ Randomly Generated Quote (1159 of 1230): When I woke up this morning my wife asked me, Did you sleep good? I said, No, I made a few mistakes. --Steven Wright
Re: Fuzzyocr and rule errors after upgrade to 3.3.0
Le 27/01/2010 22:31, Kai Schaetzl a écrit : John Wilcock wrote on Wed, 27 Jan 2010 17:43:56 +0100: someone forgot to include 72_active.cf and 80_additional.cf in the sa-update files. Now I understand. However, why am I not getting these warnings with a spamassassin --lint? Presumably because you didn't run sa-update while the ruleset was missing from the update... John. -- -- Over 4000 webcams from ski resorts around the world - www.snoweye.com -- Translate your technical documents and web pages- www.tradoc.fr
Re: Trouble after upgrade
Quoting john ffitch j...@codemist.co.uk: After attempting to move to Sa 3.3.0 water:~ # /etc/cron.daily/sa-update http: GET http://yerp.org/rules/stage/330903380.tar.gz request failed: 404 Not Found: !DOCTYPE HTML PUBLIC -//IETF//DTD HTML 2.0//EN htmlhead title404 Not Found/title /headbody h1Not Found/h1 pThe requested URL /rules/stage/330903380.tar.gz was not found on this server./p hr addressApache/2.2.8 (Ubuntu) DAV/2 SVN/1.4.6 PHP/5.2.4-2ubuntu5.9 with Suhosin-Patch mod_ssl/2.2.8 OpenSSL/0.9.8g mod_watch/4.3 Server at yerp.org Port 80/address /body/html channel: could not find working mirror, channel failed What sould I do next? ==John ffitch use http://yerp.org/rules/stage/330903281.tar.gz
***** SPAM ***** Re: Trouble after upgrade
On Tue, 26 Jan 2010 15:13:53 -0500, you wrote: Quoting john ffitch j...@codemist.co.uk: After attempting to move to Sa 3.3.0 water:~ # /etc/cron.daily/sa-update http: GET http://yerp.org/rules/stage/330903380.tar.gz request failed: 404 Not Found: !DOCTYPE HTML PUBLIC -//IETF//DTD HTML 2.0//EN htmlhead title404 Not Found/title /headbody h1Not Found/h1 pThe requested URL /rules/stage/330903380.tar.gz was not found on this server./p hr addressApache/2.2.8 (Ubuntu) DAV/2 SVN/1.4.6 PHP/5.2.4-2ubuntu5.9 with Suhosin-Patch mod_ssl/2.2.8 OpenSSL/0.9.8g mod_watch/4.3 Server at yerp.org Port 80/address /body/html channel: could not find working mirror, channel failed What sould I do next? ==John ffitch use http://yerp.org/rules/stage/330903281.tar.gz David: I'm seeing it here also with sa-update -D --gpgkey 6C6191E3 --channel sought.rules.yerp.org Where is this edit getting made? by the channel line or ??? And will this auto update somehow in the future to fix itself? -- ===[George R. Kasica]===+1 262 677 0766 President +1 206 374 6482 FAX Netwrx Consulting Inc. Jackson, WI USA http://www.netwrx1.com geor...@netwrx1.com ICQ #12862186
Fuzzyocr and rule errors after upgrade to 3.3.0
I just upgraded to 3.3.0 from 3.2.4 and get the following errors:
Jan 26 22:10:41.856 [32397] dbg: plugin: loading FuzzyOcr from
/etc/mail/spamassassin/FuzzyOcr.pm
Jan 26 22:10:42.038 [32397] warn: plugin: eval failed: Insecure
dependency in open while running with -T switch at
/etc/mail/spamassassin/FuzzyOcr/Logging.pm line 34.
Jan 26 22:10:42.039 [32397] warn: config: failed to parse line,
skipping, in /etc/mail/spamassassin/FuzzyOcr.cf: focr_bin_helper
pnmnorm, pnminvert, pamditherbw, ppmtopgm, pamtopnm
Jan 26 22:10:42.044 [32397] warn: plugin: eval failed: Insecure
dependency in open while running with -T switch at
/etc/mail/spamassassin/FuzzyOcr/Logging.pm line 34.
Here is line 34-37:
34unless ( open LOGFILE, , $conf-{focr_logfile} ) {
35 warn Can't open $conf-{focr_logfile} for writing, check
permissions;
36 return;
37}
The plugin was doing fine in 3.2.4. I could not find much in the
archives on the errors so I thought I'd throw it out there to see if
anyone had any suggestions.
Also - is anyone else getting a lot of warning: score set for
non-existent rule errors? I ran sa-update after teand continue to
get a slew of them...
Ed
...
Randomly Generated Quote (1413 of 1582):
Truth has no special time of its own. Its hour is now -- always.
-Albert Schweitzer (1875-1965)
Re: Spamassassin not working after upgrade
This seems to have been SELinux related. When I temporarily disable it,
procmail is able to execute spamc and properly filter incoming messages.
Thanks for the suggestion. This is a huge relief!
Best,
Greg
Karsten Bräckelmann-2 wrote:
I recently upgraded to spamassassin-3.2.5-1.el5 using up2date and
spamassassin is no longer filtering messages. Spamassassin correctly
identifies the sample spam message when I do
[...]
I've googled extensively to see if anyone else is having this problem and
what possible solutions might be, but nothing that I've tried (changing
config files, restarting spamd, etc.) has worked.
Uhm, according to your procmail logs below, you are not using spamd
anyway. I do however strongly recommend to do so -- that is, in procmail
use spamc instead of 'spamassassin'.
This will result in less load on the server and faster mail processing,
since spamassassin doesn't have to be started for each mail. The spamd
daemon needs to be running for that. (Yes, this isn't related to the
issue at hand.)
Here is the relevant part of the log file for a sample email after
turning
the verbose option on in .procmailrc:
procmail: Executing /usr/bin/spamassassin
/bin/sh: /usr/bin/spamassassin: Permission denied
procmail: Program failure (126) of /usr/bin/spamassassin
procmail: Rescue of unfiltered data succeeded
RHEL5. Any chance this problem is SELinux related?
--
char
*t=\10pse\0r\0dtu...@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4;
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;il;i++){ i%8?
c=1:
(c=*++x); c128 (s+=h); if (!(h=1)||!t[s+h]){ putchar(t[s]);h=m;s=0;
}}}
--
View this message in context:
http://www.nabble.com/Spamassassin-not-working-after-upgrade-tp21982029p21999350.html
Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
Re: Spamassassin not working after upgrade
This seems to have been SELinux related. When I temporarily disable it,
procmail is able to execute spamc and properly filter incoming messages.
Thanks for the suggestion. This is a huge relief!
Ah, goodie. :) Please file a bug with RH against SELinux, for both
permission denied issues (spamassassin and spamc) when called from
procmail.
Karsten Bräckelmann wrote:
procmail: Executing /usr/bin/spamassassin
/bin/sh: /usr/bin/spamassassin: Permission denied
procmail: Program failure (126) of /usr/bin/spamassassin
procmail: Rescue of unfiltered data succeeded
RHEL5. Any chance this problem is SELinux related?
--
char *t=\10pse\0r\0dtu...@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4;
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;il;i++){ i%8? c=1:
(c=*++x); c128 (s+=h); if (!(h=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}
Re: Spamassassin not working after upgrade
:0wf
| /usr/bin/spamassassin
If there is even the slightest chance for a mail surge -- you probably
should add a lock file to that recipe. (Not to mention using spamc
again, which you appear to already have switched to. ;)
--
char *t=\10pse\0r\0dtu...@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4;
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;il;i++){ i%8? c=1:
(c=*++x); c128 (s+=h); if (!(h=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}
Spamassassin not working after upgrade
Hello, I recently upgraded to spamassassin-3.2.5-1.el5 using up2date and spamassassin is no longer filtering messages. Spamassassin correctly identifies the sample spam message when I do spamassassin -D /usr/share/doc/spamassassin-3.2.5/sample-spam.txt from the command line, but it does not tag the GTUBE email when I send it to myself from an external email account. It doesn't look like sendmail/procmail is sending the mail through spamassassin, although it's not clear to me why not. I didn't change anything in my config files and the upgrade notes for spamassassin did not indicate that anything should be changed. I've googled extensively to see if anyone else is having this problem and what possible solutions might be, but nothing that I've tried (changing config files, restarting spamd, etc.) has worked. Here is the relevant part of the log file for a sample email after turning the verbose option on in .procmailrc: procmail: Assigning DROPPRIVS=yes procmail: Assuming identity of the recipient, VERBOSE=off procmail: Assigning PATH=/bin:/usr/bin:/usr/local/bin procmail: Assigning SHELL=/bin/sh procmail: Executing /usr/bin/spamassassin /bin/sh: /usr/bin/spamassassin: Permission denied procmail: Program failure (126) of /usr/bin/spamassassin procmail: Rescue of unfiltered data succeeded I'm still stumped, however. The permissions for spamassassin seem to be correct: -rwxr-xr-x 1 root root 27021 Sep 14 18:29 /usr/bin/spamassassin I can run it from the command line, so I'm not sure why I'm still getting permission denied. Do I need to change the ownership of spamassassin? I tried changing the group to mail (same group as procmail), but that didn't do anything. I could only find one relevant posting with a similar error (located here http://use.perl.org/~samtregar/journal/29278), but that doesn't sound like my problem. Thanks for any suggestions. -- View this message in context: http://www.nabble.com/Spamassassin-not-working-after-upgrade-tp21982029p21982029.html Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
Re: Spamassassin not working after upgrade
On Thu, 12 Feb 2009, nycsurf wrote: Here is the relevant part of the log file for a sample email after turning the verbose option on in .procmailrc: procmail: Assigning DROPPRIVS=yes procmail: Assuming identity of the recipient, VERBOSE=off procmail: Assigning PATH=/bin:/usr/bin:/usr/local/bin procmail: Assigning SHELL=/bin/sh procmail: Executing /usr/bin/spamassassin /bin/sh: /usr/bin/spamassassin: Permission denied procmail: Program failure (126) of /usr/bin/spamassassin procmail: Rescue of unfiltered data succeeded I'm still stumped, however. The permissions for spamassassin seem to be correct: -rwxr-xr-x 1 root root 27021 Sep 14 18:29 /usr/bin/spamassassin Can you post the procmail ruleset that tries to run spamassassin? And, not to suggest changing many things at once, but is there some reason you're not using spamc/spamd? -- John Hardin KA7OHZhttp://www.impsec.org/~jhardin/ jhar...@impsec.orgFALaholic #11174 pgpk -a jhar...@impsec.org key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79 --- You are in a maze of twisty little protocols, all written by Microsoft. -- Today: Abraham Lincoln's and Charles Darwin's 200th Birthdays
Re: Spamassassin not working after upgrade
I recently upgraded to spamassassin-3.2.5-1.el5 using up2date and
spamassassin is no longer filtering messages. Spamassassin correctly
identifies the sample spam message when I do
[...]
I've googled extensively to see if anyone else is having this problem and
what possible solutions might be, but nothing that I've tried (changing
config files, restarting spamd, etc.) has worked.
Uhm, according to your procmail logs below, you are not using spamd
anyway. I do however strongly recommend to do so -- that is, in procmail
use spamc instead of 'spamassassin'.
This will result in less load on the server and faster mail processing,
since spamassassin doesn't have to be started for each mail. The spamd
daemon needs to be running for that. (Yes, this isn't related to the
issue at hand.)
Here is the relevant part of the log file for a sample email after turning
the verbose option on in .procmailrc:
procmail: Executing /usr/bin/spamassassin
/bin/sh: /usr/bin/spamassassin: Permission denied
procmail: Program failure (126) of /usr/bin/spamassassin
procmail: Rescue of unfiltered data succeeded
RHEL5. Any chance this problem is SELinux related?
--
char *t=\10pse\0r\0dtu...@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4;
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;il;i++){ i%8? c=1:
(c=*++x); c128 (s+=h); if (!(h=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}
Re: Spamassassin not working after upgrade
On Thu, 12 Feb 2009, nycsurf wrote:
Spamassassin correctly identifies the sample spam message when I do
spamassassin -D /usr/share/doc/spamassassin-3.2.5/sample-spam.txt
Does /usr/bin/spamassassin behave properly from the command line?
{sorry for two messages}
procmail: Executing /usr/bin/spamassassin
/bin/sh: /usr/bin/spamassassin: Permission denied
--
John Hardin KA7OHZhttp://www.impsec.org/~jhardin/
jhar...@impsec.orgFALaholic #11174 pgpk -a jhar...@impsec.org
key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79
---
You are in a maze of twisty little protocols,
all written by Microsoft.
--
Today: Abraham Lincoln's and Charles Darwin's 200th Birthdays
Re: Spamassassin not working after upgrade
Can you post the procmail ruleset that tries to run spamassassin? I've been trying several different rulesets. Here's the latest: LOGFILE=/home/gjw10/mail/maillog VERBOSE=on PATH=/bin:/usr/bin:/usr/local/bin SHELL=/bin/sh :0wf | /usr/bin/spamassassin :0: * ^X-Spam-Level: \*\*\*\*\*\*\*\*\*\*\*\*\*\*\* mail/almost-certainly-spam And, not to suggest changing many things at once, but is there some reason you're not using spamc/spamd? I just kept what I was using under the previous version of spamassassin--figured if it wasn't broke, etc. I have tried changing .procmailrc to use spamc, but I'm getting the same permission denied error--i.e., it complains: /bin/sh: /usr/bin/spamc: Permission denied procmail: Program failure (126) of /usr/bin/spamc -- View this message in context: http://www.nabble.com/Spamassassin-not-working-after-upgrade-tp21982029p21983006.html Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
Re: No URIBL after upgrade to 3.2.4
On 02/04/08 16:33, [EMAIL PROTECTED] (Daryl C. W. O'Shea) wrote: Christopher Bort wrote: I have recently upgraded a SpamAssassin installation from 3.2.1 to 3.2.4. Since then URIBL hits have dropped to nearly zero, where before there were several hundred per day. Immediately after the upgrade, there were a handful of hits on URIBL_BLACK, but I have not seen any at all in the last few days. No configs have been changed with the upgrade, but sa_update is run nightly via cron. Run a message that you expect an URIBL hit on through spamassassin -D and look at the debug output to find out what is going on. Curious. A message that was run through SA by my mail server's helper without hits on any URIBL or RAZOR2 rules gets hits on multiple URIBL and RAZOR2 rules when fed to spamassassin -D manually. I will look into the possibility that the server's helper program is either misconfigured or is doing something wrong. Whatever it is doesn't seem terribly consistent at this point, though, because I continue to get plenty of RAZOR2 hits and a small handful of URIBL hits. At any rate, it warrants further investigation... Thank you for your help. -- Christopher Bort [EMAIL PROTECTED] http://www.thehundredacre.net/
No URIBL after upgrade to 3.2.4
I have recently upgraded a SpamAssassin installation from 3.2.1 to 3.2.4. Since then URIBL hits have dropped to nearly zero, where before there were several hundred per day. Immediately after the upgrade, there were a handful of hits on URIBL_BLACK, but I have not seen any at all in the last few days. No configs have been changed with the upgrade, but sa_update is run nightly via cron. The upgrade was done with CPAN, after first making sure that all relevant Perl modules were up to date. Google doesn't show me anything about problems with URIBL and SA 3.2.4, so I'm inclined to think there's a problem with my particular installation. I'm getting hits on Razor rules, so other network checks are working, and I do have 'loadplugin Mail::SpamAssassin::Plugin::URIDNSBL' in my init.pre. I'm not sure where to look next and I'd be grateful to be pointed in the right direction.
Re: No URIBL after upgrade to 3.2.4
Christopher Bort wrote: I have recently upgraded a SpamAssassin installation from 3.2.1 to 3.2.4. Since then URIBL hits have dropped to nearly zero, where before there were several hundred per day. Immediately after the upgrade, there were a handful of hits on URIBL_BLACK, but I have not seen any at all in the last few days. No configs have been changed with the upgrade, but sa_update is run nightly via cron. Run a message that you expect an URIBL hit on through spamassassin -D and look at the debug output to find out what is going on. Daryl
Re: Perl error after upgrade to 3.2.3
It is definately Sys:Syslog causing the problem. If you look in the actual spamd file, it gives some indication of this. I found that if I specified my log file options in the spamassassin options files that the problem is resolved. Add something like -s /var/log/spam.d to the existing options and the error clears. bw - Rank1st Neil-27 wrote: Hi; I've seen this as well. I did a cpan upgrade and upgraded all perl mods on a BSD, but not SA which was at 3.2.3. I think that may be due to an issue with Sys:Syslog v0.20 SA seems to be working fine, as you say. [96054] error: Can't locate Sys/Syslog/Win32.pm in @INC (@INC contains: /usr/local/lib/perl5/site_perl/5.8.8 /usr/local/lib/perl5/5.8.8/BSDPAN /usr/local/lib/perl5/site_perl/5.8.8/mach /usr/local/lib/perl5/site_perl /usr/local/lib/perl5/5.8.8/mach /usr/local/lib/perl5/5.8.8) at (eval 14) line 2. [96054] error: BEGIN failed--compilation aborted at (eval 14) line 2. rgds n Jonathan Armitage wrote: Apologies if I am asking in the wrong place, since I can see that there are several possible reasons. We have just upgraded to SpamAssassin 3.2.3 on an elderly 386 box running Red Hat 9. At the same time I used CPAN to upgrade any out-of-date perl modules. Now, when SA starts, we get the following error: Starting SpamAssassin daemon... [23172] error: Can't locate Sys/Syslog/Win32.pm in @INC (@INC contains: /usr/local/lib/perl5/site_perl/5.8.8/i686-linux /usr/local/lib/perl5/site_perl/5.8.8 /usr/local/lib/perl5/5.8.8/i686-linux /usr/local/lib/perl5/5.8.8 /usr/local/lib/perl5/site_perl) at (eval 11) line 2. [23172] error: BEGIN failed--compilation aborted at (eval 11) line 2. done. The error comes up twice, but SA does in fact start, and appears to be functioning normally. Does anyone know why it suddenly wants to load a Win32 module? Jon Jon Armitage System Administrator, 365 Media Group -- View this message in context: http://www.nabble.com/Perl-error-after-upgrade-to-3.2.3-tf4428549.html#a12942940 Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
Perl error after upgrade to 3.2.3
Apologies if I am asking in the wrong place, since I can see that there are several possible reasons. We have just upgraded to SpamAssassin 3.2.3 on an elderly 386 box running Red Hat 9. At the same time I used CPAN to upgrade any out-of-date perl modules. Now, when SA starts, we get the following error: Starting SpamAssassin daemon... [23172] error: Can't locate Sys/Syslog/Win32.pm in @INC (@INC contains: /usr/local/lib/perl5/site_perl/5.8.8/i686-linux /usr/local/lib/perl5/site_perl/5.8.8 /usr/local/lib/perl5/5.8.8/i686-linux /usr/local/lib/perl5/5.8.8 /usr/local/lib/perl5/site_perl) at (eval 11) line 2. [23172] error: BEGIN failed--compilation aborted at (eval 11) line 2. done. The error comes up twice, but SA does in fact start, and appears to be functioning normally. Does anyone know why it suddenly wants to load a Win32 module? Jon Jon Armitage System Administrator, 365 Media Group
Re: Perl error after upgrade to 3.2.3
Hi; I've seen this as well. I did a cpan upgrade and upgraded all perl mods on a BSD, but not SA which was at 3.2.3. I think that may be due to an issue with Sys:Syslog v0.20 SA seems to be working fine, as you say. [96054] error: Can't locate Sys/Syslog/Win32.pm in @INC (@INC contains: /usr/local/lib/perl5/site_perl/5.8.8 /usr/local/lib/perl5/5.8.8/BSDPAN /usr/local/lib/perl5/site_perl/5.8.8/mach /usr/local/lib/perl5/site_perl /usr/local/lib/perl5/5.8.8/mach /usr/local/lib/perl5/5.8.8) at (eval 14) line 2. [96054] error: BEGIN failed--compilation aborted at (eval 14) line 2. rgds n Jonathan Armitage wrote: Apologies if I am asking in the wrong place, since I can see that there are several possible reasons. We have just upgraded to SpamAssassin 3.2.3 on an elderly 386 box running Red Hat 9. At the same time I used CPAN to upgrade any out-of-date perl modules. Now, when SA starts, we get the following error: Starting SpamAssassin daemon... [23172] error: Can't locate Sys/Syslog/Win32.pm in @INC (@INC contains: /usr/local/lib/perl5/site_perl/5.8.8/i686-linux /usr/local/lib/perl5/site_perl/5.8.8 /usr/local/lib/perl5/5.8.8/i686-linux /usr/local/lib/perl5/5.8.8 /usr/local/lib/perl5/site_perl) at (eval 11) line 2. [23172] error: BEGIN failed--compilation aborted at (eval 11) line 2. done. The error comes up twice, but SA does in fact start, and appears to be functioning normally. Does anyone know why it suddenly wants to load a Win32 module? Jon Jon Armitage System Administrator, 365 Media Group
Scan Time Problem After Upgrade
We began upgrading to 3.2.3 from 3.2.1. There are 5 machines. On the first machine prior to the upgrade the average scan time for a message was 2 to 4 seconds, fairly consistent at 2.5 or so seconds. After upgrading the same systems now have a scan time of 7 or more seconds. Not sure if this was a message related issue so we upgraded the second machine that was running the same way. Again, after the upgrade the scan times doubled our more. We then downgraded back to 3.2.1 on the first machine and the scan times went back to the lower time. Everything looks like it's configured the same way. Anyone know what we may be experiencing? GA -- View this message in context: http://www.nabble.com/Scan-Time-Problem-After-Upgrade-tf4429657.html#a12636664 Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
Re: Errors after upgrade to 3.2.2
Frank Bures wrote: After yesterday upgrade to 3.2.2 I am seeing these in the logs (upon spamd restart): spamd[19878]: rules: meta test FM__TIMES_2 has dependency 'FH_HOST_EQ_D_D_D_D' with a zero score spamd[19878]: rules: meta test FM_SEX_HOST has dependency 'FH_HOST_EQ_D_D_D_D' with a zero score Any solution or ideas? Ignore it. It's just rule debug info. Daryl
Errors after upgrade to 3.2.2
After yesterday upgrade to 3.2.2 I am seeing these in the logs (upon spamd restart): spamd[19878]: rules: meta test FM__TIMES_2 has dependency 'FH_HOST_EQ_D_D_D_D' with a zero score spamd[19878]: rules: meta test FM_SEX_HOST has dependency 'FH_HOST_EQ_D_D_D_D' with a zero score Any solution or ideas? Thanks Frank [EMAIL PROTECTED]
Issues after upgrade Debian from sarge to etch
Hello list! I'm new here so please be nice to me :) Since I upgraded my box to debian etch I have the same errors day by day. I'm running SpamAssassin version 3.2.0 running on Perl version 5.8.8 (standard etch-package) with amavisd-new-2.4.2 (20060627) (also etch-pack). There is a cronjob bundled with amavis which invokes 'spamassassin --lint' once in a while. Command: test -e /usr/sbin/amavisd-new-cronjob /usr/sbin/amavisd-new-cronjob sa-sync The cronjob fails with this message(s): +++ snip plugin: failed to parse plugin (from @INC): Bareword Mail::SpamAssassin::Constants::CHARSETS_LIKELY_TO_FP_AS_CAPS not allowed while strict subs in use at /usr/local/share/perl/5.8.8/Mail/SpamAssassin/Plugin/HeaderEval.pm line 965. Compilation failed in require at (eval 70) line 1. plugin: failed to create instance of plugin Mail::SpamAssassin::Plugin::HeaderEval: Can't locate object method new via package Mail::SpamAssassin::Plugin::HeaderEval at /usr/local/share/perl/5.8.8/Mail/SpamAssassin/Plugin/HeaderEval.pm line 39. plugin: failed to parse plugin (from @INC): CHARSETS_LIKELY_TO_FP_AS_CAPS is not exported by the Mail::SpamAssassin::Constants module Can't continue after import errors at /usr/local/share/perl/5.8.8/Mail/SpamAssassin/Plugin/MIMEEval.pm line 22 BEGIN failed--compilation aborted at /usr/local/share/perl/5.8.8/Mail/SpamAssassin/Plugin/MIMEEval.pm line 22. Compilation failed in require at (eval 72) line 1. plugin: failed to create instance of plugin Mail::SpamAssassin::Plugin::MIMEEval: Can't locate object method new via package Mail::SpamAssassin::Plugin::MIMEEval at (eval 73) line 1. +++ /snip Since I'm barely familiar to perl I couldn't get my self rid of these errors. Although spamassassin and amavis work fine together. Can anyone help me out? Thanks in advance, Stefan signature.asc Description: OpenPGP digital signature
Re: Issues after upgrade Debian from sarge to etch
Stefan Hoth wrote: Since I upgraded my box to debian etch I have the same errors day by day. I'm running SpamAssassin version 3.2.0 running on Perl version 5.8.8 (standard etch-package) with amavisd-new-2.4.2 (20060627) (also etch-pack). Hmm... I know you said standard Etch packages but those versions do not match the versions in Etch. They match the versions in Testing. Therefore I conclude that you are actually running Debian testing. For various reasons I recommend Debian Stable (currently Etch) or Debian Unstable (always named Sid). I can't recommend Testing for production use. Command: test -e /usr/sbin/amavisd-new-cronjob /usr/sbin/amavisd-new-cronjob sa-sync ... plugin: failed to parse plugin (from @INC): Bareword Mail::SpamAssassin::Constants::CHARSETS_LIKELY_TO_FP_AS_CAPS not allowed while strict subs in use at /usr/local/share/perl/5.8.8/Mail/SpamAssassin/Plugin/HeaderEval.pm line 965. Compilation failed in require at (eval 70) line 1. Because this file is installed in /usr/local I know that it is not the Debian packaged version but is instead a direct local installation. That is fine. But this is an indication of a typical problem. Often when multiple versions of perl modules are installed simultaneously this will create version mismatch problems. It is certainly possible to install multiple versions but there have also been a lot of reports of problems in those cases too. Since I'm barely familiar to perl I couldn't get my self rid of these errors. Although spamassassin and amavis work fine together. Please check and see if you have SA installed multiple different ways, by package and by direct installation (e.g. CPAN). If you have multiple versions of SpamAssassin installed I suggest removing all of the ones that you are not using. Bob
Re: Issues after upgrade Debian from sarge to etch [SOLVED]
Hello! Hmm... I know you said standard Etch packages but those versions do not match the versions in Etch. They match the versions in Testing. Therefore I conclude that you are actually running Debian testing. Didn't think so but obviously I must mess things up while experimenting with amavisd-new (and spamassassin plugins). For various reasons I recommend Debian Stable (currently Etch) or Debian Unstable (always named Sid). I can't recommend Testing for production use. I know and I agree - my sources.list is only linked to etch - but maybe there was a short time when I had testing in it. Please check and see if you have SA installed multiple different ways, by package and by direct installation (e.g. CPAN). If you have multiple versions of SpamAssassin installed I suggest removing all of the ones that you are not using. Bob, you made my day - thank you! After checking my installation with your hints I could cleanup some cpan-installed modules and replaced the testing-version with the version from the etch repository. Finally I got rid of this error messages. Thank you all for your help! Stefan signature.asc Description: OpenPGP digital signature
RE: Error on startup after upgrade to 3.2.1:CompiledRegexps
On Wednesday, Jun 13th 2007 at 17:14 -0400, quoth Rosenbaum, Larry M.: = From: Steven W. Orr [mailto:[EMAIL PROTECTED] = = [EMAIL PROTECTED] ~]# rpm -Uvh = /usr/src/redhat/RPMS/i386/spamassassin-3.2.1-1.i386.rpm = /usr/src/redhat/RPMS/i386/perl-Mail-SpamAssassin-3.2.1-1.i386.rpm = Preparing... =### = [100%] = 1:perl-Mail-SpamAssassin = ### [ 50%] = 2:spamassassin = ### [100%] = Stopping spamd: [ OK ] = Starting spamd: [13775] error: Can't locate = Mail/SpamAssassin/CompiledRegexps/body_0.pm in @INC (@INC contains: =... = = Am I concerned? Where is CompiledRegexps supposed to be and why is it = not = there? = =I think it means you have Rule2XSBody uncommented in v320.pre but you =don't have a compiled ruleset. Perhaps you ran sa-compile under v3.2.0 =but you haven't run it under v3.2.1. Thanks to Larry for the answer. This leads to a question about how SA is packaged: I downloaded the tarfile and built an rpm. When I installed the rpm, the rpm was smart enough to restart SA. Should this postinst code in the rpm not also have rerun sa-compile before the restart? Seems logical to me. -- Time flies like the wind. Fruit flies like a banana. Stranger things have .0. happened but none stranger than this. Does your driver's license say Organ ..0 Donor?Black holes are where God divided by zero. Listen to me! We are all- 000 individuals! What if this weren't a hypothetical question? steveo at syslang.net
Re: Error on startup after upgrade to 3.2.1:CompiledRegexps
On Thu, Jun 14, 2007 at 08:45:17AM -0400, Steven W. Orr wrote: I downloaded the tarfile and built an rpm. When I installed the rpm, the rpm was smart enough to restart SA. Should this postinst code in the rpm not also have rerun sa-compile before the restart? Seems logical to me. The script has no way to know how you're doing your config, so I wouldn't expect it to compile rules automatically in the same way that I wouldn't expect it to run sa-update or any other do something with my configs program automatically. -- Randomly Selected Tagline: They sell cans of fresh Maine air ... probably vacuum-sealed. - Theo pgpRW1Vu0CvaH.pgp Description: PGP signature
Re: Errors in logs after upgrade from debian sarge to etch
Ok, I saw the upgrade file. I've done quite a bit of modifications on the local.cf file. But I still get a bunch of errors when restarting spamd. Any help ? Le mardi 12 juin 2007 à 21:06 +0200, LESOUEF Emmanuel a écrit : Hello, After upgrading SA from 3.0 to 3.1, I get the attached logs when I restart spamd. This seems to be a configuration error. In fact, the local.cf file has been wrote for the 3.0 version. Can someone help me with it ? Thanks. -- Emmanuel Lesouef DSI | CRBN t : 0231069671 m : [EMAIL PROTECTED] -- Emmanuel Lesouef CRBN | DSI t : 0231069671 m : [EMAIL PROTECTED]
Error on startup after upgrade to 3.2.1:CompiledRegexps
[EMAIL PROTECTED] ~]# rpm -Uvh /usr/src/redhat/RPMS/i386/spamassassin-3.2.1-1.i386.rpm /usr/src/redhat/RPMS/i386/perl-Mail-SpamAssassin-3.2.1-1.i386.rpm Preparing...### [100%] 1:perl-Mail-SpamAssassin ### [ 50%] 2:spamassassin ### [100%] Stopping spamd: [ OK ] Starting spamd: [13775] error: Can't locate Mail/SpamAssassin/CompiledRegexps/body_0.pm in @INC (@INC contains: /var/lib/spamassassin/compiled/3.002001 /var/lib/spamassassin/compiled/3.002001/auto lib /usr/lib/perl5/site_perl/5.8.6/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.6 /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.4/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.3/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.5 /usr/lib/perl5/site_perl/5.8.4 /usr/lib/perl5/site_perl/5.8.3 /usr/lib/perl5/site_perl /usr/lib/perl5/vendor_perl/5.8.6/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.4/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.3/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.6 /usr/lib/perl5/vendor_perl/5.8.5 /usr/lib/perl5/vendor_perl/5.8.4 /usr/lib/perl5/vendor_perl/5.8.3 /usr/lib/perl5/vendor_perl /usr/lib/perl5/5.8.6/i386-linux-thread-multi /usr/lib/perl5/5.8.6) at (eval 570) line 1. [ OK ] Am I concerned? Where is CompiledRegexps supposed to be and why is it not there? TIA -- Time flies like the wind. Fruit flies like a banana. Stranger things have .0. happened but none stranger than this. Does your driver's license say Organ ..0 Donor?Black holes are where God divided by zero. Listen to me! We are all- 000 individuals! What if this weren't a hypothetical question? steveo at syslang.net
RE: Error on startup after upgrade to 3.2.1:CompiledRegexps
From: Steven W. Orr [mailto:[EMAIL PROTECTED] [EMAIL PROTECTED] ~]# rpm -Uvh /usr/src/redhat/RPMS/i386/spamassassin-3.2.1-1.i386.rpm /usr/src/redhat/RPMS/i386/perl-Mail-SpamAssassin-3.2.1-1.i386.rpm Preparing... ### [100%] 1:perl-Mail-SpamAssassin ### [ 50%] 2:spamassassin ### [100%] Stopping spamd: [ OK ] Starting spamd: [13775] error: Can't locate Mail/SpamAssassin/CompiledRegexps/body_0.pm in @INC (@INC contains: ... Am I concerned? Where is CompiledRegexps supposed to be and why is it not there? I think it means you have Rule2XSBody uncommented in v320.pre but you don't have a compiled ruleset. Perhaps you ran sa-compile under v3.2.0 but you haven't run it under v3.2.1.
Errors in logs after upgrade from debian sarge to etch
Hello, After upgrading SA from 3.0 to 3.1, I get the attached logs when I restart spamd. This seems to be a configuration error. In fact, the local.cf file has been wrote for the 3.0 version. Can someone help me with it ? Thanks. -- Emmanuel Lesouef DSI | CRBN t : 0231069671 m : [EMAIL PROTECTED] Jun 12 17:58:58 adele spamd[25024]: spamd: server killed by SIGTERM, shutting down Jun 12 17:58:59 adele spamd[25038]: logger: removing stderr method Jun 12 17:58:59 adele spamd[25040]: config: score: the non-numeric score (.85) is not valid, a numeric score is required Jun 12 17:58:59 adele spamd[25040]: config: SpamAssassin failed to parse line, MY_DSL .85 is not valid for score, skipping: score MY_DSL .85 Jun 12 17:58:59 adele spamd[25040]: config: score: the non-numeric score (.25) is not valid, a numeric score is required Jun 12 17:58:59 adele spamd[25040]: config: SpamAssassin failed to parse line, AOL_DSL .25 is not valid for score, skipping: score AOL_DSL .25 Jun 12 17:58:59 adele spamd[25040]: config: score: the non-numeric score (.75) is not valid, a numeric score is required Jun 12 17:58:59 adele spamd[25040]: config: SpamAssassin failed to parse line, SARE_FROM_SPAM_WORD3 .75 is not valid for score, skipping: score SARE_FROM_SPAM_WORD3 .75 Jun 12 17:58:59 adele spamd[25040]: config: score: the non-numeric score (.43) is not valid, a numeric score is required Jun 12 17:58:59 adele spamd[25040]: config: SpamAssassin failed to parse line, SALES_REPLY .43 is not valid for score, skipping: score SALES_REPLY .43 Jun 12 17:58:59 adele spamd[25040]: config: failed to parse line, skipping: rewrite_subject 1 Jun 12 17:58:59 adele spamd[25040]: config: failed to parse line, skipping: subject_tag ~~~SPAM:~~~ Jun 12 17:58:59 adele spamd[25040]: config: failed to parse line, skipping: auto_learn 1 Jun 12 17:58:59 adele spamd[25040]: config: failed to parse, now a plugin, skipping: ok_languages all Jun 12 17:58:59 adele spamd[25040]: Use of uninitialized value in substitution (s///) at /usr/share/perl5/Mail/SpamAssassin/Conf/Parser.pm line 851. Jun 12 17:58:59 adele spamd[25040]: Use of uninitialized value in pattern match (m//) at /usr/share/perl5/Mail/SpamAssassin/Conf/Parser.pm line 924. Jun 12 17:58:59 adele spamd[25040]: Use of uninitialized value in concatenation (.) or string at /usr/share/perl5/Mail/SpamAssassin/Conf/Parser.pm line 925. Jun 12 17:58:59 adele spamd[25040]: config: invalid regexp for rule LOCAL_DEMONSTRATION_RULE: : missing or invalid delimiters Jun 12 17:59:03 adele spamd[25040]: rules: meta test DIGEST_MULTIPLE has undefined dependency 'DCC_CHECK' Jun 12 17:59:03 adele spamd[25040]: rules: meta test SARE_FROM_FREE has undefined dependency '__MR_LEGIT_FREE' Jun 12 17:59:03 adele spamd[25040]: rules: meta test NIGERIAN_BODY_2 has undefined dependency '__NIGERIAN_BODY_1' Jun 12 17:59:03 adele spamd[25040]: rules: meta test NIGERIAN_BODY_2 has undefined dependency '__NIGERIAN_BODY_2' Jun 12 17:59:03 adele spamd[25040]: rules: meta test NIGERIAN_BODY_2 has undefined dependency '__NIGERIAN_BODY_3' Jun 12 17:59:03 adele spamd[25040]: rules: meta test NIGERIAN_BODY_2 has undefined dependency '__NIGERIAN_BODY_5' Jun 12 17:59:03 adele spamd[25040]: rules: meta test NIGERIAN_BODY_2 has undefined dependency '__NIGERIAN_BODY_6' Jun 12 17:59:03 adele spamd[25040]: rules: meta test NIGERIAN_BODY_2 has undefined dependency '__NIGERIAN_BODY_7' Jun 12 17:59:03 adele spamd[25040]: rules: meta test NIGERIAN_BODY_2 has undefined dependency '__NIGERIAN_BODY_8' Jun 12 17:59:03 adele spamd[25040]: rules: meta test NIGERIAN_BODY_2 has undefined dependency '__NIGERIAN_BODY_9' Jun 12 17:59:03 adele spamd[25040]: rules: meta test NIGERIAN_BODY_2 has undefined dependency '__NIGERIAN_BODY_10' Jun 12 17:59:03 adele spamd[25040]: rules: meta test NIGERIAN_BODY_2 has undefined dependency '__NIGERIAN_BODY_11' Jun 12 17:59:03 adele spamd[25040]: rules: meta test NIGERIAN_BODY_2 has undefined dependency '__NIGERIAN_BODY_12' Jun 12 17:59:03 adele spamd[25040]: rules: meta test NIGERIAN_BODY_2 has undefined dependency '__NIGERIAN_BODY_13' Jun 12 17:59:03 adele spamd[25040]: rules: meta test NIGERIAN_BODY_2 has undefined dependency '__NIGERIAN_BODY_14' Jun 12 17:59:03 adele spamd[25040]: rules: meta test NIGERIAN_BODY_2 has undefined dependency '__NIGERIAN_BODY_15' Jun 12 17:59:03 adele spamd[25040]: rules: meta test NIGERIAN_BODY_2 has undefined dependency '__NIGERIAN_BODY_16' Jun 12 17:59:03 adele spamd[25040]: rules: meta test NIGERIAN_BODY_2 has undefined dependency '__NIGERIAN_BODY_17' Jun 12 17:59:03 adele spamd[25040]: rules: meta test NIGERIAN_BODY_2 has undefined dependency '__NIGERIAN_BODY_18' Jun 12 17:59:03 adele spamd[25040]: rules: meta test NIGERIAN_BODY_2 has undefined dependency '__NIGERIAN_BODY_19' Jun 12 17:59:03 adele spamd[25040]: rules: meta test NIGERIAN_BODY_2 has undefined dependency '__NIGERIAN_BODY_20' Jun 12 17:59:03 adele spamd[25040]: rules: meta test
Re: Mail::SpamAssassin::PerMsgStatus::finish failing after upgrade from 3.1.7 to 3.2.0
Thanks Justin. I am embedding Perl inside a C program, so I hope this is still true. It used to return a non-NULL or at least the following call used to always return a count of 1 and not 0 like it is now after the SA upgrade. count = perl_call_method(Mail::SpamAssassin::PerMsgStatus::finish, (G_ARRAY|G_EVAL|G_KEEPERR)); Is your answer still the same? Thanks a lot! Joe Justin Mason wrote: hi Joe -- just ignore the return value of finish() -- it's a void method. (note how it doesn't mention a return value in its POD doc ;) --j. Joe Flowers writes: Hello Everyone, I'm getting a weird error message that I have never gotten before over several versions of SA. I just upgraded from SpamAssassin version 3.1.7 running on Perl version 5.8.8 to SpamAssassin version 3.2.0 running on Perl version 5.8.8. Now, my calls to Mail::SpamAssassin::PerMsgStatus::finish are failing; or at least, it looks like their has been some change in the return values by finish(). I have been running this programming over many iterations of SA and this is the first time I have run into such a problem. This worries me a lot because from the docs (http://spamassassin.apache.org/full/3.2.x/doc/Mail_SpamAssassin_PerMsgStatus.html): $status-finish () If you are using SpamAssassin in a persistent environment, or checking many mail messages from one Mail::SpamAssassin factory, this method should be called to ensure Perl's garbage collection will clean up old status objects. . These calls succeed as usual: Mail::SpamAssassin::PerMsgStatus::get_required_score Mail::SpamAssassin::PerMsgStatus::get_score Mail::SpamAssassin::PerMsgStatus::is_spam Mail::SpamAssassin::PerMsgStatus::get_names_of_tests_hit Mail::SpamAssassin::PerMsgStatus::finish would normally go here if it succeeded. Any ideas please? Joe
Re: Mail::SpamAssassin::PerMsgStatus::finish failing after upgrade from 3.1.7 to 3.2.0
hi Joe -- just ignore the return value of finish() -- it's a void method. (note how it doesn't mention a return value in its POD doc ;) --j. Joe Flowers writes: Hello Everyone, I'm getting a weird error message that I have never gotten before over several versions of SA. I just upgraded from SpamAssassin version 3.1.7 running on Perl version 5.8.8 to SpamAssassin version 3.2.0 running on Perl version 5.8.8. Now, my calls to Mail::SpamAssassin::PerMsgStatus::finish are failing; or at least, it looks like their has been some change in the return values by finish(). I have been running this programming over many iterations of SA and this is the first time I have run into such a problem. This worries me a lot because from the docs (http://spamassassin.apache.org/full/3.2.x/doc/Mail_SpamAssassin_PerMsgStatus.html): $status-finish () If you are using SpamAssassin in a persistent environment, or checking many mail messages from one Mail::SpamAssassin factory, this method should be called to ensure Perl's garbage collection will clean up old status objects. . These calls succeed as usual: Mail::SpamAssassin::PerMsgStatus::get_required_score Mail::SpamAssassin::PerMsgStatus::get_score Mail::SpamAssassin::PerMsgStatus::is_spam Mail::SpamAssassin::PerMsgStatus::get_names_of_tests_hit Mail::SpamAssassin::PerMsgStatus::finish would normally go here if it succeeded. Any ideas please? Joe
Re: Mail::SpamAssassin::PerMsgStatus::finish failing after upgrade from 3.1.7 to 3.2.0
Thanks a lot Justin. This is a big relief. I was worried that SA may fall apart on me today and this makes me feel a lot better. Thank you! Joe Justin Mason wrote: hi Joe -- yep, it is. In fact you should probably use the G_ flag for calling a method in void context, can't recall which one that is ;) --j. Joe Flowers writes: Thanks Justin. I am embedding Perl inside a C program, so I hope this is still true. It used to return a non-NULL or at least the following call used to always return a count of 1 and not 0 like it is now after the SA upgrade. count = perl_call_method(Mail::SpamAssassin::PerMsgStatus::finish, (G_ARRAY|G_EVAL|G_KEEPERR)); Is your answer still the same? Thanks a lot! Joe Justin Mason wrote: hi Joe -- just ignore the return value of finish() -- it's a void method. (note how it doesn't mention a return value in its POD doc ;) --j. Joe Flowers writes: Hello Everyone, I'm getting a weird error message that I have never gotten before over several versions of SA. I just upgraded from SpamAssassin version 3.1.7 running on Perl version 5.8.8 to SpamAssassin version 3.2.0 running on Perl version 5.8.8. Now, my calls to Mail::SpamAssassin::PerMsgStatus::finish are failing; or at least, it looks like their has been some change in the return values by finish(). I have been running this programming over many iterations of SA and this is the first time I have run into such a problem. This worries me a lot because from the docs (http://spamassassin.apache.org/full/3.2.x/doc/Mail_SpamAssassin_PerMsgStatus.html): $status-finish () If you are using SpamAssassin in a persistent environment, or checking many mail messages from one Mail::SpamAssassin factory, this method should be called to ensure Perl's garbage collection will clean up old status objects. . These calls succeed as usual: Mail::SpamAssassin::PerMsgStatus::get_required_score Mail::SpamAssassin::PerMsgStatus::get_score Mail::SpamAssassin::PerMsgStatus::is_spam Mail::SpamAssassin::PerMsgStatus::get_names_of_tests_hit Mail::SpamAssassin::PerMsgStatus::finish would normally go here if it succeeded. Any ideas please? Joe
Re: Mail::SpamAssassin::PerMsgStatus::finish failing after upgrade from 3.1.7 to 3.2.0
hi Joe -- yep, it is. In fact you should probably use the G_ flag for calling a method in void context, can't recall which one that is ;) --j. Joe Flowers writes: Thanks Justin. I am embedding Perl inside a C program, so I hope this is still true. It used to return a non-NULL or at least the following call used to always return a count of 1 and not 0 like it is now after the SA upgrade. count = perl_call_method(Mail::SpamAssassin::PerMsgStatus::finish, (G_ARRAY|G_EVAL|G_KEEPERR)); Is your answer still the same? Thanks a lot! Joe Justin Mason wrote: hi Joe -- just ignore the return value of finish() -- it's a void method. (note how it doesn't mention a return value in its POD doc ;) --j. Joe Flowers writes: Hello Everyone, I'm getting a weird error message that I have never gotten before over several versions of SA. I just upgraded from SpamAssassin version 3.1.7 running on Perl version 5.8.8 to SpamAssassin version 3.2.0 running on Perl version 5.8.8. Now, my calls to Mail::SpamAssassin::PerMsgStatus::finish are failing; or at least, it looks like their has been some change in the return values by finish(). I have been running this programming over many iterations of SA and this is the first time I have run into such a problem. This worries me a lot because from the docs (http://spamassassin.apache.org/full/3.2.x/doc/Mail_SpamAssassin_PerMsgStatus.html): $status-finish () If you are using SpamAssassin in a persistent environment, or checking many mail messages from one Mail::SpamAssassin factory, this method should be called to ensure Perl's garbage collection will clean up old status objects. . These calls succeed as usual: Mail::SpamAssassin::PerMsgStatus::get_required_score Mail::SpamAssassin::PerMsgStatus::get_score Mail::SpamAssassin::PerMsgStatus::is_spam Mail::SpamAssassin::PerMsgStatus::get_names_of_tests_hit Mail::SpamAssassin::PerMsgStatus::finish would normally go here if it succeeded. Any ideas please? Joe
Mail::SpamAssassin::PerMsgStatus::finish failing after upgrade from 3.1.7 to 3.2.0
Hello Everyone, I'm getting a weird error message that I have never gotten before over several versions of SA. I just upgraded from SpamAssassin version 3.1.7 running on Perl version 5.8.8 to SpamAssassin version 3.2.0 running on Perl version 5.8.8. Now, my calls to Mail::SpamAssassin::PerMsgStatus::finish are failing; or at least, it looks like their has been some change in the return values by finish(). I have been running this programming over many iterations of SA and this is the first time I have run into such a problem. This worries me a lot because from the docs (http://spamassassin.apache.org/full/3.2.x/doc/Mail_SpamAssassin_PerMsgStatus.html): $status-finish () If you are using SpamAssassin in a persistent environment, or checking many mail messages from one Mail::SpamAssassin factory, this method should be called to ensure Perl's garbage collection will clean up old status objects. . These calls succeed as usual: Mail::SpamAssassin::PerMsgStatus::get_required_score Mail::SpamAssassin::PerMsgStatus::get_score Mail::SpamAssassin::PerMsgStatus::is_spam Mail::SpamAssassin::PerMsgStatus::get_names_of_tests_hit Mail::SpamAssassin::PerMsgStatus::finish would normally go here if it succeeded. Any ideas please? Joe
Warnings after upgrade
Hi. Gentoo Spamassassin 3.1.8-r1 After upgrading from 3.1.3 to 3.1.8-r1 I found many warnings in logs (see attachment) which fill up all space on my /var/log partition. This warings is equal to warnings from spamd -D. Also I attach versions of my perl modules. May be it will be usefull. Any ideas? Regards, Andreev Nikita.May 21 09:23:22 mail spamd[4214]: plugin: failed to parse plugin (from @INC): Bareword Mail::SpamAssassin::Constants::CHARSETS_LIKELY_TO_FP_AS_CAPS not all owed while strict subs in use at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Plugin/HeaderEval.pm line 965. May 21 09:23:22 mail spamd[4214]: Compilation failed in require at (eval 55) line 1. May 21 09:23:22 mail spamd[4214]: plugin: failed to create instance of plugin Mail::SpamAssassin::Plugin::HeaderEval: Can't locate object method new via pa ckage Mail::SpamAssassin::Plugin::HeaderEval at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Plugin/HeaderEval.pm line 39. May 21 09:23:22 mail spamd[4214]: plugin: failed to parse plugin (from @INC): CHARSETS_LIKELY_TO_FP_AS_CAPS is not exported by the Mail::SpamAssassin::Cons tants module May 21 09:23:22 mail spamd[4214]: Can't continue after import errors at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Plugin/MIMEEval.pm line 22 May 21 09:23:22 mail spamd[4214]: BEGIN failed--compilation aborted at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Plugin/MIMEEval.pm line 22. May 21 09:23:22 mail spamd[4214]: Compilation failed in require at (eval 57) line 1. May 21 09:23:22 mail spamd[4214]: plugin: failed to create instance of plugin Mail::SpamAssassin::Plugin::MIMEEval: Can't locate object method new via pack age Mail::SpamAssassin::Plugin::MIMEEval at (eval 58) line 1. May 21 09:23:23 mail spamd[4214]: Use of uninitialized value in concatenation (.) or string at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatu s.pm line 2669. May 21 09:23:23 mail spamd[4214]: Use of uninitialized value in concatenation (.) or string at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatu s.pm line 2669. May 21 09:23:23 mail spamd[4214]: Use of uninitialized value in concatenation (.) or string at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatu s.pm line 2669. May 21 09:23:23 mail spamd[4214]: Number found where operator expected at (eval 230) line 10, near } May 21 09:23:23 mail spamd[4214]: May 21 09:23:23 mail spamd[4214]: 1 May 21 09:23:23 mail spamd[4214]: (Missing operator before May 21 09:23:23 mail spamd[4214]: May 21 09:23:23 mail spamd[4214]: 1?) May 21 09:23:23 mail spamd[4214]: rules: failed to run header tests, skipping some: syntax error at (eval 230) line 11, near ; May 21 09:23:23 mail spamd[4214]: } May 21 09:23:23 mail spamd[4214]: Use of uninitialized value in concatenation (.) or string at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatu s.pm line 2669. May 21 09:23:23 mail spamd[4214]: Use of uninitialized value in concatenation (.) or string at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatu s.pm line 2669. May 21 09:23:23 mail spamd[4214]: Use of uninitialized value in concatenation (.) or string at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatu s.pm line 2669. May 21 09:23:23 mail spamd[4214]: Number found where operator expected at (eval 231) line 10, near } May 21 09:23:23 mail spamd[4214]: May 21 09:23:23 mail spamd[4214]: 1 May 21 09:23:23 mail spamd[4214]: (Missing operator before May 21 09:23:23 mail spamd[4214]: May 21 09:23:23 mail spamd[4214]: 1?) May 21 09:23:23 mail spamd[4214]: rules: failed to run header tests, skipping some: syntax error at (eval 231) line 11, near ; May 21 09:23:23 mail spamd[4214]: } (last error repeats many times)Package namespace installedlatest in CPAN file Archive::Tar 1.28 1.31 KANE/Archive-Tar-1.31.tar.gz Compress::Zlib 1.41 2.004 PMQS/Compress-Zlib-2.004.tar.gz Crypt::SSLeay 0.49 0.54 DLAND/Crypt-SSLeay-0.54.tar.gz DBD::ExampleP 11.12 12.009532 TIMB/DBI-1.56.tar.gz DBD::mysql 2.9007 4.004 CAPTTOFU/DBD-mysql-4.004.tar.gz DB_File 1.814 1.815 PMQS/DB_File-1.815.tar.gz Digest 1.13 1.15 GAAS/Digest-1.15.tar.gz Digest::MD52.33 2.36 GAAS/Digest-MD5-2.36.tar.gz ExtUtils::Command 1.07 1.13 RKOBES/ExtUtils-Command-1.13.tar.gz ExtUtils::Command::MM 0.03 0.07 MSCHWERN/ExtUtils-MakeMaker-6.32.tar.gz ExtUtils::Install 1.32 1.41 YVES/ExtUtils-Install-1.41.tar.gz ExtUtils::Manifest 1.43 1.51 RKOBES/ExtUtils-Manifest-1.51.tar.gz HTML::Entities 1.32 1.35 GAAS/HTML-Parser-3.56.tar.gz HTML::Form1.039 1.054 GAAS/libwww-perl-5.805.tar.gz HTML::Tagset 3.03 3.10 PETDANCE/HTML-Tagset-3.10.tar.gz
new warning in sa-learn after upgrade
Just upgraded to 3.1.8. Everything seems fine except that I get this line when running sa-learn: archive-iterator: invalid (undef) format in target list, 2 at /usr/lib/perl5/site_perl/5.8.0/Mail/SpamAssassin/ArchiveIterator.pm line 727, STDIN line 1. sa-learn seems to be working fine though. Just for the record, the sa-learn has messages (one eache time) fed thru stdin from a cyrus imapd folder. -Raul Dias
Re: new warning in sa-learn after upgrade
On Thu, Feb 15, 2007 at 02:15:47PM -0300, Raul Dias wrote: archive-iterator: invalid (undef) format in target list, 2 at /usr/lib/perl5/site_perl/5.8.0/Mail/SpamAssassin/ArchiveIterator.pm line 727, STDIN line 1. Just for the record, the sa-learn has messages (one eache time) fed thru stdin from a cyrus imapd folder. We'd have to see your sa-learn commandline. If you want to learn a folder of messages though, you should just aim sa-learn at the folder. -- Randomly Selected Tagline: Only wimps use tape backup: _real_ men just upload their important stuff on ftp, and let the rest of the world mirror it ;) - Linus Torvalds pgpGW51QztAzf.pgp Description: PGP signature
Re: new warning in sa-learn after upgrade
On Thu, 2007-02-15 at 12:45 -0500, Theo Van Dinter wrote:
On Thu, Feb 15, 2007 at 02:15:47PM -0300, Raul Dias wrote:
archive-iterator: invalid (undef) format in target list, 2
at /usr/lib/perl5/site_perl/5.8.0/Mail/SpamAssassin/ArchiveIterator.pm
line 727, STDIN line 1.
Just for the record, the sa-learn has messages (one eache time) fed thru
stdin from a cyrus imapd folder.
We'd have to see your sa-learn commandline. If you want to learn a folder of
messages though, you should just aim sa-learn at the folder.
actually I run this from a script:
open (LEARN, | /usr/bin/sa-learn -u $user -- . $OPTIONS-{type})
which reflects for: /usr/bin/sa-learn -u raul --spam for example.
-Raul Dias
Re: new warning in sa-learn after upgrade
On Thu, Feb 15, 2007 at 03:53:29PM -0300, Raul Dias wrote:
open (LEARN, | /usr/bin/sa-learn -u $user -- . $OPTIONS-{type})
which reflects for: /usr/bin/sa-learn -u raul --spam for example.
Hey look at that, piping in has the issue if no target is specified.
For the moment, add in - as a target and that seems to solve it,
for an as yet unknown reason.
Please open a bugzilla ticket about it. The patch is pretty simple. :)
--
Randomly Selected Tagline:
Exactly what it should've been, give people what they expect. The third
one can be clever. - John Hughes about Home Alone 2
pgpH4WzeF9s94.pgp
Description: PGP signature
Re: how to solve errors after upgrade
Leon, 451 4.5.0 Error in processing, id=15039-05, mime_decode-1 FAILED: Can't locate object method max_parts via package MIME::Parser at /usr/sbin/amavisd line 5933. Your version of MIME::Parser (i.e. MIME-Tools) is too old, use 5.420. Mark
how to solve errors after upgrade
Hello All, I'm running SLES9 with the following versions: spamassassin-2.64-3.2 perl-spamassassin-2.64-3.2 amavisd-new-20030616p9-3.6 I know I probably stuck with perl5.8.3 because SLES9 don't have the newer :( I've installed new versions of SA and amavis (see below) with the following packets (compiled from src.rpm's): # rpm -Uvh amavisd-new-2.4.4-4.i586.rpm perl-BerkeleyDB-0.25-2.i586.rpm perl-Compress-Zlib-1.35-12.i586.rpm perl-Convert-UUlib-1.051-11.i586.rpm # rpm -Uvh perl-spamassassin-3.1.7-3.i586.rpm spamassassin-3.1.7-3.i586.rpm Restarted SA and amavis, and started to get the following errors while there was no email-coming through my system and mailque growing! Example of maillog errors: Nov 22 14:25:39 mail postfix/smtp[15132]: 23CBE1CA24: to= [EMAIL PROTECTED] , orig_to= [EMAIL PROTECTED], relay=127.0.0.1[127.0.0.1], delay=25, status=deferred (host 127.0.0.1[127.0.0.1] said: 451 4.5.0 Error in processing, id=15039-05, mime_decode-1 FAILED: Can't locate object method max_parts via package MIME::Parser at /usr/sbin/amavisd line 5933. (in reply to end of DATA command)) Nov 22 14:28:14 mail postfix/smtp[15215]: AC330192F3: to=[EMAIL PROTECTED], orig_to=[EMAIL PROTECTED], relay=127.0.0.1[127.0.0.1], delay=0, status=deferred (host 127.0.0.1[127.0.0.1] said: 451 4.5.0 Error in processing, id=15038-09, mime_decode-1 FAILED: Can't locate object method max_parts via package MIME::Parser at /usr/sbin/amavisd line 5933. (in reply to end of DATA command)) So, meanwhile I got the old SA and amavis back, but I wish I could use the newest versions. What may be causing these errors and how to solve this? Best Regards, Leon Kolchinsky
Re: [OT really Amavis Q] how to solve errors after upgrade
You should upgrade your MIME::Parser as well. You are probably using a very old one, where it does not support of max_parts as stated in the error log! /Micke Leon Kolchinsky wrote: Example of maillog errors: Nov 22 14:25:39 mail postfix/smtp[15132]: 23CBE1CA24: to= [EMAIL PROTECTED] , orig_to= [EMAIL PROTECTED], relay=127.0.0.1[127.0.0.1], delay=25, status=deferred (host 127.0.0.1[127.0.0.1] said: 451 4.5.0 Error in processing, id=15039-05, mime_decode-1 FAILED: Can't locate object method max_parts via package MIME::Parser at /usr/sbin/amavisd line 5933. (in reply to end of DATA command)) Nov 22 14:28:14 mail postfix/smtp[15215]: AC330192F3: to=[EMAIL PROTECTED], orig_to=[EMAIL PROTECTED], relay=127.0.0.1[127.0.0.1], delay=0, status=deferred (host 127.0.0.1[127.0.0.1] said: 451 4.5.0 Error in processing, id=15038-09, mime_decode-1 FAILED: Can't locate object method max_parts via package MIME::Parser at /usr/sbin/amavisd line 5933. (in reply to end of DATA command)) So, meanwhile I got the old SA and amavis back, but I wish I could use the newest versions. What may be causing these errors and how to solve this? Best Regards, Leon Kolchinsky
Re: how to solve errors after upgrade
On Wed, Nov 22, 2006 at 05:33:39PM +0200, Leon Kolchinsky wrote: Nov 22 14:25:39 mail postfix/smtp[15132]: 23CBE1CA24: to= [EMAIL PROTECTED] , orig_to= [EMAIL PROTECTED], relay=127.0.0.1[127.0.0.1], delay=25, status=deferred (host 127.0.0.1[127.0.0.1] said: 451 4.5.0 Error in processing, id=15039-05, mime_decode-1 FAILED: Can't locate object method max_parts via package MIME::Parser at /usr/sbin/amavisd line 5933. (in reply to end of DATA command)) What may be causing these errors and how to solve this? You'll want to talk to the amavis folks, since those errors aren't coming from SA. -- Randomly Selected Tagline: There is hopeful symbolism in the fact that flags do not wave in a vacuum. - Arthur C. Clarke pgpfsuCkSoJk6.pgp Description: PGP signature
extra line-break after upgrade
i just upgraded spamassassin 3.1.0 to 3.1.7 ( Rh9 ) and seem to be getting an extra line-break in the Content-Type header. outlook apparently sees the semi-colon as a LF and doesn't render the email correctly. evolution sees it as a semi colon and every- thing works fine. always in the Content-Type line, and always on or after the semi-colon. any ideas? thx. MM Content-Type: text/plain; charset=windows-1250 line feed carriage return line break
Re: extra line-break after upgrade
Mark Merchant wrote: i just upgraded spamassassin 3.1.0 to 3.1.7 ( Rh9 ) and seem to be getting an extra line-break in the Content-Type header. outlook apparently sees the semi-colon as a LF and doesn't render the email correctly. evolution sees it as a semi colon and every- thing works fine. always in the Content-Type line, and always on or after the semi-colon. any ideas? Are you using spamass-milter? If so, upgrade it. Daryl
errors after upgrade to 3.1.7, now it doesn't work
I had a working setup of Courier-MTA, spamassassin 3.0.4, and maildrop, but I upgraded spamassassin to 3.1.7 and now I have errors and mail doesn't get delivered unless I remove the tie-in to spamassassin in the courierd file. Here are some of the errors: Oct 20 14:10:20 mail spamd[5776]: configuration file /usr/share/spamassassin/20_net_tests.cf requires version 3.001007 of SpamAssassin, but this is code ve rsion 3.04. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/vendor_perl/5.8.6/Mail/SpamAssassin /Conf/Parser.pm line 332. Oct 20 14:10:20 mail spamd[5776]: configuration file /usr/share/spamassassin/20_phrases.cf requires version 3.001007 of SpamAssassin, but this is code vers ion 3.04. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/vendor_perl/5.8.6/Mail/SpamAssassin/C onf/Parser.pm line 332. Oct 20 14:10:21 mail spamd[5776]: configuration file /usr/share/spamassassin/20_porn.cf requires version 3.001007 of SpamAssassin, but this is code version 3.04. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/vendor_perl/5.8.6/Mail/SpamAssassin/Conf /Parser.pm line 332. Oct 20 14:10:21 mail spamd[5776]: configuration file /usr/share/spamassassin/20_uri_tests.cf requires version 3.001007 of SpamAssassin, but this is code ve rsion 3.04. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/vendor_perl/5.8.6/Mail/SpamAssassin /Conf/Parser.pm line 332. Oct 20 14:10:21 mail spamd[5776]: configuration file /usr/share/spamassassin/23_bayes.cf requires version 3.001007 of SpamAssassin, but this is code versio n 3.04. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/vendor_perl/5.8.6/Mail/SpamAssassin/Con f/Parser.pm line 332. Oct 20 14:10:22 mail spamd[5776]: Failed to run __ENV_AND_HDR_FROM_MATCH SpamAssassin test, skipping:__(Can't locate object method check_for_matching_env_an d_hdr_from via package Mail::SpamAssassin::PerMsgStatus at /usr/lib/perl5/vendor_perl/5.8.6/Mail/SpamAssassin/PerMsgStatus.pm line 2340._) Oct 20 14:10:22 mail spamd[5776]: Failed to run USER_IN_DEF_SPF_WL SpamAssassin test, skipping:__(Can't locate object method check_for_def_spf_whitelist_fro m via package Mail::SpamAssassin::PerMsgStatus at /usr/lib/perl5/vendor_perl/5.8.6/Mail/SpamAssassin/PerMsgStatus.pm line 2340._) Oct 20 14:10:22 mail spamd[5776]: Failed to run RATWARE_EFROM SpamAssassin test, skipping:__(Can't locate object method check_ratware_envelope_from via pac kage Mail::SpamAssassin::PerMsgStatus at /usr/lib/perl5/vendor_perl/5.8.6/Mail/SpamAssassin/PerMsgStatus.pm line 2340._) Oct 20 14:10:22 mail spamd[5776]: Failed to run __RATWARE_NAME_ID SpamAssassin test, skipping:__(Can't locate object method check_ratware_name_id via packa ge Mail::SpamAssassin::PerMsgStatus at /usr/lib/perl5/vendor_perl/5.8.6/Mail/SpamAssassin/PerMsgStatus.pm line 2340._) Oct 20 14:10:22 mail spamd[5776]: Failed to run SPF_NEUTRAL SpamAssassin test, skipping:__(Can't locate object method check_for_spf_neutral via package Ma il::SpamAssassin::PerMsgStatus at /usr/lib/perl5/vendor_perl/5.8.6/Mail/SpamAssassin/PerMsgStatus.pm line 2340._) Oct 20 14:10:22 mail spamd[5776]: Failed to run USER_IN_SPF_WHITELIST SpamAssassin test, skipping:__(Can't locate object method check_for_spf_whitelist_from via package Mail::SpamAssassin::PerMsgStatus at /usr/lib/perl5/vendor_perl/5.8.6/Mail/SpamAssassin/PerMsgStatus.pm line 2340._) Reading the top errors indicates that I haven't removed something from the old version, but without knowing for sure what I should remove, I am hesitant to do so. The bottom errors indicate something didn't get installed or configured correctly. Please advise. Thanks, Brian -- All people who think everything is either black or white are idiots.
Re: errors after upgrade to 3.1.7, now it doesn't work
On Fri, Oct 20, 2006 at 02:30:14PM -0400, Brian S. Meehan wrote: Oct 20 14:10:20 mail spamd[5776]: configuration file /usr/share/spamassassin/20_net_tests.cf requires version 3.001007 of SpamAssassin, but this is code ve rsion 3.04. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/vendor_perl/5.8.6/Mail/SpamAssassin /Conf/Parser.pm line 332. You have the 3.1.7 rules installed, but are using the perl modules from 3.0.4. Oct 20 14:10:22 mail spamd[5776]: Failed to run __ENV_AND_HDR_FROM_MATCH SpamAssassin test, skipping:__(Can't locate object method check_for_matching_env_an d_hdr_from via package Mail::SpamAssassin::PerMsgStatus at /usr/lib/perl5/vendor_perl/5.8.6/Mail/SpamAssassin/PerMsgStatus.pm line 2340._) You're going to be missing a bunch of functions. Reading the top errors indicates that I haven't removed something from the old version, but without knowing for sure what I should remove, I am hesitant to do so. The bottom errors indicate something didn't get installed or configured correctly. Please advise. It appears that your upgrade didn't complete. I would go and blow away the perl modules, scripts, and default rules, then install 3.1.7, then go from there. -- Randomly Selected Tagline: What is the difference between a Democrat and a Republican? A Democrat blows, a Republican sucks. - Lewis Black, Comedy Central Presents pgpUA1IYtJT0B.pgp Description: PGP signature
Re: errors after upgrade to 3.1.7, now it doesn't work
On Fri, Oct 20, 2006 at 02:42:09PM -0400, Brian S. Meehan wrote: When you say blow them away, are there folders besides the below ones that should be removed? /etc/mail/spamassassin I'd save these files, since they're your local configs. Copy them back appropriately after the install. /usr/share/spamassassin Yeah. Also get rid of: /var/lib/spamassassin then find the perl modules and remove those (SpamAssassin.pm and everything in the SpamAssassin directory). then find the SA-related progs and remove those (spamassassin, sa-update, sa-learn, spamc, spamd, etc). Then do the install, fix up /etc/mail/spamassassin as necessary. -- Randomly Selected Tagline: Ignore me. You'd freak out if you understood what I'm doing. pgpfqnfapFkWM.pgp Description: PGP signature
RE: use of ram after upgrade
From: Balzi Andrea snippers I've try it, but now I've the follow use: Tasks: 83 total, 2 running, 81 sleeping, 0 stopped, 0 zombie Cpu0 : 0.0% user, 1.3% system, 1.7% nice, 97.0% idle Cpu1 : 0.0% user, 1.3% system, 0.0% nice, 98.7% idle Cpu2 : 0.0% user, 0.0% system, 1.3% nice, 98.7% idle Cpu3 : 0.0% user, 0.0% system, 98.7% nice, 1.3% idle Mem: 6206432k total, 909444k used, 5296988k free, 117224k buffers Swap: 284k total, 7856k used, 1992228k free,70724k cached PID PPID PR NI S #C RES SHR SWAP TIME COMMAND 15404 15386 15 10 S 1 354m 33m0 5:29 spamd child 15405 15386 19 10 R 2 176m 34m0 4:33 spamd child 15626 15386 14 10 S 0 88m 36m0 0:22 spamd child 15645 15386 15 10 S 3 85m 36m0 0:07 spamd child 15386 1 15 10 S 2 73m 36m0 0:03 /usr/sbin/spamd My engineers and I have determined that since this is a 4 way processor box (hopefully with a lot of RAM and processor speed), that you should box it up and send it to us for extended testing... ...probably only a year or two and we will fix it and get it right back you you... if you cannot send this one, another 4 proc or 8 proc box will do. ;- Thanks and kind regards! - rh -- Robert - Abba Communications Computer Internet Services (509) 624-7159 - www.abbacomm.net
