procmail
[Top] [All Lists]

Re: Problem with charset recipe

2004-04-16 16:10:06
Ruud H.G. van Tol wrote:

Toen wij Timur Tabi kietelden, kwam er dit uit:


* ^Content-Type:.*charset=(\")?(${CHARSETS})


That needs an early $, see man procmailrc:

  $    Evaluate the remainder of this condition according to
       sh(1) substitution rules inside double  quotes,  skip
       leading whitespace, then reparse it.

What exactly does that mean?

  CHARSETS = "(Windows-1251|koi8-r|big5)"
  CT_test  = "^Content-Type:.*charset=\"?$CHARSETS"
  dh       = ".dh-unblocked-spam/"

  :0
  *$ $CT_test
  $dh

  :0E
  *$ B ?? $CT_test
  $dh

I haven't tried that yet, but I don't understand why I need CT_test. I made some changes, and this is what I have now, but it still doesn't work:

:0
* ^Content-Type:.*charset=\"?$CHARSETS
.dh-unblocked-spam/
:0E
* Content-Type: multipart/
* B ?? ^Content-Type:(.|$)*charset=\"?$CHARSETS
.dh-unblocked-spam/



--
Timur Tabi
This email is digitally signed with my public key (S/MIME).
Please use this key to encrypt all email sent to me.

Looking for a low-cost, full-featured web host?
Try DreamHost: http://www.dreamhost.com/rewards.cgi?thetabis

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail
<Prev in Thread] Current Thread [Next in Thread>