Hi,

> If I put a spamc (or spamassasin) call in /etc/procmailrc (and
> procmail is my MDA in sendmail), will SA look for user confs based on
> the intended recipient?  I think the answer is no, but I want to be
> sure.
 
Unless you DROPPRIV=yes or you use -u $LOGNAME, it will not use the
user preferences. See also the options to run spamd, I think -x should
turn off per_user config files.

> In order to test that things are working OK without munging anyone's
> mail, I decided to create a procmail recipe for my /etc/procmailrc.
> Tell me if this looks OK, or if I'm making some horrible mistake.  I
> tested it briefly on a low-usage system and it seems OK, but I'm
> particularly conerned about the locking aspect on a higher volume
> system.

In order to get people accustomed to SA, what I did is that for one
month I did the tagging with SA, but did not do any filtering.

So people would receive all their spam marked as *** SPAM *** in the
subject, and they could see by themself that SA was working correct.

Only after that I added the filtering of tagged messages, and it went
like a dream.

procmail is fail safe, I think spamc/spamd is too, that is if
spamc/spamd would fail, procmail would deliver the original message
unmodified, so I did not feel like using a copy of the message to run
SA.

Your receipt is OK, but bound to one problem: it uses a single file to
put all the messages, so it can proceed only one message at a time. If
your using external test (RBL, Razor...) proceeding one message can
take 1, 2,... 5 minutes. So during this period, you cannot deliver any
message!

Better you make it one file per message. Or at least one file per user
(so at a time you receive at most one messge per user).

One file per message would be something alogn the line:

DATE=`date +%Y%m%d%H%M`
PID=`echo $$`
SPAMFILE=$DEFAULT-spam.$DATE.$PID
:0c:
| spamc -f >SPAMFILE

which gives you a file name user-spam-200207160951-processID
I use that receipt to archive spam all the time and it works fine.

and one file per user would be along the lines

FILENONSPAM=/var/maildump/$LOGNAME.nonspam
DUMMY=`test -f $FILENONSPAM || touch $FILENONSPAM`
:0c:
| spamc -f >>FILENONSPAM

which gives you a file /var/maildump/user.nonspam
I used to use that receipt to sort copies of the spam/non spam

Olivier


-------------------------------------------------------
This sf.net email is sponsored by: Jabber - The world's fastest growing 
real-time communications platform! Don't just IM. Build it in! 
http://www.jabber.com/osdn/xim
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk

Reply via email to