procmail
[Top] [All Lists]

Re: spam spool format

1999-05-02 07:28:25
| I'm running a .procmailrc that calls the spam.rc file shown below:
| 
| 
| :0
| {
|         SPAM_LOG=${SPAM_LOG:-spam/spam.log}
|         SPAM_SPOOL=${SPAM_SPOOL:-spam}
|         FROM_ADDR=`formail -rtzxTo:`
| 
|         :0c
|         $SPAM_SPOOL/.
| 
|         :0
|         * ^To: *\/[^ ].*
|         { TO_ADDR=$MATCH }
| 
|         :0
|         * ^Subject: *\/[^ ].*
|         { SUBJ=$MATCH }
| 
|         :0
|         * ^Message\-ID: *\/[^ ].*
|         { MSID=$MATCH }
| # original seperators were (:) colons.  changed to ** [hp]
|         :0h: $SPAM_LOG$LOCKEXT
|         | (echo "`date` ** $FROM_ADDR ** $TO_ADDR ** $SUBJ ** $MSID" >> 
$SPAM_LOG)
| }
| 
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
| 
| This file sends suspect messages to a dir <spam> in numbered
| individual files like so:  ~/spam/1 2 3 4  etc.  The line:
| SPAM_SPOOL=${SPAM_SPOOL:-spam}  being the one that does that (I think). 
| 
| I'd rather have the messages appended to a spool type file, or really
| just a "unix-message-format" file.
| 
| With that format I can open the spam spool with "mail" "mutt"
| "emacs-rmail" etc etc.  view, delete etc as needed.
| The current setup leaves a spam dir with individual files for each
| message, which is not recognized by the above mentioned apps.
| 
| My problem is that I don't understand the syntax in spam.rc enough to
| tell it to make the kind of file I want.

I think I would just comment out the 'SPAM_SPOOL' variable (with #), then 
change 
the first recipe so that it puts spam into its own folder:

         :0c
         SPAM

-Dale-

<Prev in Thread] Current Thread [Next in Thread>