md.pid -s mail --syslog-socket=inet --username=nobody --local
Is there something I'm missing? I've previously reported this same issue,
and things were modified.. I haven't retested until now, with version
2.55, and stuff still appears to be the same.
Please let me know if I&
Make test for 2.50 CVS has been failing for me, for the last few
days. Have others encountered this?
Freebsd 4.7, Perl 5.8.0
--Tomki
---
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See
Jonathan,
I don't know the answer to #1, but for #2 you should go here:
http://www.uwasa.fi/~ts/info/proctips.html for the answer, and more great
education on procmail.
--Tomki
At 12:36 AM 1/8/2003 +, you wrote:
1) How can I check to see if RBL checks are actually being made on my
s
The issue appears to also have been resolved for FreeBSD 4.7, which is the
OS where I have been experiencing this problem.
Thanks!!!
--Tomki
At 12:15 12/29/2002 +0100, Stefan Seiz wrote:
On 28.12.2002 1:00 Uhr, Justin Mason <[EMAIL PROTECTED]> wrote:
>> Even so I run it with t
(perl5.8.0)
brandon-1917 19239
10.0 0.0 00 ?? Z 4:26PM 0:00.00 (perl5.8.0)
brandon-1917 19926 8.0 0.0 00 ?? Z 4:30PM 0:00.00
(perl5.8.0)
eplatt-0178 19958 6.0 0.0 00 ?? Z 4:30PM 0:00.00
(perl5.8.0)
tomki-017818845 5.0 0.0 00 ?? Z
At least, not as advertised
I have set up 2 spamd servers, and I have spamc being used from my
.procmailrc like so:
spamc -d spamd.alink.net -f
However... when I shut down the spamd on one, there are failures
connecting to both.. is this a known bug, or have I overlooked something
somewhere i
At least, not as advertised
I have set up 2 spamd servers, and I have spamc being used from my
.procmailrc like so:
spamc -d spamd.alink.net -f
However... when I shut down the spamd on one, there are failures
connecting to both.. is this a known bug, or have I overlooked something
somewhere i
At 21:46 12/05/2002 -0500, Theo Van Dinter wrote:
On Thu, Dec 05, 2002 at 05:51:46PM -0800, Tomki wrote:
> That's the list of hits that you got when you tested that email?
Yep.
> I don't see the score you got.
Well, I see you're using 2.50 ... Did you install 2.50 or
their
settings... so of course the best thing would be for the default rules to
catch spam as well as yours seems to indicate.
Something I'm missing?
--Tomki
At 19:51 12/05/2002 -0500, Theo Van Dinter wrote:
On Thu, Dec 05, 2002 at 04:16:08PM -0800, Tomki wrote:
> It's getting pretty bad
It's getting pretty bad... still a lot better than with anything else in
my experience, granted, but the number of false negatives really is rising.
This example is a prime example, and really pretty amazing in the score:
Received: from spoon.alink.net (spoon.sv-server1.alink.net [207.135.64.
ike to allow from more
than 1.
Version 2.50 CVS, today's.
--Tomki
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Spamassassin-talk m
http://www.spamassassin.org/dist/
Changes file is dated 13 Nov.
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Spamassassin-talk mailing list
[EMA
's an irritant:
gets all the load averages to about 1.8.
--Tomki
At 11:00 11/19/2002 +0800, Glynn S. Condez wrote:
From: "Tomki" <[EMAIL PROTECTED]>
> Glynn,
>From my experience, spamd occasionally dies under a fairly light
> load. then when spamc attempts to m
; make start' (I've hacked the sendmail Makefile to
stop/start spamd)
--Tomki
At 10:58 11/18/2002 +0800, Glynn S. Condez wrote:
All,
My spamassassin dies last November 15, 2002.
Im using spamassassin-2.31 and got this bunch of message in my syslog and
lots of procmail and spamd in the p
ditto for today's build, 11-15
At 12:27 11/14/2002 -0800, Tomki wrote:
Today's build has the same problem. A new zombie for each message processed.
'ps -auxw |grep perl |sort |cat -n' currently shows 95 zombies for
different users.
--Tomki
At 12:00 11/14/2002 -0800, To
Today's build has the same problem. A new zombie for each message processed.
'ps -auxw |grep perl |sort |cat -n' currently shows 95 zombies for
different users.
--Tomki
At 12:00 11/14/2002 -0800, Tomki wrote:
The spamd perl process from spamassassin 2.50 CVS I got yesterday (1
The spamd perl process from spamassassin 2.50 CVS I got yesterday (11-13)
seems to spawn lots of zombie processes.
I'll try today's build.
At 13:02 11/14/2002 +, Justin Mason wrote:
Tomki said:
> I'll give it a shot right away, thanks!
BTW -- the people who are using thi
I'll give it a shot right away, thanks!
--Tomki
At 11:47 11/13/2002 +, Justin Mason wrote:
Tomki said:
> Although there has been no talk of a solution, there continue to be people
> who experience the problem of spamd dying.
> The experience of someone else on this list poi
ng in fast enough for btwn 3 and 10 mails to bounce
before supervise manages to restart spamd.
Is there any work being done on this problem?
Is there a denial that this problem exists with the software?
Thanks
--Tomki Camp
---
This sf.ne
nt for the current user base is fairly high)
--Tomki
At 23:52 10/11/2002 -0500, Mike Burger wrote:
Given that sendmail, these days, comes configured by default to already
use procmail as the local delivery agent, try removing your .forward
files, and see if it works.
On Fri, 11 Oct 2002, Tomki wrote:
nt for the current user base is fairly high)
--Tomki
At 23:52 10/11/2002 -0500, Mike Burger wrote:
Given that sendmail, these days, comes configured by default to already
use procmail as the local delivery agent, try removing your .forward
files, and see if it works.
On Fri, 11 Oct 2002, Tomki wrote:
each of THOSE emails ALSO
generate failure messages to postmaster.. so the cycle continues.
"We don't die, we MULTIPLY!!".. so I can fix that looping bit by taking
[EMAIL PROTECTED] into its own mailbox, but it still doesn't
tell me what the root problem is: spamd dies occ
1. 'touch ~/pm.log'
2. Put this at the top of your .procmailrc:
LOGFILE = $HOME/pm.log
LOGABSTRACT = "all"
VERBOSE = "on"
That will log relevant information about what procmail is doing with your
email. :-) Can be quite useful.
--Tomki
At 13:25 10/0
e target server (the only one currently
running spamc/d) fails again, beginning the process anew.
Any other suggestions as to what might be causing this problem?
Thanks
--Tomki
X-Persona:
Received: from spoon.alink.net (spoon.sv-server1.alink.net [207.135.64.249])
by lonestar.alink.net
If this were the issue wouldn't I have the problem at hand constantly,
instead of randomly as I appear to? For instance, I didn't change any
configurations at all after my problem this morning, I just cleaned the
queues and restarted spamd/sendmail.
At 14:06 09/29/2002 -0400, Theo Van Dinter
but it didn't seem to help.
Sendmail is 8.12.5.
Thanks for any help.
---Tomki
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Spamassassin-talk ma
26 matches
Mail list logo
