Justin Gombos wrote:
Does this work around the problem, or does it still have the side
effect if the HB is embedded?
Specifying "H ??" or "HB ??" on the individual conditions avoids the bug.
However, these two run into the leading slash problem:
* ! \<scr\>
* HB ?? ! \<ex.?500\>
and should be written
> * ! ()\<scr\>
> * HB ?? ! ()\<ex.?500\>
if you want \< to act as a match to a non-word character.
Also, since there is no B on the colon line, you don't need to specify
"H ??" on the conditions where you did. For which part to run regexp an
exit code conditions on, H without B is the default (HB is the default,
overriding the colon line flags, for size conditions); that's confusing,
I know, because when it comes to which part to run the action on, hb is
the default.
____________________________________________________________
procmail mailing list Procmail homepage: http://www.procmail.org/
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail