Hi Vincent,
> Are you running spamd/spamc as root? it is not recommended to run spamd
> as root.
I know, but so far I was too lazy setting it up to run as a user.
There are still some issues, e.g. when I start spamd with
use_auto_whitelist 1
and there is no file auto-whitelist yet, it is
> If you remember my log file, there were a bunch of days in a row with one
> to three of them, then three on April 8th, one on April 9th and none
> since then.
Well, it still could be some kind of watchdog that kills processes when
they use too much CPU or memory. That wouldn't happen on a regula
--- Andy Spiegl <[EMAIL PROTECTED]> wrote:
> Hi Jason,
>
> I found the cause: my stupidess DOH!
>
> I've got a cronjob that kills processes which have been hanging
> around for
> too long. Two days ago I reconfigured it and made a mistake which
> lead to
> exactly this: spamd with etime of mo
It doesn't seem excessive to me, though my whitelist is actually twice
this size. Here's my blacklist from local.cf:
blacklist_from *reunion.com [EMAIL PROTECTED] [EMAIL PROTECTED]
[EMAIL PROTECTED] [EMAIL PROTECTED]
blacklist_from *rm05.net *adm02.com [EMAIL PROTECTED]
[EMAIL PROTECTED] *agava.ne
Hi Jason,
I found the cause: my stupidess DOH!
I've got a cronjob that kills processes which have been hanging around for
too long. Two days ago I reconfigured it and made a mistake which lead to
exactly this: spamd with etime of more than 60 minutes are killed with
SIGTERM. This cronjob is re
--- Duane Hill <[EMAIL PROTECTED]> wrote:
> On Fri, 13 Apr 2007, J. wrote:
>
> > --- Andy Spiegl <[EMAIL PROTECTED]> wrote:
> >
> >> I seem to have the same problem!
> >>
> >> Yesterday I upgraded from 3.0 to 3.1
> >> (to be exact: 3.0.3-2sarge1 to 3.1.7-1~bpo.1 from Debian
> backports)
> >> an
J. wrote:
I got an obvious spam a little while ago that got scored
"X-Spam-Status: No, hits=? required=?" so I looked up the message in
the system log. Check out line 5 below (server killed by SIGTERM):
I had a similar issue caused by using a very large blacklist; I took out
the blacklist a
--- Andy Spiegl <[EMAIL PROTECTED]> wrote:
> > Someone here suggested that it's a memory problem.
> Where? I didn't see any reply to your post.
Sorry, it was on the Gentoo forum, not here. Here's the thread, not
much beyond what I mentioned though so not sure it will help:
http://forums.gentoo.
On Fri, 13 Apr 2007, Andy Spiegl wrote:
Someone here suggested that it's a memory problem.
Where? I didn't see any reply to your post.
Most of my machines have 1gig RAM. That should be enough for the 5
SA-children I thought...
The rate that it's occuring for you might support that if you h
On Fri, 13 Apr 2007, J. wrote:
--- Andy Spiegl <[EMAIL PROTECTED]> wrote:
I seem to have the same problem!
Yesterday I upgraded from 3.0 to 3.1
(to be exact: 3.0.3-2sarge1 to 3.1.7-1~bpo.1 from Debian backports)
and now ALL spamds terminate after a while. And I have no clue why!
The worst
> Someone here suggested that it's a memory problem.
Where? I didn't see any reply to your post.
Most of my machines have 1gig RAM. That should be enough for the 5
SA-children I thought...
> The rate that it's occuring for you might support that if you handle a
> lot of users.
Yes, but my setup
--- Andy Spiegl <[EMAIL PROTECTED]> wrote:
> I seem to have the same problem!
>
> Yesterday I upgraded from 3.0 to 3.1
> (to be exact: 3.0.3-2sarge1 to 3.1.7-1~bpo.1 from Debian backports)
> and now ALL spamds terminate after a while. And I have no clue why!
>
> The worst part is that spamc re
I seem to have the same problem!
Yesterday I upgraded from 3.0 to 3.1
(to be exact: 3.0.3-2sarge1 to 3.1.7-1~bpo.1 from Debian backports)
and now ALL spamds terminate after a while. And I have no clue why!
The worst part is that spamc returns the messages unprocessed if it cannot
connect to spa
13 matches
Mail list logo
