On Tue, 2010-04-27 at 13:43 -0700, PaulYo wrote:
> We are experiencing a sporadic error running SA 3.3.1 on an Ubuntu distro,
> with the following behavior: a message is being processed and a spamd child
> dies allowing the spam message to go through to the qmail queue. [...]
> required_hits 2
T
AIL PROTECTED]
> Sent: Friday, May 12, 2006 11:42 AM
> To: users@spamassassin.apache.org
> Subject: Re: Spamd Children
>
> From: "Steven Stern" <[EMAIL PROTECTED]>
>
> > Please don't top post and reply to the list. Thanks.
>
> Please don't
From: "Steven Stern" <[EMAIL PROTECTED]>
Please don't top post and reply to the list. Thanks.
Please don't be anal retentive, Steve. You're human. You can adapt.
Or should I start advocating side posting?
{^_^}
Sorry for not replying to all, forgot.
Thank you for the help! Someday ill remember it!
on 5/12/06 8:53 AM, Steven Stern at [EMAIL PROTECTED] wrote:
> [EMAIL PROTECTED] wrote:
>> Doh, no...can you point me in the direction of how to do that?
>>
>>
>>
>> on 5/12/06 8:23 AM, Steven Stern at
[EMAIL PROTECTED] wrote:
> Doh, no...can you point me in the direction of how to do that?
>
>
>
> on 5/12/06 8:23 AM, Steven Stern at [EMAIL PROTECTED] wrote:
>
>> [EMAIL PROTECTED] wrote:
>>> Ok, fair enough...i downloaded and ran
>>>
>>> rpmbuild -tb Mail-SpamAssassin-3.1.1.tar.gz
>>>
>>> As
[EMAIL PROTECTED] wrote:
> Ok, fair enough...i downloaded and ran
>
> rpmbuild -tb Mail-SpamAssassin-3.1.1.tar.gz
>
> As descibed on the site. I don't see any changes in the version number, is
> there more I have to do ?
>
>
That just creates the RPM files in /usr/src/redhat/RPMS. Did you inst
Ok, fair enough...i downloaded and ran
rpmbuild -tb Mail-SpamAssassin-3.1.1.tar.gz
As descibed on the site. I don't see any changes in the version number, is
there more I have to do ?
on 5/11/06 12:41 PM, Daryl C. W. O'Shea at [EMAIL PROTECTED] wrote:
> The Help Guy wrote:
>> hello all:
>>
The Help Guy wrote:
hello all:
You've been very helpful in the past, so let me say thank you to start.
Im currently using SA 3.1.0 on Linux with procmail.
I have a problem that is pretty much exactly described in this bug report:
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4410
Afte
Craig Green wrote:
Scott Russell wrote:
Greets.
Running SA 3.1.0 with spamc/spamd on RHEL4 i386. I have the following
options for my spamd: -d --allow-tell --max-children=30
--min-children=10 --min-spare=3 --max-spare=6 -q -x -u spamd
Today I saw the following error in /var/log/maillog:
s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
all this info is useful on the bug, not on this side discussion.
- --j.
Craig McLean writes:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> FWIW I *don't* see this issue on FBSD 5.2.1 running SA 3.0.4 with perl 5.6.1
>
> Craig.
>
> Justin
I've been running spamc and spamd (3.0.4) on FreeBSD 4.10 with Perl 5.8.5
for quite a while, but using the -u vmail flag doesn't cause any problems.
vmail 15329 0.0 2.9 59052 30300 ?? INsJ 5:55AM 0:03.05
/usr/local/bin/spamd -x -d -m 2 -r /var/run/spamd/spamd.pid -u vmail
--socketpath=/t
On Tue, 9 Aug 2005, Craig McLean wrote:
I applied the patch, and it fixed things on my end. I noted in my PR that
it was also odd to me that before, the children showed in ps as "perl" and
afterwards as "perl5.8.6" or something very similar.
FWIW I *don't* see this issue on FBSD 5.2.1 runni
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
FWIW I *don't* see this issue on FBSD 5.2.1 running SA 3.0.4 with perl 5.6.1
Craig.
Justin Mason wrote:
>
> ah, good to hear -- although it would have been nice to have had that
noted on bug 3900, which was still listed as "awaiting confirmation"...
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
ah, good to hear -- although it would have been nice to have had that
noted on bug 3900, which was still listed as "awaiting confirmation"...
- --j.
Charles Sprickman writes:
> I've seen this problem as well, even in the latest "ports" version. Sti
I've seen this problem as well, even in the latest "ports" version. Still
runs as root. If I apply the attached patch (obtained from one of the
bugzilla entries), it works properly. Running FBSD 4.11 w/perl 5.6.2
(5.8.7 had the same problem, I backed out of 5.8 since it chewed up more
memory
On Tue, 26 Apr 2005, Justin Mason wrote:
It's specifically a problem with perl on *BSD platforms -- there's
a bug open about it, but it's stalled because we don't have any
developers with BSD machines ;)
Anyone want a test machine where this is occurring? Where it DIDN'T occur
before under
>...
>
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA1
>
>
>It's specifically a problem with perl on *BSD platforms -- there's
>a bug open about it, but it's stalled because we don't have any
>developers with BSD machines ;)
>
>at least on some platforms (MacOS X) it appears perl's setuid
>support
Hello!
s/ignored/missed/ ;) that does look logical. I'd appreciate if
other *BSD users could try that out...
- --j.
It works on my end; thanks.
Me too, FreeBSD 5.4S
-Brandon
With respect,
Boris
On Tue, 26 Apr 2005, Justin Mason wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Robert Blayzor writes:
Brandon Kuczenski wrote:
I've seen this question posted a couple times in the mailing list
archives (from October 2004) but no resolution. The question again:
I'm running SpamAssassin 3.0.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Robert Blayzor writes:
> Brandon Kuczenski wrote:
> > I've seen this question posted a couple times in the mailing list
> > archives (from October 2004) but no resolution. The question again:
> >
> > I'm running SpamAssassin 3.0.2 on FreeBSD 4.10 in
Brandon Kuczenski wrote:
> I've seen this question posted a couple times in the mailing list
> archives (from October 2004) but no resolution. The question again:
>
> I'm running SpamAssassin 3.0.2 on FreeBSD 4.10 in spamc/spamd format
> with the '-u spamd' flag. Problem is, all the child proces
Justin Mason wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It's specifically a problem with perl on *BSD platforms -- there's
a bug open about it, but it's stalled because we don't have any
developers with BSD machines ;)
at least on some platforms (MacOS X) it appears perl's setuid
support
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It's specifically a problem with perl on *BSD platforms -- there's
a bug open about it, but it's stalled because we don't have any
developers with BSD machines ;)
at least on some platforms (MacOS X) it appears perl's setuid
support substantially doe
Brandon Kuczenski wrote:
I've seen this question posted a couple times in the mailing list
archives (from October 2004) but no resolution. The question again:
I'm running SpamAssassin 3.0.2 on FreeBSD 4.10 in spamc/spamd format
with the '-u spamd' flag. Problem is, all the child processes are
Ernie Dunbar wrote:
I'm running Spamassassin v3.0.0 on FreeBSD 4.9-RELEASE, and I run spamd like
this:
/usr/local/bin/spamd -A 127.0.0.1 -L -x -u spamc -d -m 10
When I use `ps aux |grep spamd` I get this:
spamc 61970 0.5 3.9 21292 20032 ?? Is3:04PM 0:00.47
/usr/local/bin/spamd -A 12
[EMAIL PROTECTED] wrote:
Rick Macdougall wrote:
Is there maybe a way to work around it using
su -c "spamd -L -x -d -m 10" spamc
? Or does that stop binding, or children from propagating?
Hi,
That won't work since non-root users can't bind to ports below 1024.
What about
su -c "spamd -L -x -d -m
Ernie Dunbar wrote:
[EMAIL PROTECTED] wrote:
Ernie Dunbar wrote:
I'm running Spamassassin v3.0.0 on FreeBSD 4.9-RELEASE, and I
run spamd like this:
/usr/local/bin/spamd -A 127.0.0.1 -L -x -u spamc -d -m 10
Perhaps the -A and -u flags are mutually exclusive? Maybe binding to a
particular
interf
> Rick Macdougall wrote:
>> [EMAIL PROTECTED] wrote:
>>> Ernie Dunbar wrote:
>>> /usr/local/bin/spamd -A 127.0.0.1 -L -x -u spamc -d -m 10
>> The spamd children start out as the correct user
>> but over time (I'm assuming when max-connections are hit) the newly
>> spawned children are run as root
Rick Macdougall wrote:
> [EMAIL PROTECTED] wrote:
>> Ernie Dunbar wrote:
>> /usr/local/bin/spamd -A 127.0.0.1 -L -x -u spamc -d -m 10
> The spamd children start out as the correct user
> but over time (I'm assuming when max-connections are hit) the newly
> spawned children are run as root instead
> [EMAIL PROTECTED] wrote:
>> Ernie Dunbar wrote:
>>
>>>I'm running Spamassassin v3.0.0 on FreeBSD 4.9-RELEASE, and I
>>>run spamd like this:
>>>
>>>/usr/local/bin/spamd -A 127.0.0.1 -L -x -u spamc -d -m 10
>>
>>
>> Perhaps the -A and -u flags are mutually exclusive? Maybe binding to a
>> particu
[EMAIL PROTECTED] wrote:
Ernie Dunbar wrote:
I'm running Spamassassin v3.0.0 on FreeBSD 4.9-RELEASE, and I
run spamd like this:
/usr/local/bin/spamd -A 127.0.0.1 -L -x -u spamc -d -m 10
Perhaps the -A and -u flags are mutually exclusive? Maybe binding to a particular interface is a root-only kin
Ernie Dunbar wrote:
> I'm running Spamassassin v3.0.0 on FreeBSD 4.9-RELEASE, and I
> run spamd like this:
>
> /usr/local/bin/spamd -A 127.0.0.1 -L -x -u spamc -d -m 10
Perhaps the -A and -u flags are mutually exclusive? Maybe binding to a
particular interface is a root-only kind of thing. I b
Ernie Dunbar wrote:
I'm running Spamassassin v3.0.0 on FreeBSD 4.9-RELEASE, and I run spamd like
this:
/usr/local/bin/spamd -A 127.0.0.1 -L -x -u spamc -d -m 10
When I use `ps aux |grep spamd` I get this:
spamc 61970 0.5 3.9 21292 20032 ?? Is3:04PM 0:00.47
/usr/local/bin/spamd -A 1
33 matches
Mail list logo
