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-spamd"
Matus UHLAR - fantomas skrev den 2023-10-31 11:48:
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 --hel
> 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-spamd"
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, falling back to nobody"
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 am not sure w
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 with -u,
>
> 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
On 2023-07-07 at 12:08:22 UTC-0400 (Fri, 7 Jul 2023 09:08:22 -0700
(PDT))
Richard Troy
is rumored to have said:
Hi All,
I changed the subject line to hopefully get some insight from a wider
audience regarding this situation that Reindl uncovered:
It should be noted that Harald Reindl is no
Check the systemd unit file. It should set the user the service runs as.
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, skippi
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/spamassassin/local.c
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::SpamAssassin::Plugin::UR
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 and does not appea
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 the date of any
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 case, the message size is
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 reaches the limit of 300+ seconds. In
> this part
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
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 they are. And when
> > they're all busy, nothing works anymore.
>
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.
On Thu, 30 May 2019 22:40:22 +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 they are. And when
> > they're all busy, nothing works anymore.
>
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 maximum CPU usage several
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 another thread
here a
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 "spamd child" wi
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?
This will *
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 a
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 downstream of spamc and l
Even I am new, check if this works.
Go to /etc/default/spamassassin and change the following,
OPTIONS="--create-prefs --max-children 2 --username spamd \-H ${SAHOME} -s
${SAHOME}spamd.log"
(This specifies the username Spamassassin will run under as spamd, as well
as add the home directory, create
On 14 May 2019, at 07:52, Emanuel Gonzalez wrote:
> [root@server ~] # spamassassin --version
> SpamAssassin version 3.4.1
> running on Perl version 5.10.1
5.10? Isn't that like... 15 years old? Definitely at least 10.
So I don't think perl updates is your problem.
--
My little brother got hi
On 1/10/2019 6:03 PM, David Gibbs wrote:
I'm trying to get spamd to log to my maillog but can't figure out
what's going wrong. Jan 10 17:43:01 listmail spamd[21503]: logger:
removing stderr method
I tried changing the syslog facility on spamd to local1 and the same
thing happened, expect the one
On 1/10/19 6:03 PM, David Gibbs wrote:
I'm trying to get spamd to log to my maillog but can't figure out what's
going wrong.
Also, spamd is logging oddly even in the messages file...
Jan 10 18:11:32 listmail spamd[21867]: logger: removing stderr method
Jan 10 18:11:33 listmail check[21869]: sp
On Tue, 30 Oct 2018, RW wrote:
On Tue, 30 Oct 2018 17:27:18 +0200
Jari Fredriksson wrote:
John Hardin kirjoitti 24.10.2018 kello 18.10:
As was suggested earlier, disable auto-expiry and run a cron job to
expire Bayes tokens.
I seem to have auto expiry on, but have not seen any problems
On Tue, 30 Oct 2018 17:27:18 +0200
Jari Fredriksson wrote:
> > John Hardin kirjoitti 24.10.2018 kello 18.10:
> > As was suggested earlier, disable auto-expiry and run a cron job to
> > expire Bayes tokens.
>
>
> I seem to have auto expiry on, but have not seen any problems with it.
Expiry wi
> John Hardin kirjoitti 24.10.2018 kello 18.10:
>
> 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
>>
On Mon, 29 Oct 2018, Emanuel Gonzalez wrote:
Hi.!!
the permits of the directory are correct:
ll -d /.spamassassin/
drwxrwxr-x 2 nobody nobody 63 oct 29 08:54 /.spamassassin/
The parameter bayes_auto_learn is set to "0".
The advice was for auto *expire*.
--
John Hardin KA7OHZ
Hi.!!
the permits of the directory are correct:
ll -d /.spamassassin/
drwxrwxr-x 2 nobody nobody 63 oct 29 08:54 /.spamassassin/
The parameter bayes_auto_learn is set to "0".
any ideas?
Regards,
Emanuel.
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:
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
On Tue, 23 Oct 2018, RW wrote:
On Tue, 23 Oct 2018 18:16:51 +
Emanuel Gonzalez wrote:
Hello,
I have a problem with the /.spamassassin/bayes.lock
I see this error:
Oct 23 15:12:14 server spamd[18073]: bayes: cannot open bayes
databases /.spamassassin/bayes_* R/W: lock failed: File exists
On Tue, 23 Oct 2018 18:16:51 +
Emanuel Gonzalez wrote:
> Hello,
>
> I have a problem with the /.spamassassin/bayes.lock
>
> I see this error:
>
> 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
On 28 Nov 2017, at 12:15, Colony.three wrote:
[...]
My God. It's full of stars!
This fixed the spamass-milter problem. And it seems to be the correct
way to fix the hundreds of other SELinux errors I have.
You take this box, and put it through a magic tunnel and see if it
looks right. If
>> First, copy and paste lines from the log into a file called thing0.log where
>> thing is a mnemonic name for what you're trying to enable. In this example,
>> thing is smartd
>>
>> root# cd; mkdir selinux; cd selinux
>> root# cat > smartd0.log
>> type=AVC msg=audit(1425551687.181:491): avc: de
>> On 11/27/2017 10:34 PM, Colony.three wrote:
>>
ExecStartPre=/bin/chown -R spamd:spamd /run/spamassassin
There's a root exploit for the "spamd" user in that last line. Assuming
you got the tmpfiles.d thing working, you should delete those
ExecStartPre commands.
>>>
>>> Ca
On 11/27/2017 10:34 PM, Colony.three wrote:
ExecStartPre=/bin/chown -R spamd:spamd /run/spamassassin
There's a root exploit for the "spamd" user in that last line. Assuming
you got the tmpfiles.d thing working, you should delete those
ExecStartPre commands.
Can you explain further please?
On 11/27/2017 10:34 PM, Colony.three wrote:
>> ExecStartPre=/bin/chown -R spamd:spamd /run/spamassassin
>>
>> There's a root exploit for the "spamd" user in that last line. Assuming
>> you got the tmpfiles.d thing working, you should delete those
>> ExecStartPre commands.
>
> Can you explain f
>I am really trying to not turn off SELinux with this server, and only have
>this one showstopper error. But I don't know what to do with this gibberish:
Here's an extract from a page I wrote about SELinux (not currently published,
or I could just send you the link).
--->8---
This is where it
On 27 Nov 2017, at 22:45 (-0500), Colony.three wrote:
>> Is anyone using the unix:socket for spamaassassin's milter?
>> When I turned on SELinux, it will not let me change the group of the
>> spamass-milter socket. (/run/spamass-milter/postfix/sock)
>> /var/log/messages
>> spamass-milter: group op
On 27 Nov 2017, at 22:45 (-0500), Colony.three wrote:
Is anyone using the unix:socket for spamaassassin's milter?
When I turned on SELinux, it will not let me change the group of the
spamass-milter socket. (/run/spamass-milter/postfix/sock)
/var/log/messages
spamass-milter: group option, cho
Is anyone using the unix:socket for spamaassassin's milter?
When I turned on SELinux, it will not let me change the group of the
spamass-milter socket. (/run/spamass-milter/postfix/sock)
/var/log/messages
spamass-milter: group option, chown: Operation not permitted
G**gle's baffled how to set S
On 11/27/2017 11:53 AM, Colony.three wrote:
>> It simply would not create /run/spamassassin directory on boot. It is
>> supposed to create it automatically like clamd does, since /run is wiped
>> at each boot. To make it work I finally had to add:
>> ExecStartPre=/usr/bin/mkdir /run/spamassassin
On 11/27/2017 11:53 AM, Colony.three wrote:
>
> It simply would not create /run/spamassassin directory on boot. It is
> supposed to create it automatically like clamd does, since /run is wiped
> at each boot. To make it work I finally had to add:
> ExecStartPre=/usr/bin/mkdir /run/spamassassin
>
On Mon, 27 Nov 2017, sha...@shanew.net wrote:
I wonder if it's worth adding a note to the wiki, or even the
--socketpath section of the spamd man-page?
*That* would be something the SA team *could* do...
I'd be happy to do the commit if someone could provide some text.
On Mon, 27 Nov 2017,
> sha...@shanew.net kirjoitti 27.11.2017 kello 20.32:
>
> or what it's worth, there's no
> tmpfiles.d entry on my Ubuntu or Gentoo systems (Gentoo does its
> thing in the init script).
Debian (well, Raspbian for me) does have it. Apparently Ubuntu has removed it!
signature.asc
Description:
tmpfiles.d became a thing when /run became a temporary filesystem, so
it is relatively new. And most of the time packages install the
necessary files in /usr/lib/tmpfiles.d, so admins may have never run up
against this issue since it became a thing.
As John says, you can file a bug report with R
On Mon, 27 Nov 2017, Colony.three wrote:
I suspect you need an entry in /etc/tmpfiles.d so that directory gets
created at boot time.
Indeed there is no tmpfiles in the spamassassin package. (I've never heard of
this in 22 years) How can this be, in the 21st Century? As I'd suspected,
every
I suspect you need an entry in /etc/tmpfiles.d so that directory gets
> created at boot time.
>
> Google tmpfiles.d or see this redhat blog page:
> https://developers.redhat.com/blog/2016/09/20/managing-temporary-files-with-systemd-tmpfiles-on-rhel7/
Indeed there is no tmpfiles in the spamassassi
I suspect you need an entry in /etc/tmpfiles.d so that directory gets
created at boot time.
Google tmpfiles.d or see this redhat blog page:
https://developers.redhat.com/blog/2016/09/20/managing-temporary-files-with-systemd-tmpfiles-on-rhel7/
On Mon, 27 Nov 2017, Colony.three wrote:
I have fo
On 2017-01-06 16:02, Bowie Bailey wrote:
On 1/6/2017 7:07 AM, R wrote:
OPTIONS="-u spamass-milter -x -e mydomain.com -i 127.0.0.1"
Jan 6 11:23:39 mail spamd[18251]: spamd: using default config for
spamass-milter: /var/vmail///.spamassassin/user_prefs
Jan 6 11:23:39 mail spamd[18251]: spamd:
On Fri, 6 Jan 2017 10:02:20 -0500
Bowie Bailey wrote:
> I don't use spamass-milter, but I would guess that the -x option may
> require some extra configuration.
>
According to the man page it uses sendmail -bv to perform the
translation. It also has a "Recipient processing" debug flag.
On 1/6/2017 11:06 AM, R wrote:
thank you for highlighting that... I've always tried to fix this
trying to make spamassassin "alias aware". I'll try instead to just
pass the intended mailbox name to spamc.
Excluding the spamassassin word from my online researches finally I've
started finding p
On 01/06/2017 05:06 PM, R wrote:
Perhaps I just need to remove/replace spamass-milter,
If you're using Postfix I can recommend Fuglu (https://fuglu.org) in pre
queue mode.
lightweight, very well documented and has been rock solid.
Axb
Hi Kevin,
thank you for highlighting that... I've always tried to fix this trying
to make spamassassin "alias aware". I'll try instead to just pass the
intended mailbox name to spamc.
Excluding the spamassassin word from my online researches finally I've
started finding people with the same
On 1/6/2017 7:07 AM, R wrote:
Hello all,
I'm running a mail server with this setup: Debian based postfix +
spamassassin (called using spamass-milter) and I have a config problem
I cannot fix by myself...
All the users are virtual users (using a sql database) and both
delivery and per-user
On 1/6/2017 7:07 AM, R wrote:
Hello all,
I'm running a mail server with this setup: Debian based postfix +
spamassassin (called using spamass-milter) and I have a config problem
I cannot fix by myself...
SpamAss-milter, known as the glue, is not an Apache SpamAssassin product.
Someone here
Am 27.07.2016 um 15:08 schrieb Reindl Harald:
Am 27.07.2016 um 12:00 schrieb Reindl Harald:
Am 11.07.2016 um 13:47 schrieb Axb:
Bug 7156
Bug 7104
Bug 6896
on Fedora 24 when that happens at the same time error like below appear
in the maillog (perl-5.22.2-361.fc24.x86_64)
maybe better in
Am 27.07.2016 um 12:00 schrieb Reindl Harald:
Am 11.07.2016 um 13:47 schrieb Axb:
Bug 7156
Bug 7104
Bug 6896
on Fedora 24 when that happens at the same time error like below appear
in the maillog (perl-5.22.2-361.fc24.x86_64)
maybe better in context here:
Jul 27 13:43:12 mail-gw spamd[93
Am 11.07.2016 um 13:47 schrieb Axb:
Bug 7156
Bug 7104
Bug 6896
on Fedora 24 when that happens at the same time error like below appear
in the maillog (perl-5.22.2-361.fc24.x86_64)
**Unmatched Entries**
Use of uninitialized value $2 in concatenation (.) or string at
/usr/share/perl5
I also block all top, win, science and some other spammy TLDs that
provide free one day trial registrations. All such mail goes to a
folder that I review periodically and so far, I have not seen any
false positives.
I also have an imperfect perl script that determines age of a domain,
and flags a
Bug 7156
Bug 7104
Bug 6896
On 07/11/2016 01:42 PM, Jari Fredriksson wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Reindl Harald kirjoitti 11.7.2016 14:34:
Am 11.07.2016 um 13:27 schrieb Jari Fredriksson:
Reindl Harald kirjoitti 11.7.2016 11:52:
Am 11.07.2016 um 10:02 schrieb Jari
On Sun, 10 Jul 2016 17:08:32 +0200
Reindl Harald wrote:
> Jul 8 10:00:40 mail-gw spamd[14221]: dns: new_dns_packet
> (domain=www..windstrom.at. type=A class=IN) failed: a domain name
> contains a null label
>
> i guess that was a typo in the mail itself - shouldn't SA replace
> such accidents
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Reindl Harald kirjoitti 11.7.2016 14:34:
> Am 11.07.2016 um 13:27 schrieb Jari Fredriksson:
>> Reindl Harald kirjoitti 11.7.2016 11:52:
>>> Am 11.07.2016 um 10:02 schrieb Jari Fredriksson:
Define correctly, please.
>>
>>> "www..windstrom.at" is o
Am 11.07.2016 um 13:27 schrieb Jari Fredriksson:
Reindl Harald kirjoitti 11.7.2016 11:52:
Am 11.07.2016 um 10:02 schrieb Jari Fredriksson:
Define correctly, please.
"www..windstrom.at" is obvious wrong and was meant as
"www.windstrom.at", so fix that typo in the background or just ignore
t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Reindl Harald kirjoitti 11.7.2016 11:52:
> Am 11.07.2016 um 10:02 schrieb Jari Fredriksson:
>> Define correctly, please.
>
> "www..windstrom.at" is obvious wrong and was meant as
> "www.windstrom.at", so fix that typo in the background or just ignore
Am 11.07.2016 um 10:02 schrieb Jari Fredriksson:
Define correctly, please.
"www..windstrom.at" is obvious wrong and was meant as
"www.windstrom.at", so fix that typo in the background or just ignore
the url at all since it CAN NOT become a positive dns response
10. heinäkuuta 2016 18.08.
Define correctly, please.
10. heinäkuuta 2016 18.08.32 GMT+03:00 Reindl Harald
kirjoitti:
>Jul 8 10:00:40 mail-gw spamd[14221]: dns: new_dns_packet
>(domain=www..windstrom.at. type=A class=IN) failed: a domain name
>contains a null label
>
>i guess that was a typo in the mail itself - shouldn
'Content-length' needs to be 'Content-Length'
are you kidding me?
/**
* Scan RAW-Message with spamd
*
* @param string $socket_path spamd-socket
* @param string $eml_path sample-file
* @param boolean $bayes_only only return bayes-classification
('BAYES_00', 'BAYES_05'...)
On Mar 29, 2016, at 10:41 AM, Daniel J. Luke wrote:
> On Mar 28, 2016, at 8:57 PM, Bill Cole
> wrote:
>> On 28 Mar 2016, at 14:42, Daniel J. Luke wrote:
>>> On Mar 24, 2016, at 12:10 PM, Daniel J. Luke wrote:
/usr/bin/time spamassassin < spam.msg
7.92 real 1.85 user
On Mar 28, 2016, at 8:57 PM, Bill Cole
wrote:
> On 28 Mar 2016, at 14:42, Daniel J. Luke wrote:
>> On Mar 24, 2016, at 12:10 PM, Daniel J. Luke wrote:
>>> /usr/bin/time spamassassin < spam.msg
>>> 7.92 real 1.85 user 0.13 sys
>>>
>>> /usr/bin/time spamc -U /var/run/spamd.s
On 28 Mar 2016, at 14:42, Daniel J. Luke wrote:
On Mar 24, 2016, at 12:10 PM, Daniel J. Luke
wrote:
/usr/bin/time spamassassin < spam.msg
7.92 real 1.85 user 0.13 sys
/usr/bin/time spamc -U /var/run/spamd.sock < spam.msg
126.44 real 0.00 user 0.00 sy
On Mar 24, 2016, at 12:10 PM, Daniel J. Luke wrote:
> /usr/bin/time spamassassin < spam.msg
>7.92 real 1.85 user 0.13 sys
>
> /usr/bin/time spamc -U /var/run/spamd.sock < spam.msg
> 126.44 real 0.00 user 0.00 sys
well, it looks like it's DNS related,
On 6/19/2015 2:31 PM, Nick Gill wrote:
Greetings,
spamd is using 100% CPU on my RaspberryPi 2 B, even though there is no
email coming in. Each process only runs 10 seconds or so, but then a
new one starts. (I have m set to 1)
I tried some of the tips on the site, ran sa-compile and disable
On Sat Jun 20 13:11:18 2015, RW wrote:
> The error is about a missing virtual user. Is "spamass-milter" perhaps a
> default virtual user used when an email has multiple recipients?
This email was sent to an unique recipient and ala...@gozmail.net is a
valid virtual user ton the server.
--
alari
On Sat, 20 Jun 2015 12:11:56 +0200
alarig wrote:
> Hi,
>
> I installed a spamassassin instance on my email server, it works but I
> have a strange error on each email: ?spamd[12325]: spamd: handle_user
> unable to find user: 'spamass-milter'?
> My MTA is postfix and I use spamass-milter. This is
Am 26.12.2014 um 17:58 schrieb Mark Martinec:
http://www.gossamer-threads.com/lists/spamassassin/users/188895
Has anyone made any progress on this? Anyone found a workaround?
Yes, it's the same issue. The bug is in perl, fixed in 5.18 or later.
A minimal test program triggering the bug was p
Michael Grant wrote:
I'm getting this message in my mail.log:
spamd: spf: lookup failed: addr is not a string at
/usr/share/perl5/IO/Socket/IP.pm line 646.
I'm running debian stable with Spamassassin from backports:
SpamAssassin Server version 3.4.0
running on Perl 5.14.2
and libmail-dki
Am 26.12.2014 um 16:05 schrieb Michael Grant:
I'm getting this message in my mail.log:
spamd: spf: lookup failed: addr is not a string at
/usr/share/perl5/IO/Socket/IP.pm line 646.
I'm running debian stable with Spamassassin from backports:
SpamAssassin Server version 3.4.0
running on Perl
On 10.10.2014 3:35, LuKreme wrote:
> On Tuesday, October 7, 2014, 10:56:54 PM, LuKreme wrote:
> >>>
>> On 07 Oct 2014, at 11:45 , Jari Fredrisson wrote:
>>> > I ran sa-update & sa-compile.
> >>>
>> Should sa-compile be run after sa-update?
> >>>
Of course it should. I assumed && w
On 09 Oct 2014, at 18:35 , LuKreme wrote:
> No, that is not what it says.
>
> $ man 1 bash
> …
> The control operators && and || denote AND lists and OR lists,
> respectively. An AND list has the form
Sorry for duplicating other’s posts, I replied to the original message out of
the “replie
> On 08 Oct 2014, at 16:23 , Duane Hill wrote:
>
> On Wednesday, October 8, 2014, 3:11:06 PM, LuKreme wrote:
>
>>> On 08 Oct 2014, at 04:56 , Duane Hill wrote:
>>>
>>> On Tuesday, October 7, 2014, 10:56:54 PM, LuKreme wrote:
>>>
On 07 Oct 2014, at 11:45 , Jari Fredrisson wrote:
> I
On Thu, 2014-10-09 at 18:08 +0700, Olivier Nicole wrote:
> But you don't do a -lint before restarting SA: if an update was to break
> SA (like a big Perl syntax error in a rule, or you are working on a
> plugin on your production system, you feel safe because as long as you
> don't restart spamd, a
Martin,
> I do something similar on my SA rules development system (I also have SA
> installed on this laptop but it is normally not running, which has the
> side effect of disabling the standard Fedora sa-update cron job because
> this won't run sa-update if it can't find the spamd daemon). My mo
On Thu, 2014-10-09 at 11:50 +0700, Olivier Nicole wrote:
> Hi,
>
> > /usr/local/bin/sa-update && /usr/local/bin/sa-compile &&
> > /usr/local/etc/rc.d/sa-spamd restart
> >
> > the only time spamd would restart is if sa-update AND sa-compile were
> > successfully completed, correct?
>
Yes, tha
Hi,
> /usr/local/bin/sa-update && /usr/local/bin/sa-compile &&
> /usr/local/etc/rc.d/sa-spamd restart
>
> the only time spamd would restart is if sa-update AND sa-compile were
> successfully completed, correct?
Sorry for jumping in the conversation... I have solved that issue by
calling sa-u
On Wednesday, October 8, 2014, 6:31:08 PM, Martin confabulated:
> On Wed, 2014-10-08 at 16:46 -0600, Amir Caspi wrote:
>> On Oct 8, 2014, at 4:23 PM, Duane Hill wrote:
>> >
>> > No. && is a way of chaining commands together. Your cron says run
>> > sa-update and then restart spamd. In
1 - 100 of 952 matches
Mail list logo
