Steve,

FYI the file is /etc/procmailrc normally (no . on the front of the filename in 
/etc)

In answer to your question, what you'll want to do is have something 
like this at the top of your procmailrc file:

# First stop loops
:0
* ^[EMAIL PROTECTED]
{
   :0:
   /var/spool/mail/auto

   :0
   {
      EXITCODE=0
      HOST=
   }
}

That will match [EMAIL PROTECTED] on any of the various To,Cc,etc lines, then 
store those messages in /var/spool/mail/auto (you should deliver them where they 
need to go -- that's just an example), then it will exit procmail.  If there is 
no [EMAIL PROTECTED] in any of those lines, then it'll proceed with the rest of 
the procmail stuff (so insert your existing procmail code below there).

As for the volume where you'll want to switch to spamc/spamd, it'll depend on 
your hardware :)  -- I think spamassassin on "decent" hardware will probably 
allow you to process one email every few seconds (maybe one every 5-10 
seconds?).  On the same hardware, spamc/spamd will probably increase that by 
about 50x, so you'll be able to do about 5 per second, maybe 10 per second.  
Whether it's worth switching over will depend on how heavily loaded the machine 
is, whether you need extra headroom on it, etc, etc.

Hope this helps,

C

Steve Yuroff wrote:

SY> Date: 29 Apr 2002 16:18:57 -0500
SY> From: Steve Yuroff <[EMAIL PROTECTED]>
SY> To: [EMAIL PROTECTED]
SY> Subject: [SAtalk] Deploying SA sitewide
SY> 
SY> Hi List,
SY> 
SY> I'm new at this type of thing, so bear with me.  I recently installed SA and 
.procmailrc files for 4 users at my small company, and it's working well- so well that 
it's time to let everyone benefit from this magic tool.  But before I do that, I have 
2 things I have to understand:
SY> 
SY> 1) Right now, I'm using 4 individiual .procmailrc files which redirect all 
X-Spam-Status: yes to [EMAIL PROTECTED] However, I'd prefer to use /etc/.procmailrc.  
If I'm going to use a global .procmailrc, can someone advise if I'm better off adding 
an X-Loop statement, or a statement that excludes [EMAIL PROTECTED] from any processing 
to avoid an endless loop of auto forwarding mail to itself? Some hints what that would 
look like would be greatly appreciated- every version I whipped up myself has ended up 
killing my filtering.
SY> 
SY> 2) At what volume should one use spamc/spamd over spamassassin?  I understand and 
can invoke regular 'ol SA just fine, but I'm not quite sure how to route it to 
spamc/d.  The whole starting dameons thing is beyond my current mojo... I'd need it to 
autostart on my Cobalt Qube 3.  Would anyone mind pointing me in the right direction?
SY> 
SY> Many thanks,
SY> Steve.
SY> 
SY> 
SY> 
SY> _______________________________________________
SY> Spamassassin-talk mailing list
SY> [EMAIL PROTECTED]
SY> https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
SY> 
SY> 
SY> 


_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk

Reply via email to