On Wed, May 15, 2002 at 09:26:50AM -0600, LuKreme wrote:
| On Tuesday, May 14, 2002, at 08:24 PM, Sidney Markowitz wrote:
| >On Tue, 2002-05-14 at 18:28, Ron Carter wrote:
| >
| > :0:
| > * ^X-Spam-Status: Yes
| > /dev/null
| >}
| >
| >I agree with Theo that piping to /dev/null is not a good idea because 
| >spamassassin is
| >not perfect.
| 
| I have
| 
| :0:
| * X-Spam-Level: **********
| /dev/null

Are you sure this does what you think it does?  I think this regex
reads like this :
    
0 or more occurences of
 0 or more occurences of
  0 or more occurences of
   0 or more occurences of
    0 or more occurences of
     0 or more occurences of
      0 or more occurences of
       0 or more occurences of
        0 or more occurences of
         0 or more occurences of
          a single space character

The other interpretation I can think of is that the regex fails to
compile.

Remember that '*' in a regex means "0 or more occurences of the
preceding item".

I think that rule should be
 
* X-Spam-Level: \*\*\*\*\*\*\*\*\*\*

but correct me if I'm wrong.

| Although I would prefer a way to bounce it (with spamassasin headers), on 
| the off chance that there is ever legitimate mail with a spam score over 10.

One solution is to use Marc Merlin's sa-exim function.  I'm using this
right now.

Another solution would be to use a router that matches the header and
routes to ":fail:" (if you're using exim).

Once procmail has the message it is really hard to bounce
it because
    o   often the envelope sender (where to send the bounce) is no
        longer known
    o   the MTA has completed delivery already, the "bounce" would
        really be a brand new message

HTH,
-D

-- 

The lot is cast into the lap,
but its every decision is from the Lord.
        Proverbs 16:33
 
GnuPG key : http://dman.ddts.net/~dman/public_key.gpg

Attachment: msg04979/pgp00000.pgp
Description: PGP signature

Reply via email to