not work :)
Yeah I've just switched to amavisd and it's working perfectly. Still
confused by the spamd arg length error, as I see a lot of people online
saying they're using the same setup and not seeing the error online, but
oh well, at least I have spam filtering on my server n
revsuine skrev den 2024-11-04 04:57:
Trying to use SpamAssassin with Postfix using spamd:
https://cwiki.apache.org/confluence/display/SPAMASSASSIN/IntegratedSpamdInPostfix
drop this
and ask a maintainer for import spampd from here
https://github.com/mpaperno/spampd
its a simple proxy smtp
Hi all,
Trying to use SpamAssassin with Postfix using spamd:
https://cwiki.apache.org/confluence/display/SPAMASSASSIN/IntegratedSpamdInPostfix
Unfortunately emails are not going to my inbox processed by
SpamAssassin. Postfix seems to be calling SpamAssassin correctly, as I
see this in my
it turns off _URIDOMAINS_ so its always empty results, i have thinked it
could expose all urls just did not do any dns resolving on any dnsbl or
rbl, was it not the propose ?
is code change possible so in --local it still shows domains content ?
Bill Cole wrote on 22/03/24 8:36 am:
It seems to me that it would require extension of the spamc/spamd protocol and
cargo-culting some code from spamassassin to spamd.
Doesn't look like much cargo-culting to do. The spamassassin script just
calls a function in Mail::SpamAssassin.pm for
nalities of the spamassassin script when using the spamc/spamd
interface.
Does anyone see it hiding somewhere that I don't?
Does anyone have any rationale for this missing functionality?
I don't expect that it would be difficult to add. (Something I've
believed every ti
me]list functionalities of the
>> spamassassin script when using the spamc/spamd interface.
>>
>> Does anyone see it hiding somewhere that I don't?
>>
>> Does anyone have any rationale for this missing functionality?
>>
>> I don't expect that it would b
ck,welcome]list
functionalities of the spamassassin script when using the spamc/spamd
interface.
Does anyone see it hiding somewhere that I don't?
Does anyone have any rationale for this missing functionality?
I don't expect that it would be difficult to add. (Something I've
believed eve
he spamassassin script when using the spamc/spamd
interface.
Does anyone see it hiding somewhere that I don't?
Does anyone have any rationale for this missing functionality?
I don't expect that it would be difficult to add. (Something I've
believed every time I've taken on
On 3/20/24 21:58, Bill Cole wrote:
I'm not sure how I've not noticed before, but unless I'm missing something,
there is no way to replicate the [block,welcome]list functionalities of the
spamassassin script when using the spamc/spamd interface.
Does anyone see it hiding somewhe
On 20.03.24 16:58, Bill Cole wrote:
I'm not sure how I've not noticed before, but unless I'm missing
something, there is no way to replicate the [block,welcome]list
functionalities of the spamassassin script when using the spamc/spamd
interface.
Does anyone see it hiding s
Bill Cole wrote:
I'm not sure how I've not noticed before, but unless I'm missing
something, there is no way to replicate the [block,welcome]list
functionalities of the spamassassin script when using the spamc/spamd
interface.
Does anyone see it hiding somewhere that I don&
I'm not sure how I've not noticed before, but unless I'm missing
something, there is no way to replicate the [block,welcome]list
functionalities of the spamassassin script when using the spamc/spamd
interface.
Does anyone see it hiding somewhere that I don't?
Does anyon
I'm in the process of setting up virtual users on my mail server. It
looks like I may have a mix of both real and virtual users.
The flow when scanning a message is:
sendmail -> spamass-milter -> spamc -> spamd
spamass-milter looks at the To: header and passes just the user pa
On 31.10.23 09:10, Linkcheck via users wrote:
Thanks, Matus. So nice when these little changes creep up on you. :)
I have merged the new OPTIONS with my old one...
OPTIONS="--create-prefs --nouser-config -4 -i 127.0.0.1
--max-children=5 --helper-home-dir=/var/lib/spamassassin -u
debian-
ren=5 --helper-home-dir=/var/lib/spamassassin -u
debian-spamd"
I assume that's ok.
yes, although --create-prefs is useless when you use --nouser-config
and --create-prefs needs root ?
so if needed prefs, setup sql/ldap based userprefs
> yes, although --create-prefs is useless when you use --nouser-config
Thanks. I'll look at the docs.
On 31.10.23 09:10, Linkcheck via users wrote:
Thanks, Matus. So nice when these little changes creep up on you. :)
I have merged the new OPTIONS with my old one...
OPTIONS="--create-prefs --nouser-config -4 -i 127.0.0.1
--max-children=5 --helper-home-dir=/var/lib/spamassassin -u
debian-
Thanks, Vincent. I hadn't spotted that.
Thanks, Matus. So nice when these little changes creep up on you. :)
I have merged the new OPTIONS with my old one...
OPTIONS="--create-prefs --nouser-config -4 -i 127.0.0.1 --max-children=5
--helper-home-dir=/var/lib/spamassassin -u debian-spamd"
I assume that's ok.
On 2023-10-30 16:45:31 +, Linkcheck via users wrote:
> I have just updated Debian to Bookworm in order to install SA 4. Very few
> problems so far but the postfix log is giving:
>
> "spamd: still running as root: user not specified with -u, not found, or set
> to root, fa
On 30.10.23 16:45, Linkcheck via users wrote:
I have just updated Debian to Bookworm in order to install SA 4. Very
few problems so far but the postfix log is giving:
"spamd: still running as root: user not specified with -u, not found,
or set to root, falling back to nobody"
I a
On 2023-10-30 at 12:45:31 UTC-0400 (Mon, 30 Oct 2023 16:45:31 +)
Linkcheck via users
is rumored to have said:
I have just updated Debian to Bookworm in order to install SA 4. Very
few problems so far but the postfix log is giving:
"spamd: still running as root: user not specified wi
I have just updated Debian to Bookworm in order to install SA 4. Very
few problems so far but the postfix log is giving:
"spamd: still running as root: user not specified with -u, not found, or
set to root, falling back to nobody"
I am not sure where to specify an appropriate
>
> I should probably add that I personally don't do per-user config because
> of the enlarged attack surface it presents and small marginal value, but
> that's guided by local details. I work with systems owned by others
> where other choices were made for very sound reasons and they have not
> h
' for their installations is beyond the
scope of the SA project per se, and the specific packagers should be
consulted if you need an explanation of their choices.
If you want spamd to be able to access the per-user preferences and
databases for AWL/TxRep and/or Bayes of real system users,
Check the systemd unit file. It should set the user the service runs as.
Hi All,
I changed the subject line to hopefully get some insight from a wider
audience regarding this situation that Reindl uncovered:
It started here:
It appears that it IS running as root?! OR maybe as "sa-milt" ... As
root I got this:
# ps auxwww | grep spamd
root
On 1/2/2023 4:27 PM, Bill Cole wrote:
On 2023-01-02 at 16:18:53 UTC-0500 (Mon, 2 Jan 2023 16:18:53 -0500)
joe a
is rumored to have said:
On 1/2/2023 4:01 PM, joe a wrote:
On 1/2/2023 2:49 PM, joe a wrote:
Noticed this line in /var/log/mail:
spamd[31188]: config: failed to parse line
Bill Cole skrev den 2023-01-02 22:22:
Whenever you change a SpamAssassin config file, you should run
'spamassassin --lint' to make sure it is parsing correctly.
loadplugin does --lint even in cf files imho, but it should not
i have not tested yet in sa 4.x.x with this
joe a skrev den 2023-01-02 22:18:
Wow. It appears you actually have to state "loadplugin".
A great way to start a new year.
and it should in no way be in a cf file, loadplugin belongs to pre files
simple to fix with sed
On 2023-01-02 at 16:18:53 UTC-0500 (Mon, 2 Jan 2023 16:18:53 -0500)
joe a
is rumored to have said:
On 1/2/2023 4:01 PM, joe a wrote:
On 1/2/2023 2:49 PM, joe a wrote:
Noticed this line in /var/log/mail:
spamd[31188]: config: failed to parse line, skipping, in
"/etc/mail/spamass
On 2023-01-02 at 16:01:34 UTC-0500 (Mon, 2 Jan 2023 16:01:34 -0500)
joe a
is rumored to have said:
On 1/2/2023 2:49 PM, joe a wrote:
Noticed this line in /var/log/mail:
spamd[31188]: config: failed to parse line, skipping, in
"/etc/mail/spamassassin/local.cf":
Mail::SpamAssass
On 1/2/2023 4:01 PM, joe a wrote:
On 1/2/2023 2:49 PM, joe a wrote:
Noticed this line in /var/log/mail:
spamd[31188]: config: failed to parse line, skipping, in
"/etc/mail/spamassassin/local.cf": Mail::SpamAssassin::Plugin::URIDNSBL
It seems to have started a few weeks ago an
On 1/2/2023 2:49 PM, joe a wrote:
Noticed this line in /var/log/mail:
spamd[31188]: config: failed to parse line, skipping, in
"/etc/mail/spamassassin/local.cf": Mail::SpamAssassin::Plugin::URIDNSBL
It seems to have started a few weeks ago and does not appear to be
related to t
Noticed this line in /var/log/mail:
spamd[31188]: config: failed to parse line, skipping, in
"/etc/mail/spamassassin/local.cf": Mail::SpamAssassin::Plugin::URIDNSBL
It seems to have started a few weeks ago and does not appear to be
related to the date of any deliberate changes
On Fri, Oct 07, 2022 at 10:58:07AM +0200, Matus UHLAR - fantomas wrote:
I have configured my personal user_prefs to process options for extracttext.
so far, spamd complains:
Oct 7 09:29:05 fantomas spamd[26887]: spamd: setuid to uhlar succeeded
Oct 7 09:29:05 fantomas spamd[26887]: config
On Fri, Oct 07, 2022 at 10:58:07AM +0200, Matus UHLAR - fantomas wrote:
> Hello,
>
> I have configured my personal user_prefs to process options for extracttext.
>
> so far, spamd complains:
>
> Oct 7 09:29:05 fantomas spamd[26887]: spamd: setuid to uhlar succeeded
>
Hello,
I have configured my personal user_prefs to process options for extracttext.
so far, spamd complains:
Oct 7 09:29:05 fantomas spamd[26887]: spamd: setuid to uhlar succeeded
Oct 7 09:29:05 fantomas spamd[26887]: config: failed to parse line in
/home/uhlar/.spamassassin/user_prefs
include dnswl.
Recommendation to install local dns caching server followed.
Once installed, large numbers of messages started to appear in
maillog.
The messages you included indicate that you've got spamd running with
debug enabled. The usual way to set debugging is in
/etc/sysconfig/spamassassin
ns caching server followed.
>> Once installed, large numbers of messages started to appear in maillog.
>
> The messages you included indicate that you've got spamd running with
> debug enabled. The usual way to set debugging is in
> /etc/sysconfig/spamassassin with the
followed.
Once installed, large numbers of messages started to appear in
maillog.
The messages you included indicate that you've got spamd running with
debug enabled. The usual way to set debugging is in
/etc/sysconfig/spamassassin with the 'SPAMDOPTIONS' parameter. The
option t
On 2022-05-29 01:25, DL Neil wrote:
SpamAssassin x86_64 3.4.0 CentOS 6.el7 release
Postfix 2.10.1
unbound 1.6.6
upgrade centos
and check you dont added -D or --debug into spamd options
more help show spamd options
DL Neil:
> SpamAssassin x86_64 3.4.0 CentOS 6.el7 release
> Postfix 2.10.1
> unbound 1.6.6
This does not answer your question, but I noticed that the versions you
gave are all ~5–8 years old. Often enough such problems disappear after
upgrading to a current version.
=
May 28 22:12:57 vps517507 opendkim[16791]: DAE2B6AAE: DKIM-Signature
field added (s=staff, d=etelligence.info)
May 28 22:12:57 vps517507 postfix/qmgr[22236]: DAE2B6AAE:
from=, size=17034, nrcpt=2 (queue active)
May 28 22:12:57 vps517507 spamd[11912]: spamd: connection from localhost
[::1]:49920 to
I am testing with containerizing the spamd and I was wondering what would be a
good solution to configure multiple spamd. What is the general advice on this
here?
1. multiple instances
If I spawn multiple instances of the same container, I would get multiple ip
addresses something like
> > ~]# spamass-milter -h
> > spamass-milter: invalid option -- 'h'
> > spamass-milter - Version 0.4.0
> > SpamAssassin Sendmail Milter Plugin
> > Usage: spamass-milter -p socket [-b|-B bucket] [-d xx[,yy...]] [-D host]
> > [-e defaultdomain] [-f] [-i networks] [-m] [-M]
> >
Marc writes:
>> On 06.02.22 14:02, Marc wrote:
>> >Thanks! Got it to work with this:
>> >EXTRA_FLAGS=" -D xx.xxx.xxx -- -p 34219"
>>
>> the man page for spamass-milter says:
>>
>> -D host
>> Co
> On 06.02.22 14:02, Marc wrote:
> >Thanks! Got it to work with this:
> >EXTRA_FLAGS=" -D xx.xxx.xxx -- -p 34219"
>
> the man page for spamass-milter says:
>
> -D host
> Connects to a remote spamd server on host, instead of using
it to work with this:
EXTRA_FLAGS=" -D xx.xxx.xxx -- -p 34219"
the man page for spamass-milter says:
-D host
Connects to a remote spamd server on host, instead of using one
on localhost. This option is deprecated; use -- -d host instead.
so, 1. it'
> Usually a SpamAssassin milter can accept additional arguments after ‘--’
> that it will pass to spamc. So:
>
> spamassassin-milter ...other args... -- -d 192.168.10.243 -p 34219
>
> Or configure the connection in /etc/spamassassin/spamc.conf, that works
> too.
Thanks! Got it to work with this:
Marc:
> I have problems configuring the spamass-milter to connect to the remote
> spamd. I am constantly getting
>
> getaddrinfo(192.168.10.243:34219) failed: Name or service not known
> could not resolve any hosts (192.168.10.243:34219): no such host
>
> Nothing of th
I have problems configuring the spamass-milter to connect to the remote spamd.
I am constantly getting
getaddrinfo(192.168.10.243:34219) failed: Name or service not known
could not resolve any hosts (192.168.10.243:34219): no such host
Nothing of these seem to work
-D 192.168.10.243:34219 inet
Brilliant! Thank you very much, David. No warnings, no errors now.
--
Dave Stiles
-max-children=5
--helper-home-dir=/var/lib/spamassassin -u debian-spamd"
and the spamass-milter options:
OPTIONS="-u spamass-milter -- -d 127.0.0.1"
Once I remembered that spamass-milter also needed to be restarted, along with
spamassassin and postfix, I made more progress. :
On 18/10/2021 11:20 am, Matus UHLAR - fantomas wrote:
spamd by default tries to find recipients' home directories and user
preferences in them. try passing following option to spamd:
-x, --nouser-config, --user-config
On 18.10.21 14:47, Linkcheck wrote:
Thanks. Where would I act
On Mon, 18 Oct 2021, Linkcheck wrote:
On 18/10/2021 11:20 am, Matus UHLAR - fantomas wrote:
spamd by default tries to find recipients' home directories and user
preferences in them. try passing following option to spamd:
instruct spamd to connect to 127.0.0.1
Sorry, I'm not sur
On Mon, 18 Oct 2021, Linkcheck wrote:
On 18/10/2021 11:20 am, Matus UHLAR - fantomas wrote:
spamd by default tries to find recipients' home directories and user
preferences in them. try passing following option to spamd:
-x, --nouser-config, --user-config
Thanks. Where wo
Linkcheck writes:
>> instruct spamd to connect to 127.0.0.1
>
> Sorry, I'm not sure where to do that. I've tried as noted in the OP; I
> can't find anywhere else (remembering I've dropped spamfilter.sh).
I'm fuzzy on the details but hope this helps
On 18/10/2021 11:20 am, Matus UHLAR - fantomas wrote:
spamd by default tries to find recipients' home directories and user
preferences in them. try passing following option to spamd:
-x, --nouser-config, --user-config
Thanks. Where would I actually add that? Which file / co
The problem with browsing online for an answer is that everyone seems to
have a different solution. Obviously, I've managed to combine two
solutions. Thanks for the pointer!
I've tried both types independantly now and opted for the milter, since
the other one does not use any of my own regex f
resolution
for either warning. The server is debian 10 buster.
1) "spamd: handle_user (userdir) unable to find user: 'dave'"
Postfix is using dovecot to resolve users but 'dave' is not a user.
spamd by default tries to find recipients' home directories
One thing that needs clarification is how you want to integrate spam
filtering with SpamAssassin with Postfix:
Apparently, you are trying to do this with two different methods at
once? Once with spamass-milter, which is a milter that uses spamc to
integrate SpamAssassin with Postfix. And once with
server is debian 10 buster.
1) "spamd: handle_user (userdir) unable to find user: 'dave'"
Postfix is using dovecot to resolve users but 'dave' is not a user. The
processing completes without it but I don't know what the process is
trying to do with the user t
Hi everybody!
Sometimes sending HUP signal to the parent spamd daemon, or even restarting it,
do not cause a reload in all spam childs. normally (99% of times) all
childs work with current config as expected but 1% of the times...some childs
work with current config and some childs keep
On 11 Jun 2020, PGNet Dev outgrape:
> for anyone interested, it appears the config, as advised, is a bit of a mess
>
> using _explicit_ config of
>
>./configure \
>--with-installroot=/ \
> --mandir=/usr/local/man \
> --bindir=/usr/local/bin \
> --libexecdir
--with-installroot=/ \
--mandir=/usr/local/man \
--bindir=/usr/local/bin \
--libexecdir=/usr/local/libexec/dcc \
--homedir=/var/lib/dcc \
--with-uid=spamd \
--disable-server \
--disable-dccm \
i've built & installed a new instance of
spamd -V
SpamAssassin Server version 3.4.4
running on Perl 5.26.1
with SSL support (IO::Socket::SSL 2.067)
with zlib support (Compress::Zlib 2.093)
running on
On Tue, 9 Jun 2020 19:55:24 -0700
PGNet Dev wrote:
> sorry, that's unclear
>
> spamc --help | egrep "config|socket|fallback|size|username|log-to"
> -U, --socket path Connect to spamd via UNIX domain sockets.
> -F, --config path Use this configuration fil
On 6/9/20 7:45 PM, PGNet Dev wrote:
> RW Tue, 09 Jun 2020 17:15:49 -0700
> If you need this line you are doing something strange.
always happy to simplify.
rm'ing
--configpath=/usr/local/etc/spamassassin \
from spamd launch, I still see
...
Jun 09 19:44
On Tue, 9 Jun 2020 16:27:01 -0700
PGNet Dev wrote:
> next, launching 'spamd',
>
>--configpath=/usr/local/etc/spamassassin \
If you need this line you are doing something strange.
You are overriding the default config location with the default site
config locatio
I'm setting up a local/standalone instance spamd on linux
lsb_release -rd
Description:openSUSE Leap 15.1
Release:15.1
uname -rm
5.7.1-25.gc4df4ce-default x86_64
perl -v
This is perl 5, ve
Thanks, RW.
The problem I'm having is that the system service isn't running any of
the network tests, but they do run when I send the same sample through
spamassassin from the command line. It has nothing to do with the
particular piece of spam. There is some sort of permission problem (I
thin
On Wed, 5 Feb 2020 08:18:34 -0600
Hugh Sparks wrote:
> I have a sample spam in file test_01.
> ...
> And get a nice rejection with hits from many rules:
>...
> The same message test_01 appeared in my inbox with this header:
> ...X-Spam-Status: No, score=2.7
...
> many of the rules mentioned in th
sendmail-8.15
spamassassin-3.43
procmail-3.22,
perl-Razor-Agent-2.85
Systemd is configured to run the spamassassin.service on startup
which executes:
/usr/bin/spamd $SPAMDOPTIONS
SPAMDOPTIONS="-c -m5 -H --razor-home-dir='/var/lib/razor/'
--razor-log-file='sys-syslog'"
Thanks for any insight!
On 8 Jan 2020, at 3:42, Guido Goluke, MajorLabel wrote:
Hello,
I would like to control user preferences through SQL and read the
docs, that stated you should start spamd with the -q option. As a
novice that installed spamassassin through apt in Ubuntu, it's
installed as a systemd se
On 8 Jan 2020, at 3:42, Guido Goluke, MajorLabel wrote:
Hello,
I would like to control user preferences through SQL and read the
docs, that stated you should start spamd with the -q option. As a
novice that installed spamassassin through apt in Ubuntu, it's
installed as a systemd se
Hello,
I would like to control user preferences through SQL and read the docs,
that stated you should start spamd with the -q option. As a novice that
installed spamassassin through apt in Ubuntu, it's installed as a
systemd service and runs as a postfix milter. Should I just alte
On Fri, 29 Nov 2019, Tom H wrote:
Hey everyone,
I have a few questions about something I'm encountering with spamd.
I've noticed cases where a bounce message to the server results in spamd
'exceeded time limit'. It reaches the limit of 300+ seconds. In this
particular ca
On Fri, 29 Nov 2019 16:19:23 -0700 (MST)
Tom H wrote:
> Hey everyone,
>
> I have a few questions about something I'm encountering with spamd.
>
> I've noticed cases where a bounce message to the server results in
> spamd 'exceeded time limit'. It reache
Hey everyone,
I have a few questions about something I'm encountering with spamd.
I've noticed cases where a bounce message to the server results in spamd
'exceeded time limit'. It reaches the limit of 300+ seconds. In this
particular case, the message size is 564kB and co
RW wrote:
On Wed, 5 Jun 2019 10:45:13 -0400
Kris Deugau wrote:
jim.ander...@wohosting.net wrote:
Greetings,
I've searched but haven't had any luck finding documentation about
how to determine the optimal settings for spamd children
(max-children, min-children, max-spare, min-spar
On Wed, 5 Jun 2019 10:45:13 -0400
Kris Deugau wrote:
> jim.ander...@wohosting.net wrote:
> > Greetings,
> >
> > I've searched but haven't had any luck finding documentation about
> > how to determine the optimal settings for spamd children
> > (max-c
On Wed, 5 Jun 2019, jim.ander...@wohosting.net wrote:
Greetings,
I've searched but haven't had any luck finding documentation about how to
determine the optimal settings for spamd children (max-children,
min-children, max-spare, min-spare, and max-conn-per-child). I have a
dedica
jim.ander...@wohosting.net wrote:
Greetings,
I've searched but haven't had any luck finding documentation about how
to determine the optimal settings for spamd children (max-children,
min-children, max-spare, min-spare, and max-conn-per-child). I have a
dedicated server for running
Greetings,
I've searched but haven't had any luck finding documentation about how
to determine the optimal settings for spamd children (max-children,
min-children, max-spare, min-spare, and max-conn-per-child). I have a
dedicated server for running spamd. It has 6GB (can add m
On Fri, 31 May 2019 00:50:27 +0100
RW wrote:
> On Thu, 30 May 2019 23:29:10 +0100
> RW wrote:
>
> > On Thu, 30 May 2019 23:24:06 +0200
> > Yves Goergen wrote:
> >
> >
> > > BTW, why doesn't the --max-children option do anything? There are
> > > always 5 child processes, no matter how busy the
spawned instantaneously.
Children can be spawned from the old code in spamd, if the number drops
below the minimum, or from the scaling code, which is event driven
based on child messages.
I'm guessing that when the code in spamd replaces the killed child it
creates a cascade of events f
On Thu, 30 May 2019 23:24:06 +0200
Yves Goergen wrote:
> BTW, why doesn't the --max-children option do anything? There are
> always 5 child processes, no matter how busy they are. And when
> they're all busy, nothing works anymore.
I couldn't reproduce this on FreeBSD with perl 5.28.
're all busy, nothing works anymore.
>
> What are your arguments to spamd?
Sorry, I missed that you'd already given them.
On Thu, 30 May 2019 23:24:06 +0200
Yves Goergen wrote:
> BTW, why doesn't the --max-children option do anything? There are
> always 5 child processes, no matter how busy they are. And when
> they're all busy, nothing works anymore.
What are your arguments to spamd?
Thank you,
That's what I've also found somewhere. Since the rules were not fixed
this morning I have disabled that rule and it's stable again today.
Over the last night I've helped with a workaround to restart spamd every
20 minutes via cron. The monitoring did show maxim
On 5/29/2019 3:41 PM, Yves Goergen wrote:
Hello,
Today SpamAssassin started failing on my server system. I could
observe the following:
* There are 5 processes named "spamd child" with very high (100%) CPU
usage
This could be the style gibberish rule hanging. There's anoth
There is a meta that Karsten posted on list and we have it in KAM.cf if you
use and update that. Masscheck can take days to publish rules
unfortunately.
On Wed, May 29, 2019, 18:59 John Hardin wrote:
> On Thu, 30 May 2019, Yves Goergen wrote:
>
> > * There are 5 processes named
On Thu, 30 May 2019, Yves Goergen wrote:
* There are 5 processes named "spamd child" with very high (100%) CPU usage
...
I have never seen this behaviour before. As it is now, the spam filter is
making my mail service very unreliable for incoming mail. What can I do to
fix that?
Hello,
Today SpamAssassin started failing on my server system. I could observe
the following:
* There are 5 processes named "spamd child" with very high (100%) CPU usage
* The Exim mail server temporarily rejects the recipients because it
cannot connect to the spamd server
This i
4:5.16.3-294.el7_6
@updates
De: Bill Cole
Enviado: martes, 28 de mayo de 2019 16:41
Para: Mailing-List spamassassin
Asunto: Re: Spamd error message "spamd:
On 28 May 2019, at 14:55, Emanuel Gonzalez wrote:
Hello, i updated perl via yum.
# spamassassin --version
SpamAssassin version 3.4.2
running on Perl version 5.16.3
CentOS Linux release 7.6.1810 (Core)
x86_64
I see this error:
May 28 15:40:03 server spamd[17267]: spamd: error: addr is not
Hello, i updated perl via yum.
# spamassassin --version
SpamAssassin version 3.4.2
running on Perl version 5.16.3
CentOS Linux release 7.6.1810 (Core)
x86_64
I see this error:
May 28 15:40:03 server spamd[17267]: spamd: error: addr is not a string at
/usr/share/perl5/vendor_perl/IO/Socket
On Wed, May 15, 2019 at 4:29 PM Lucio wrote:
> Is there any configuration to have spamd log a particular message
> header long with the other informations it usually logs?
>
I've not seen that mentioned by anybody, but, you can always write a
filter that sits immediately downstrea
1 - 100 of 2459 matches
Mail list logo
