[prev in list] [next in list] [prev in thread] [next in thread] 

List:       procmail
Subject:    Re: Problem with ^TO_
From:       "Ruud H.G. van Tol" <rvtol () isolution ! nl>
Date:       2004-04-22 19:57:15
Message-ID: 038701c428a4$55346060$0a01a8c0 () isolution ! nl
[Download RAW message or body]

Toen wij LuKreme kietelden, kwam er dit uit:

> * ^TO_(.*<)?<?\/.*@subdomain\.domain\.com


There is another problem here:
- \/ is greedy to the left
- in front of the \/ you have 2 optional parts
- directly after the \/ is a .* that matches anything 
- so the optional parts in front of the '\/' will be 
  ignored, which leads to 
  * ^TO_\/.*@subdomain\.domain\.com
- the ^TO_ macro is for 'specific addresses', so not for .*@ 
  cases (the ones that ^TO@ is good for) 
- the greediness of the \/ bends that last rule a little

The expansion of the ^TO_ (simplified, see man procmailrc) is:
(^To:(.*[^-a-zA-Z0-9_.])?), which also ends in optionals, 
which reduces it to ^To: when '\/.*' follows it.

I don't think it is ever 'good' to put a '.*' directly 
after the '\/'. 

It is possible to do it when the part at the left of the '\/' 
does not end in optionals, but even then it is better to put 
a discriminating element directly following the '\/', 
for example the '[^ <]+' that David used.

-- 
Grtz, Ruud

_______________________________________________
procmail mailing list
procmail@lists.RWTH-Aachen.DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail

[prev in list] [next in list] [prev in thread] [next in thread]