Re: Procmail Recipe Problem

2005-05-26 Thread Andy Jezierski

Jake Colman [EMAIL PROTECTED] wrote on 05/25/2005
10:12:08 PM:

[snip]

 How can I limit the number of sendmails anyway?
My server gets very
 overloaded in those circumstances. In general, what happens
if there are
 more sendmails than there are spamd processes?
 

You can try confCONNECTION_RATE_THROTTLE or confMAX_DAEMON_CHILDREN.
I believe that if sendmail doesn't get a response from your milter that
calls spamd within the timeout period you specifed when defining the milter
that it will bypass it, unless you told it to fail.

Andy

Re: Procmail Recipe Problem

2005-05-25 Thread Loren Wilton
 Clearly, some of my emails are skipping SA!

Which version were you running, again?  This was a known-to-happen 'feature'
with the 2.6x series, although nobody ever really figured out why.  There
are conditions where it can happen on 3.0.1 or .2, I believe, if the spamd
children all get themselves in a knot.  Spam processing stops and mail ends
up bypassing SA.  However, the 3.0.1-2 case should result in a lot of mail
bypassing SA, not just the occasional thing as on 2.6x.

Loren



Re: Procmail Recipe Problem

2005-05-25 Thread Jake Colman
 LW == Loren Wilton [EMAIL PROTECTED] writes:

Clearly, some of my emails are skipping SA!

   LW Which version were you running, again?  This was a known-to-happen
   LW 'feature' with the 2.6x series, although nobody ever really figured
   LW out why.  There are conditions where it can happen on 3.0.1 or .2, I
   LW believe, if the spamd children all get themselves in a knot.  Spam
   LW processing stops and mail ends up bypassing SA.  However, the 3.0.1-2
   LW case should result in a lot of mail bypassing SA, not just the
   LW occasional thing as on 2.6x.

Loren,

I think I already posted a reply to this email but I don't see it in the
list.  If this is a duplicate I apologize.

I am using SA 3.0.3.  What you are suggesting as the problem makes alot of
sense.  I usually see this happen when my server comes back on-line after
being off-line for a while.  When that happens, my server gets very
overloaded as the backup MX dumps whatever it was holding.  I end up with
over a 100 sendmail processes running at the same time.

Maybe I need to reconfigure sendmail and/or spamd?  I limit spamd to 5 child
processes (I specify options -d -c -m4).  Maybe this is the problem?  Maybe
I need more spamd processes or fewer sendmail processes??

How can I limit the number of sendmails anyway?  My server gets very
overloaded in those circumstances.  In general, what happens if there are
more sendmails than there are spamd processes?

Thanks for your help!

...Jake

-- 
Jake Colman
Sr. Applications Developer
Principia Partners LLC
Harborside Financial Center
1001 Plaza Two
Jersey City, NJ 07311
(201) 209-2467
www.principiapartners.com



Re: PRocmail recipe problem and spamassassin not filtering correctly

2004-11-04 Thread Matt Kettler


At 10:53 AM 11/4/2004, [EMAIL PROTECTED] wrote:
I use spamassassin 2.63 on fedora
core 2.
I have two problems :
1. Spamassassin does not flag all spam, although muy level is at 3.
Sometimes he
doesn't even have ONE hit on a spam message !!!.
You're running a rather old version of SA, one which is vulnerable to a
malformed message causing denial of service.
If you can't upgrade to 3.x, at minumum upgrade to 2.64.
As for accuracy:
1)
Consider installing Net::DNS so SA can query RBLs.
(this
is just done with CPAN, or a distribution package)
2)
Consider adding DCC or Razor
http://www.rhyolite.com/anti-spam/dcc/
http://razor.sourceforge.net/
3) if
you're on 2.6x consider adding antidrug.cf (built in on 3.x)
http://mywebpages.comcast.net/mkettler/sa/antidrug.cf
(just
wget it into /etc/mail/spamassassin and restart spamd)
4) if
you're on 2.6x consider adding the surbl.org plugin (similar code built
in on 3.x)
http://sourceforge.net/projects/spamcopuri/
5) if you
can keep up on training, consider setting up bayes.

2. I want to move the spam messages
to a specific folder, how to do that ?. 
Procmail rules. See the example at:
http://wiki.apache.org/spamassassin/UsedViaProcmail?action="">
Which moves mail to almost-certainly-spam and
probably-spam mailboxes automaticaly.





Re: PRocmail recipe problem and spamassassin not filtering correctly

2004-11-04 Thread Greg Ennis
On Thu, 2004-11-04 at 09:53, [EMAIL PROTECTED] wrote:
 Hi all,
 
 I use spamassassin 2.63 on fedora core 2.
 I have two problems :
 
 1. Spamassassin does not flag all spam, although muy level is at 3. Sometimes 
 he
 doesn't even have ONE hit on a spam message !!!.
 
 2. I want to move the spam messages to a specific folder, how to do that ?.
 
 
 My procmail.log says :
 
 ==
 From [EMAIL PROTECTED]  Thu Nov  4 09:57:10 2004
  Subject: A SPECIFIC SUBJECT
   Folder: /var/spool/mail/THE USER'S LOGIN
 procmail: Incomplete recipe
 ==
 
 
 My local.cf in spamassassin folder is like this :
 ==
 rewrite_subject 1
 subject_tag [*ATTENTION SPAM*]
 report_safe 0
 
 use_bayes 1
 auto_learn 1
 
 # Spam domains
 
 blacklist_from [EMAIL PROTECTED]
 blacklist_from [EMAIL PROTECTED]
 blacklist_from [EMAIL PROTECTED]
 blacklist_from [EMAIL PROTECTED]
 blacklist_from [EMAIL PROTECTED]
 blacklist_from [EMAIL PROTECTED]
 
 ==
 
 Here is my procmailrc file :
 
 ==
 LOGFILE=/var/log/procmail.log
 
 :0 fw
 *  256000
 | /usr/bin/spamc -f
 
 :0:
 * ^X-Spam-Level: \*\*\*
 
 ==
 Can someone help me out ?.
 
 
 /hitete

I have been doing this and it works like a charm even with 2.63.  I
would advise you to use 3.0.1 it is much much faster.  Some things you
need to consider are the following:

1. When you set up your local.cf file you must rewrite the Subject line
to identify the message as spam.  

In the SA 3.0.1 local.cf file Located in /etc/mail/spamassassin/ I use
the following two lines  (check the syntax in 2.63 becuase it is a
little differnt)

required_hits 5
rewrite_header Subject [SPAM]


In the /etc/procmailrc file I use the following entries:

MAILDIRLOG=/smile$HOME/Mail
DROPPRIVS=YES

:0fw
 *  256000
 | spamc

 # This routine will dump your spam
 :0 H
 * ^Subject:.*\[SPAM\]
 $MAILDIRLOG/spam.log

Please note that the directory you want to save the spam in must have
proper user protections and you must drop to user privileges within
procmail before you activate spamc. spamc of course requires the use of
the spamd daemon.

These suggestions are basic things for most on this list, but if you are
new to using these tools it will save you some look up and experimenting
time.

Good Luck!!!

Greg