Re: KAM_RAPTOR and other dependencies...
On Tue, 23 Oct 2018 at 14:22, Kevin A. McGrail wrote: > It means I forgot to encapsulate that rule in a plugin check. Download > the latest KAM.cf and you'll be good. > > On Mon, Oct 22, 2018 at 4:40 PM Peter L. Berghold > wrote: > >> I've seen the following message and others similar: >> spamd[20463]: rules: meta test KAM_VERY_MALWARE has dependency >> 'KAM_RAPTOR' with a zero score >> >> what is spamassassin trying to tell me? >> > I am seeing 19 of these messages every day when /etc/cron.daily/spamassassin runs under anacron (Ubuntu 18.04.1, SpamAssassin 3.4.1, Perl 5.26.1). I am using the latest KAM.cf from http://www.mcgrail.com/downloads/KAM.cf which I added to /etc/spamassassin. The dependencies with zero score are: CBJ_GiveMeABreak KAM_IFRAME KAM_RAPTOR KAM_RPTR_PASSED KAM_RPTR_SUSPECT Should I ignore these messages (by modifying /etc/cron.daily/spamassassin)?
Small talk.
I started getting very short emails, such as "How are you?" or "please. can we talk please?" Ok, maybe the latter one is a bit suspicious. But in any event, has anyone encountered "small talk" spam emails like this before? I have this big desire to respond and say "No, I'm not fine, and we can't talk". But I doubt that will resolve the issue. :) I'm just curious if anyone else has encountered this. Thanks. - Mark
Re: Cannot install SpamAssassin on Ubuntu 18.04.1 (gpg not found?)
"gpg --version” returns: gpg (GnuPG) 2.2.4 libgcrypt 1.8.1 "sa-compile --version” returns: SpamAssassin version 3.4.1 I’ve attached the man page of sa-compile (on my system). (Also I’m not sure which email address I’m supposed to send my reply to, so I’m including both of them.) SA-COMPILE(1p) User Contributed Perl Documentation SA-COMPILE(1p) NAME sa-compile - compile SpamAssassin ruleset into native code SYNOPSIS sa-compile [options] Options: --listOutput base string list to STDOUT --sudoUse 'sudo' for privilege escalation --keep-tmps Keep temporary files instead of deleting -C path, --configpath=path, --config-file=path Path to standard configuration dir -p prefs, --prefspath=file, --prefs-file=file Set user preferences file --siteconfigpath=path Path for site configs (default: /etc/spamassassin) --updatedir=path Directory to place updates (default: /var/lib/spamassassin/compiled//3.004001) --cf='config line'Additional line of configuration -D, --debug [area=n,...] Print debugging messages -V, --version Print version -h, --helpPrint usage message DESCRIPTION sa-compile uses "re2c" to compile the site-wide parts of the SpamAssassin ruleset. No part of user_prefs or any files included from user_prefs can be built into the compiled set. This compiled set is then used by the "Mail::SpamAssassin::Plugin::Rule2XSBody" plugin to speed up SpamAssassin's operation, where possible, and when that plugin is loaded. "re2c" can match strings much faster than perl code, by constructing a DFA to match many simple strings in parallel, and compiling that to native object code. Not all SpamAssassin rules are amenable to this conversion, however. This requires "re2c" (see "http://re2c.org/";), and the C compiler used to build Perl XS modules, be installed. Note that running this, and creating a compiled ruleset, will have no effect on SpamAssassin scanning speeds unless you also edit your "v320.pre" file and ensure this line is uncommented: loadplugin Mail::SpamAssassin::Plugin::Rule2XSBody Additionally, "sa-compile" will not restart "spamd" or otherwise cause a scanner to reload the now-compiled ruleset automatically. OPTIONS --list Output the extracted base strings to STDOUT, instead of generating the C extension code. --sudo Use sudo(8) to run code as 'root' when writing files to the compiled-rules storage area (which is "/var/lib/spamassassin/compiled/5.026/3.004001" by default). --quiet Produce less diagnostic output. Errors will still be displayed. --keep-tmps Keep temporary files after the script completes, instead of deleting them. -C path, --configpath=path, --config-file=path Use the specified path for locating the distributed configuration files. Ignore the default directories (usually "/usr/share/spamassassin" or similar). --siteconfigpath=path Use the specified path for locating site-specific configuration files. Ignore the default directories (usually "/etc/spamassassin" or similar). --updatedir By default, "sa-compile" will use the system-wide rules update directory: /var/lib/spamassassin/compiled/5.026/3.004001 If the updates should be stored in another location, specify it here. Note that use of this option is not recommended; if sa-compile is placing the compiled rules the wrong directory, you probably need to rebuild SpamAssassin with different "Makefile.PL" arguments, instead of overriding sa-compile's runtime behaviour. --cf='config line' Add additional lines of configuration directly from the command-line, parsed after the configuration files are read. Multiple --cf arguments can be used, and each will be considered a separate line of configuration. -p prefs, --prefspath=prefs, --prefs-file=prefs Read user score preferences from prefs (usually "$HOME/.spamassassin/user_prefs") . -D [area,...], --debug [area,...] Produce debugging output. If no areas are listed, all debugging information is printed. Diagnostic output can also be enabled for each area individually; area is the area of the code to instrument. For more information about which areas (also known as channels) are available, ple
Re: Cannot install SpamAssassin on Ubuntu 18.04.1 (gpg not found?)
On Wed, 24 Oct 2018 19:50:42 -0400 Alexander Lieflander wrote: > Hello, > > When I try to install SpamAssassin via aptitude, the installation > never gets past dpkg configuring them. The specific error reads: > > error: gpg required but not found! It is not recommended, but you > can use "sa-update" with the --no-gpg to skip the verification. > > The weird thing is that I have the most recent version of gpg > installed. what's the output of gpg --version > And when I try the suggestion from the first error message > (i.e. "sa-update --no-gpg”), I get another error that reads: > > Unknown option: no-gpg > > The man page for sa-update also doesn’t list that option anywhere… It does list --nogpg. > Any ideas? By the way, I’ve attached the logs of my most recent > installation attempt. > > I’m using Ubuntu (server) 18.04.1 LTS. >
Cannot install SpamAssassin on Ubuntu 18.04.1 (gpg not found?)
Hello, When I try to install SpamAssassin via aptitude, the installation never gets past dpkg configuring them. The specific error reads: error: gpg required but not found! It is not recommended, but you can use "sa-update" with the --no-gpg to skip the verification. The weird thing is that I have the most recent version of gpg installed. And when I try the suggestion from the first error message (i.e. "sa-update --no-gpg”), I get another error that reads: Unknown option: no-gpg The man page for sa-update also doesn’t list that option anywhere… Any ideas? By the way, I’ve attached the logs of my most recent installation attempt. I’m using Ubuntu (server) 18.04.1 LTS. Reading package lists... Building dependency tree... Reading state information... The following additional packages will be installed: libcrypt-openssl-bignum-perl libcrypt-openssl-rsa-perl libmail-dkim-perl libmail-spf-perl libnet-dns-perl libnet-ip-perl libnetaddr-ip-perl re2c sa-compile Suggested packages: razor libdbi-perl pyzor libencode-detect-perl libgeo-ip-perl libnet-patricia-perl The following NEW packages will be installed: libcrypt-openssl-bignum-perl libcrypt-openssl-rsa-perl libmail-dkim-perl libmail-spf-perl libnet-dns-perl libnet-ip-perl libnetaddr-ip-perl re2c sa-compile spamassassin 0 upgraded, 10 newly installed, 0 to remove and 0 not upgraded. Need to get 2078 kB of archives. After this operation, 6990 kB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 libcrypt-openssl-bignum-perl amd64 0.09-1build1 [24.7 kB] Get:2 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 libcrypt-openssl-rsa-perl amd64 0.28-5build2 [21.7 kB] Get:3 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 libnet-ip-perl all 1.26-1 [31.5 kB] Get:4 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 libnet-dns-perl all 1.10-2 [335 kB] Get:5 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 libmail-dkim-perl all 0.44-1 [118 kB] Get:6 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 libnetaddr-ip-perl amd64 4.079+dfsg-1build2 [81.2 kB] Get:7 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 libmail-spf-perl all 2.9.0-4 [115 kB] Get:8 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 re2c amd64 1.0.1-1 [274 kB] Get:9 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 spamassassin all 3.4.1-8build1 [1063 kB] Get:10 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 sa-compile all 3.4.1-8build1 [13.2 kB] Fetched 2078 kB in 1s (1910 kB/s) Selecting previously unselected package libcrypt-openssl-bignum-perl. (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 146321 files and directories currently installed.) Preparing to unpack .../0-libcrypt-openssl-bignum-perl_0.09-1build1_amd64.deb ... Unpacking libcrypt-openssl-bignum-perl (0.09-1build1) ... Selecting previously unselected package libcrypt-openssl-rsa-perl. Preparing to unpack .../1-libcrypt-openssl-rsa-perl_0.28-5build2_amd64.deb ... Unpacking libcrypt-openssl-rsa-perl (0.28-5build2) ... Selecting previously unselected package libnet-ip-perl. Preparing to unpack .../2-libnet-ip-perl_1.26-1_all.deb ... Unpacking libnet-ip-perl (1.26-1) ... Selecting previously unselected package libnet-dns-perl. Preparing to unpack .../3-libnet-dns-perl_1.10-2_all.deb ... Unpacking libnet-dns-perl (1.10-2) ... Selecting previously unselected package libmail-dkim-perl. Preparing to unpack .../4-libmail-dkim-perl_0.44-1_all.deb ... Unpacking libmail-dkim-perl (0.44-1) ... Selecting previously unselected package libnetaddr-ip-perl. Preparing to unpack .../5-libnetaddr-ip-perl_4.079+dfsg-1build2_amd64.deb ... Unpacking libnetaddr-ip-perl (4.079+dfsg-1build2) ... Selecting previously unselected package libmail-spf-perl. Preparing to unpack .../6-libmail-spf-perl_2.9.0-4_all.deb ... Unpacking libmail-spf-perl (2.9.0-4) ... Selecting previously unselected package re2c. Preparing to unpack .../7-re2c_1.0.1-1_amd64.deb ... Unpacking re2c (1.0.1-1) ... Selecting previously unselected package spamassassin. Preparing to unpack .../8-spamassassin_3.4.1-8build1_all.deb ... Unpacking spamassassin (3.4.1-8build1) ... Selecting previously unselected package sa-compile. Preparing to unpack .../9-sa-compile_3.4.1-8build1_all.deb ... Unpacking sa-compile (3.4.1-8build1) ... Processing triggers for ureadahead (0.100.0-20) ... Setting up libnet-ip-perl (1.26-1) ... Setting up re2c (1.0.1-1) .
Re: spamd fails to remove bayes.lock file
Have you check permissions on './spamassassin'? I had semiliar issue in the past! Thanks, Motty On 10/24/18 8:10 AM, John Hardin wrote: On Wed, 24 Oct 2018, Emanuel Gonzalez wrote: Hello.!! I have a problem with the `/.spamassassin/bayes.lock` This is the error I'm seeing : Oct 23 15:12:14 server spamd[18073]: bayes: cannot open bayes databases /.spamassassin/bayes_* R/W: lock failed: File exists Oct 23 15:12:14 server spamd[18157]: bayes: cannot open bayes databases /.spamassassin/bayes_* R/W: lock failed: File exists Oct 23 15:12:14 server spamd[18107]: bayes: cannot open bayes databases /.spamassassin/bayes_* R/W: lock failed: File exists The command `spamassassin -V` is showing : SpamAssassin version 3.4.1 running on Perl version 5.10.1 bayes_expiry_max_db_size 15 bayes_learn_to_journal 1 bayes_auto_learn 0 128K bayes_journal 547M bayes_seen 4,0M bayes_toks # spamassassin SPAMDOPTIONS="-u nobody -H --round-robin --min-children=30 --max-children=190 --min-spare=5 --max-spare=80 --timeout-child=120 --max-conn-per-child=100 -i -A IP" # directory perms Also the command `ll -d /.spamassassin` is showing : drwxrwxrwx 3 nobody nobody 4096 oct 23 15:16 /.spamassassin I restart the service and it works, but the problem reappears again Do you have any idea how to solve it? As was suggested earlier, disable auto-expiry and run a cron job to expire Bayes tokens.
Re: spamd fails to remove bayes.lock file
On Wed, 24 Oct 2018, Emanuel Gonzalez wrote: Hello.!! I have a problem with the `/.spamassassin/bayes.lock` This is the error I'm seeing : Oct 23 15:12:14 server spamd[18073]: bayes: cannot open bayes databases /.spamassassin/bayes_* R/W: lock failed: File exists Oct 23 15:12:14 server spamd[18157]: bayes: cannot open bayes databases /.spamassassin/bayes_* R/W: lock failed: File exists Oct 23 15:12:14 server spamd[18107]: bayes: cannot open bayes databases /.spamassassin/bayes_* R/W: lock failed: File exists The command `spamassassin -V` is showing : SpamAssassin version 3.4.1 running on Perl version 5.10.1 bayes_expiry_max_db_size 15 bayes_learn_to_journal 1 bayes_auto_learn 0 128Kbayes_journal 547Mbayes_seen 4,0Mbayes_toks # spamassassin SPAMDOPTIONS="-u nobody -H --round-robin --min-children=30 --max-children=190 --min-spare=5 --max-spare=80 --timeout-child=120 --max-conn-per-child=100 -i -A IP" # directory perms Also the command `ll -d /.spamassassin` is showing : drwxrwxrwx 3 nobody nobody 4096 oct 23 15:16 /.spamassassin I restart the service and it works, but the problem reappears again Do you have any idea how to solve it? As was suggested earlier, disable auto-expiry and run a cron job to expire Bayes tokens. -- 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 --- Britain used to be the most powerful empire in the world. Now they're terrified of pocketknives. How the mighty have fallen. -- Matt Walsh --- 573 days since the first commercial re-flight of an orbital booster (SpaceX)
Re: Bayes error (lock failed: File exists)
On Wed, 24 Oct 2018 13:20:11 + Emanuel Gonzalez wrote: > Any help? You've posted four versions of this question, with only minor variations, including one with a completely unrelated subject line. Please use the thread where there are already replies.
RE: Bayes error (lock failed: File exists)
Any help?
spamd fails to remove bayes.lock file
Hello.!! I have a problem with the `/.spamassassin/bayes.lock` This is the error I'm seeing : Oct 23 15:12:14 server spamd[18073]: bayes: cannot open bayes databases /.spamassassin/bayes_* R/W: lock failed: File exists Oct 23 15:12:14 server spamd[18157]: bayes: cannot open bayes databases /.spamassassin/bayes_* R/W: lock failed: File exists Oct 23 15:12:14 server spamd[18107]: bayes: cannot open bayes databases /.spamassassin/bayes_* R/W: lock failed: File exists The command `spamassassin -V` is showing : SpamAssassin version 3.4.1 running on Perl version 5.10.1 bayes_expiry_max_db_size 15 bayes_learn_to_journal 1 bayes_auto_learn 0 128Kbayes_journal 547Mbayes_seen 4,0Mbayes_toks # spamassassin SPAMDOPTIONS="-u nobody -H --round-robin --min-children=30 --max-children=190 --min-spare=5 --max-spare=80 --timeout-child=120 --max-conn-per-child=100 -i -A IP" # directory perms Also the command `ll -d /.spamassassin` is showing : drwxrwxrwx 3 nobody nobody 4096 oct 23 15:16 /.spamassassin I restart the service and it works, but the problem reappears again Do you have any idea how to solve it? Regards,
spamd: error: failed to obtain port and ip from socket
Hello.!! I have a problem with the `/.spamassassin/bayes.lock` This is the error I'm seeing : Oct 23 15:12:14 server spamd[18073]: bayes: cannot open bayes databases /.spamassassin/bayes_* R/W: lock failed: File exists Oct 23 15:12:14 server spamd[18157]: bayes: cannot open bayes databases /.spamassassin/bayes_* R/W: lock failed: File exists Oct 23 15:12:14 server spamd[18107]: bayes: cannot open bayes databases /.spamassassin/bayes_* R/W: lock failed: File exists The command `spamassassin -V` is showing : SpamAssassin version 3.4.1 running on Perl version 5.10.1 bayes_expiry_max_db_size 15 bayes_learn_to_journal 1 bayes_auto_learn 0 128Kbayes_journal 547Mbayes_seen 4,0Mbayes_toks # spamassassin SPAMDOPTIONS="-u nobody -H --round-robin --min-children=30 --max-children=190 --min-spare=5 --max-spare=80 --timeout-child=120 --max-conn-per-child=100 -i -A IP" # directory perms Also the command `ll -d /.spamassassin` is showing : drwxrwxrwx 3 nobody nobody 4096 oct 23 15:16 /.spamassassin I restart the service and it works, but the problem reappears again Do you have any idea how to solve it? Regards,
