Re: Sa-update failed
On Fri, Dec 15, 2017 at 04:26:45AM -0700, @lbutlr wrote: > FreeBSD system on 11.2-RELEASE with all packages updates as of this morning > (including a complete recompile of SA from ports). FreeBSD 11.1-RELEASE! You probably upgraded from 10.x and executed 'make delete-old-libs'!? Did you install packages for 10.x? Wrong pkg url? You have to rebuild gpg. > # sa-update --refreshmirrors -v -D > […] > Shared object "libreadline.so.8" not found, required by "gpg" > gpg: process '/usr/local/bin/gpg' finished: exit 1 > error: GPG validation failed! > The update downloaded successfully, but the GPG signature verification > failed. > > I can manually link libreadline.so to libreadline.so.8, and run > sa-update successfully, but I’m concerned that is going to come back > and bite me. Temporarily install misc/compat10x and rebuild all ports. This is not a SA issue and should be discussed on a FreeBSD mailing list. -- Herbert
Re: Bayer Filter Not Working
On Thu, 03 Jul 2014 12:05:34 +0200 Herbert J. Skuhra wrote: Den 01.07.2014 23:05, skrev Herbert J. Skuhra: On Tue, 01 Jul 2014 09:37:17 +0200 Herbert J. Skuhra wrote: Den 25.06.2014 00:42, skrev Bruce Sackett: I apologize, I’m sure it’s been covered, but I have not been successful finding results in searches on the web or through the history of the list. I get no BAYES results in the headers, so I don’t see any working. The part that gets me is below: Jun 24 13:47:53.165 [3245] dbg: bayes: tie-ing to DB file R/O /var/lib/amavis/.spamassassin/bayes_toks Jun 24 13:47:53.166 [3245] dbg: bayes: tie-ing to DB file R/O /var/lib/amavis/.spamassassin/bayes_seen Jun 24 13:47:53.167 [3245] dbg: bayes: found bayes db version 3 Jun 24 13:47:53.167 [3245] warn: plugin: eval failed: Insecure dependency in sprintf while running with -T switch at /usr/local/share/perl/5.14.2/Mail/SpamAssassin/Logger.pm line 241. Jun 24 13:47:53.168 [3245] dbg: config: score set 0 chosen. That seems to be the last time Bayes is referenced in a spamassassin -D ―lint Has anyone else run into this? I am using an Ubuntu 12.04 server, if that makes any difference. I have the same problem on FreeBSD: Jul 1 05:33:51.765 [43144] dbg: bayes: learner_new self=Mail::SpamAssassin::Plugin::Bayes=HASH(0x805b09f78), bayes_store_module=Mail::SpamAssassin::BayesStore::DBM Jul 1 05:33:51.778 [43144] dbg: bayes: learner_new: got store=Mail::SpamAssassin::BayesStore::DBM=HASH(0x806108798) Jul 1 05:33:51.779 [43144] dbg: bayes: tie-ing to DB file R/O /var/amavis/.spamassassin/bayes_toks Jul 1 05:33:51.779 [43144] dbg: bayes: tie-ing to DB file R/O /var/amavis/.spamassassin/bayes_seen Jul 1 05:33:51.779 [43144] dbg: bayes: found bayes db version 3 Jul 1 05:33:51.779 [43144] warn: plugin: eval failed: Insecure dependency in sprintf while running with -T switch at /usr/local/lib/perl5/site_perl/5.16/Mail/SpamAssassin/Logger.pm line 241. Jul 1 05:33:51.799 [43144] warn: plugin: eval failed: Insecure dependency in sprintf while running with -T switch at /usr/local/lib/perl5/site_perl/5.16/Mail/SpamAssassin/Logger.pm line 241. Running 'sa-learn --force-expire' seems to resolve the issue temporally. Jul 1 09:35:06.084 [49647] dbg: bayes: learner_new self=Mail::SpamAssassin::Plugin::Bayes=HASH(0x805b09f78), bayes_store_module=Mail::SpamAssassin::BayesStore::DBM Jul 1 09:35:06.097 [49647] dbg: bayes: learner_new: got store=Mail::SpamAssassin::BayesStore::DBM=HASH(0x806108798) Jul 1 09:35:06.098 [49647] dbg: bayes: tie-ing to DB file R/O /var/amavis/.spamassassin/bayes_toks Jul 1 09:35:06.098 [49647] dbg: bayes: tie-ing to DB file R/O /var/amavis/.spamassassin/bayes_seen Jul 1 09:35:06.098 [49647] dbg: bayes: found bayes db version 3 Jul 1 09:35:06.099 [49647] dbg: bayes: DB journal sync: last sync: 0 Jul 1 09:35:06.570 [49647] dbg: bayes: DB journal sync: last sync: 0 Jul 1 09:35:06.570 [49647] dbg: bayes: corpus size: nspam = 120857, nham = 664988 After a while the error returns. Do I have to wipe my bayes DB? I wiped my bayes DB and learned more than 200 spam and ham messages each. While nham and nspam were below 200 message error was gone. But now it is back. % spamassassin -t OvwTlDIfJxAe [...] 3.5 BAYES_99 BODY: Bayes spam probability is 99 to 100% [score: 1.] [...] 0.2 BAYES_999 BODY: Bayes spam probability is 99.9 to 100% [score: 1.] [...] Running the same command with the -D switch the error appears and I don't see the BAYES score. There is also no BAYES score in the amavisd log. :-( I could resolve this issue by setting $sa_debug from 1- 0 in amavisd.conf. This is abviously a workaround and not a proper fix. So, I can only reproduce this issue on FreeBSD (and not on Fedora 20, Arch Linux) because only FreeBSD runs spamassassin in taint mode. Is this a bug in Logger.pm? Or simply switch off taint mode? Any comments? -- Herbert
Re: Bayer Filter Not Working
On Sat, 05 Jul 2014 16:02:29 +0200 Mark Martinec wrote: On 2014-07-05 14:18, Herbert J. Skuhra wrote: Jun 24 13:47:53.167 [3245] warn: plugin: eval failed: Insecure dependency in sprintf while running with -T switch at /usr/local/share/perl/5.14.2/Mail/SpamAssassin/Logger.pm line 241. Jun 24 13:47:53.168 [3245] dbg: config: score set 0 chosen. That seems to be the last time Bayes is referenced in a spamassassin -D ―lint So, I can only reproduce this issue on FreeBSD (and not on Fedora 20, Arch Linux) because only FreeBSD runs spamassassin in taint mode. Is this a bug in Logger.pm? Or simply switch off taint mode? Any comments? The bug is not in the logger, but is a routine that calls it. Which Bayes database backend are you using? The bug must be specific to that one. I was using DBM and I cannot reproduce this issue with BDB and SDBM. I could resolve this issue by setting $sa_debug from 1- 0 in amavisd.conf. This is abviously a workaround and not a proper fix. For the time being please stick to that workaround until the problem is investigated. Or simply switch off taint mode? Please don't, that would not be a right thing to do. Looks like the kind of a thing appropriate to open a problem report in the SpamAssassin's bugzilla. I can do later. Someone else already reported this issue on this list back in February (Subject: -D turns off Bayes in in 3.4.0?). Thanks. -- Herbert
Re: Bayer Filter Not Working
On Sat, 5 Jul 2014 09:11:13 -0700 (PDT)
John Hardin wrote:
This appears to be a bit of odd coding in the Bayes DBM module. It's
passing a message to logger with unused arguments.
I haven't done a deep analysis, but you might try this patch:
Index: lib/Mail/SpamAssassin/BayesStore/DBM.pm
===
--- lib/Mail/SpamAssassin/BayesStore/DBM.pm (revision 1607964)
+++ lib/Mail/SpamAssassin/BayesStore/DBM.pm (working copy)
@@ -812,7 +812,7 @@
return 0 if ($conf-{bayes_journal_max_size} == 0);
my @vars = $self-get_storage_variables();
- dbg(bayes: DB journal sync: last sync: .$vars[7],'bayes','-1');
+ dbg(bayes: DB journal sync: last sync: .$vars[7]);
## Ok, should we do a sync?
Of course, this might just relocate where in logger the taint error
occurs.
The ultimate cause might be the stringpaste of $vars[7], which has
been retrieved unchanged from the Bayes database and thus might be
considered tainted (assuming it's treated as a string and not as a
number).
With this patch the error is gone.
Thanks.
--
Herbert
Re: Bayer Filter Not Working
Den 01.07.2014 23:05, skrev Herbert J. Skuhra: On Tue, 01 Jul 2014 09:37:17 +0200 Herbert J. Skuhra wrote: Den 25.06.2014 00:42, skrev Bruce Sackett: I apologize, I’m sure it’s been covered, but I have not been successful finding results in searches on the web or through the history of the list. I get no BAYES results in the headers, so I don’t see any working. The part that gets me is below: Jun 24 13:47:53.165 [3245] dbg: bayes: tie-ing to DB file R/O /var/lib/amavis/.spamassassin/bayes_toks Jun 24 13:47:53.166 [3245] dbg: bayes: tie-ing to DB file R/O /var/lib/amavis/.spamassassin/bayes_seen Jun 24 13:47:53.167 [3245] dbg: bayes: found bayes db version 3 Jun 24 13:47:53.167 [3245] warn: plugin: eval failed: Insecure dependency in sprintf while running with -T switch at /usr/local/share/perl/5.14.2/Mail/SpamAssassin/Logger.pm line 241. Jun 24 13:47:53.168 [3245] dbg: config: score set 0 chosen. That seems to be the last time Bayes is referenced in a spamassassin -D ―lint Has anyone else run into this? I am using an Ubuntu 12.04 server, if that makes any difference. I have the same problem on FreeBSD: Jul 1 05:33:51.765 [43144] dbg: bayes: learner_new self=Mail::SpamAssassin::Plugin::Bayes=HASH(0x805b09f78), bayes_store_module=Mail::SpamAssassin::BayesStore::DBM Jul 1 05:33:51.778 [43144] dbg: bayes: learner_new: got store=Mail::SpamAssassin::BayesStore::DBM=HASH(0x806108798) Jul 1 05:33:51.779 [43144] dbg: bayes: tie-ing to DB file R/O /var/amavis/.spamassassin/bayes_toks Jul 1 05:33:51.779 [43144] dbg: bayes: tie-ing to DB file R/O /var/amavis/.spamassassin/bayes_seen Jul 1 05:33:51.779 [43144] dbg: bayes: found bayes db version 3 Jul 1 05:33:51.779 [43144] warn: plugin: eval failed: Insecure dependency in sprintf while running with -T switch at /usr/local/lib/perl5/site_perl/5.16/Mail/SpamAssassin/Logger.pm line 241. Jul 1 05:33:51.799 [43144] warn: plugin: eval failed: Insecure dependency in sprintf while running with -T switch at /usr/local/lib/perl5/site_perl/5.16/Mail/SpamAssassin/Logger.pm line 241. Running 'sa-learn --force-expire' seems to resolve the issue temporally. Jul 1 09:35:06.084 [49647] dbg: bayes: learner_new self=Mail::SpamAssassin::Plugin::Bayes=HASH(0x805b09f78), bayes_store_module=Mail::SpamAssassin::BayesStore::DBM Jul 1 09:35:06.097 [49647] dbg: bayes: learner_new: got store=Mail::SpamAssassin::BayesStore::DBM=HASH(0x806108798) Jul 1 09:35:06.098 [49647] dbg: bayes: tie-ing to DB file R/O /var/amavis/.spamassassin/bayes_toks Jul 1 09:35:06.098 [49647] dbg: bayes: tie-ing to DB file R/O /var/amavis/.spamassassin/bayes_seen Jul 1 09:35:06.098 [49647] dbg: bayes: found bayes db version 3 Jul 1 09:35:06.099 [49647] dbg: bayes: DB journal sync: last sync: 0 Jul 1 09:35:06.570 [49647] dbg: bayes: DB journal sync: last sync: 0 Jul 1 09:35:06.570 [49647] dbg: bayes: corpus size: nspam = 120857, nham = 664988 After a while the error returns. Do I have to wipe my bayes DB? I wiped my bayes DB and learned more than 200 spam and ham messages each. While nham and nspam were below 200 message error was gone. But now it is back. % spamassassin -t OvwTlDIfJxAe [...] 3.5 BAYES_99 BODY: Bayes spam probability is 99 to 100% [score: 1.] [...] 0.2 BAYES_999 BODY: Bayes spam probability is 99.9 to 100% [score: 1.] [...] Running the same command with the -D switch the error appears and I don't see the BAYES score. There is also no BAYES score in the amavisd log. :-( I could resolve this issue by setting $sa_debug from 1- 0 in amavisd.conf. This is abviously a workaround and not a proper fix. -- Herbert
Re: Bayer Filter Not Working
Den 25.06.2014 00:42, skrev Bruce Sackett: I apologize, I’m sure it’s been covered, but I have not been successful finding results in searches on the web or through the history of the list. I get no BAYES results in the headers, so I don’t see any working. The part that gets me is below: Jun 24 13:47:53.165 [3245] dbg: bayes: tie-ing to DB file R/O /var/lib/amavis/.spamassassin/bayes_toks Jun 24 13:47:53.166 [3245] dbg: bayes: tie-ing to DB file R/O /var/lib/amavis/.spamassassin/bayes_seen Jun 24 13:47:53.167 [3245] dbg: bayes: found bayes db version 3 Jun 24 13:47:53.167 [3245] warn: plugin: eval failed: Insecure dependency in sprintf while running with -T switch at /usr/local/share/perl/5.14.2/Mail/SpamAssassin/Logger.pm line 241. Jun 24 13:47:53.168 [3245] dbg: config: score set 0 chosen. That seems to be the last time Bayes is referenced in a spamassassin -D —lint Has anyone else run into this? I am using an Ubuntu 12.04 server, if that makes any difference. I have the same problem on FreeBSD: Jul 1 05:33:51.765 [43144] dbg: bayes: learner_new self=Mail::SpamAssassin::Plugin::Bayes=HASH(0x805b09f78), bayes_store_module=Mail::SpamAssassin::BayesStore::DBM Jul 1 05:33:51.778 [43144] dbg: bayes: learner_new: got store=Mail::SpamAssassin::BayesStore::DBM=HASH(0x806108798) Jul 1 05:33:51.779 [43144] dbg: bayes: tie-ing to DB file R/O /var/amavis/.spamassassin/bayes_toks Jul 1 05:33:51.779 [43144] dbg: bayes: tie-ing to DB file R/O /var/amavis/.spamassassin/bayes_seen Jul 1 05:33:51.779 [43144] dbg: bayes: found bayes db version 3 Jul 1 05:33:51.779 [43144] warn: plugin: eval failed: Insecure dependency in sprintf while running with -T switch at /usr/local/lib/perl5/site_perl/5.16/Mail/SpamAssassin/Logger.pm line 241. Jul 1 05:33:51.799 [43144] warn: plugin: eval failed: Insecure dependency in sprintf while running with -T switch at /usr/local/lib/perl5/site_perl/5.16/Mail/SpamAssassin/Logger.pm line 241. Running 'sa-learn --force-expire' seems to resolve the issue temporally. Jul 1 09:35:06.084 [49647] dbg: bayes: learner_new self=Mail::SpamAssassin::Plugin::Bayes=HASH(0x805b09f78), bayes_store_module=Mail::SpamAssassin::BayesStore::DBM Jul 1 09:35:06.097 [49647] dbg: bayes: learner_new: got store=Mail::SpamAssassin::BayesStore::DBM=HASH(0x806108798) Jul 1 09:35:06.098 [49647] dbg: bayes: tie-ing to DB file R/O /var/amavis/.spamassassin/bayes_toks Jul 1 09:35:06.098 [49647] dbg: bayes: tie-ing to DB file R/O /var/amavis/.spamassassin/bayes_seen Jul 1 09:35:06.098 [49647] dbg: bayes: found bayes db version 3 Jul 1 09:35:06.099 [49647] dbg: bayes: DB journal sync: last sync: 0 Jul 1 09:35:06.570 [49647] dbg: bayes: DB journal sync: last sync: 0 Jul 1 09:35:06.570 [49647] dbg: bayes: corpus size: nspam = 120857, nham = 664988 After a while the error returns. Do I have to wipe my bayes DB? -- Herbert
Re: Bayer Filter Not Working
On Tue, 01 Jul 2014 09:37:17 +0200 Herbert J. Skuhra wrote: Den 25.06.2014 00:42, skrev Bruce Sackett: I apologize, I’m sure it’s been covered, but I have not been successful finding results in searches on the web or through the history of the list. I get no BAYES results in the headers, so I don’t see any working. The part that gets me is below: Jun 24 13:47:53.165 [3245] dbg: bayes: tie-ing to DB file R/O /var/lib/amavis/.spamassassin/bayes_toks Jun 24 13:47:53.166 [3245] dbg: bayes: tie-ing to DB file R/O /var/lib/amavis/.spamassassin/bayes_seen Jun 24 13:47:53.167 [3245] dbg: bayes: found bayes db version 3 Jun 24 13:47:53.167 [3245] warn: plugin: eval failed: Insecure dependency in sprintf while running with -T switch at /usr/local/share/perl/5.14.2/Mail/SpamAssassin/Logger.pm line 241. Jun 24 13:47:53.168 [3245] dbg: config: score set 0 chosen. That seems to be the last time Bayes is referenced in a spamassassin -D ―lint Has anyone else run into this? I am using an Ubuntu 12.04 server, if that makes any difference. I have the same problem on FreeBSD: Jul 1 05:33:51.765 [43144] dbg: bayes: learner_new self=Mail::SpamAssassin::Plugin::Bayes=HASH(0x805b09f78), bayes_store_module=Mail::SpamAssassin::BayesStore::DBM Jul 1 05:33:51.778 [43144] dbg: bayes: learner_new: got store=Mail::SpamAssassin::BayesStore::DBM=HASH(0x806108798) Jul 1 05:33:51.779 [43144] dbg: bayes: tie-ing to DB file R/O /var/amavis/.spamassassin/bayes_toks Jul 1 05:33:51.779 [43144] dbg: bayes: tie-ing to DB file R/O /var/amavis/.spamassassin/bayes_seen Jul 1 05:33:51.779 [43144] dbg: bayes: found bayes db version 3 Jul 1 05:33:51.779 [43144] warn: plugin: eval failed: Insecure dependency in sprintf while running with -T switch at /usr/local/lib/perl5/site_perl/5.16/Mail/SpamAssassin/Logger.pm line 241. Jul 1 05:33:51.799 [43144] warn: plugin: eval failed: Insecure dependency in sprintf while running with -T switch at /usr/local/lib/perl5/site_perl/5.16/Mail/SpamAssassin/Logger.pm line 241. Running 'sa-learn --force-expire' seems to resolve the issue temporally. Jul 1 09:35:06.084 [49647] dbg: bayes: learner_new self=Mail::SpamAssassin::Plugin::Bayes=HASH(0x805b09f78), bayes_store_module=Mail::SpamAssassin::BayesStore::DBM Jul 1 09:35:06.097 [49647] dbg: bayes: learner_new: got store=Mail::SpamAssassin::BayesStore::DBM=HASH(0x806108798) Jul 1 09:35:06.098 [49647] dbg: bayes: tie-ing to DB file R/O /var/amavis/.spamassassin/bayes_toks Jul 1 09:35:06.098 [49647] dbg: bayes: tie-ing to DB file R/O /var/amavis/.spamassassin/bayes_seen Jul 1 09:35:06.098 [49647] dbg: bayes: found bayes db version 3 Jul 1 09:35:06.099 [49647] dbg: bayes: DB journal sync: last sync: 0 Jul 1 09:35:06.570 [49647] dbg: bayes: DB journal sync: last sync: 0 Jul 1 09:35:06.570 [49647] dbg: bayes: corpus size: nspam = 120857, nham = 664988 After a while the error returns. Do I have to wipe my bayes DB? I wiped my bayes DB and learned more than 200 spam and ham messages each. While nham and nspam were below 200 message error was gone. But now it is back. % spamassassin -t OvwTlDIfJxAe [...] 3.5 BAYES_99 BODY: Bayes spam probability is 99 to 100% [score: 1.] [...] 0.2 BAYES_999 BODY: Bayes spam probability is 99.9 to 100% [score: 1.] [...] Running the same command with the -D switch the error appears and I don't see the BAYES score. There is also no BAYES score in the amavisd log. :-( Any ideas? Thanks. -- Herbert
dccproc/dccifd error
Hi,
I am using perl-5.10.1, amavisd-new 2.7.0, Mail-SpamAssassin-3.3.2 and
dcc-dccd-1.3.140.
When I receive and scan a message with a 'X-DCC-xxx-Metrics'-header the
following error is logged to maillog:
Dec 23 01:04:53 mx dccproc[81847]: unrecognized many usage: [-VdAQCHER] [-h
homedir] [-m map] [-w whiteclnt] [-T tmpdir][-a IP-address] [-f env_from]
[-t targets] [-x exitcode][-c type,[log-thold,][spam-thold]] [-g
[not-]type] [-S header][-i infile] [-o outfile] [-l logdir] [-B
dnsbl-option][-L ltype,facility.level] ; fatal error
After modifying DCC.pm the error is gone:
--- DCC.pm.bak 2011-12-22 23:03:34.0 +0100
+++ DCC.pm 2011-12-22 23:22:11.0 +0100
@@ -859,7 +859,7 @@
}
if ($tag eq dcc:) {
# query instead of report if there is an X-DCC header from upstream
- unshift(@opts, '-Q', 'many') if defined $permsgstatus-{dcc_raw_x_dcc};
+ unshift(@opts, '-Q') if defined $permsgstatus-{dcc_raw_x_dcc};
} else {
# learn or report spam
unshift(@opts, '-t', 'many');
Is this the correct fix? Or is my setup broken?
Thanks.
--
Herbert
Re: is bayes enabled by default?
At Sun, 17 Jan 2010 10:57:55 -0800 (PST), tonjg wrote: I have sa version 3.2.5 my autolearn setting always shows as 'no'. Will this eventually come on by itself or do I need to turn it on? thanks for any advice. http://wiki.apache.org/spamassassin/AutolearningNotWorking It would show disabled if use_bayes or use_bayes_autolearn is off. Have you trained enough spam/ham messages? Check bayes_min_ham_num/bayes_min_spam_num and bayes_auto_learn_threshold_spam/bayes_auto_learn_threshold_nonspam. -Herbert
Re: is bayes enabled by default?
At Sun, 17 Jan 2010 11:57:45 -0800 (PST), tonjg wrote: Herbert J. Skuhra wrote: It would show disabled if use_bayes or use_bayes_autolearn is off. Sorry, use_bayes_autolearn is wrong. :-) thanks but in what file would it show this instruction? I looked in procmailrc, local.cf and 23_bayes.cf - couldn't find anything which told me whether bayes was enabled or disabled. You can set use_bayes and bayes_auto_learn to 1 in your local.cf. -Herbert
Re: FH_DATE_PAST_20XX
At Thu, 31 Dec 2009 17:53:24 -0800 (PST),
John Hardin wrote:
On Fri, 1 Jan 2010, Mike Cardwell wrote:
I just received some HAM with a surprisingly high score. The following
rule triggered:
* 3.2 FH_DATE_PAST_20XX The date is grossly in the future.
Yet the date header looks fine to me:
Date: Fri, 1 Jan 2010 00:46:45 GMT
In /usr/share/spamassassin/72_active.cf I find:
header FH_DATE_PAST_20XX Date =~ /20[1-9][0-9]/ [if-unset: 2006]
Doesn't look particularly sane to me... I have given that rule a score
of 0 in my local.cf for now.
Agree, that should probably be [2-9][0-9].
What about
header FH_DATE_PAST_20XX Date =~ /(201[1-9])|(20[2-9][0-9])/
and
##{ FH_DATE_IS_200X
header FH_DATE_IS_200XDate =~ /200[0-9]/ [if-unset: 2006]
describe FH_DATE_IS_200XThe date is not 200x.
##} FH_DATE_IS_200X
-Herbert
