LuKreme wrote Monday, October 08, 2007 2:01 AM:
On 7-Oct-2007, at 16:58, Dallman Ross wrote:
1) It is perfectly legitimate to have no whitespace after the
colon;
Er.. I don't have the rfc in front of me, so you MAY be right, but
I've NEVER seen it in 20 years of email.
I don't see it either, but it's allowed. You're the one who (with
me) was arguing just last week that #$%^&*! and so on are allowed in
email addresses per the RFCs. We don't see those, either, as a
rule. I wasn't arguing that we see no space; only that it's
technically permitted. (Actually, I use it -- the lack of one --
as a spam test.)
* $ ^From:.*\/[^$WS].*
I prefer to match on know characters when possible than just
wildcarding for any old thing.
Um we *are* matching on known characters. The operation of
the procmail regex engine is sparse to the left of the match
token, but greedy to the right. So ".*\/[^$WS]" will always
match the first nonwhite character in that header -- regardless
of whether there is zero or there are 10,000 whitespace chars
(or more) before it. The functionality is exactly the same
between these two expressions:
* $ ^From:.*\/[^$WS].*
* $ ^From:[$WS]*\/[^$WS].*
That said, I prefer the 'bare from'
of the formail version anyway.
You might find this useful:
http://marc.info/?l=procmail&m=112782054630212&q=raw
Note that there is a follow-up with correction:
http://marc.info/?l=procmail&m=112782851505589&q=raw
(Sean: what is up with the procmail.org regular searchable
archive's not working of late?!)
Dallman
____________________________________________________________
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