RFC 2822 (sec. 2.2.3) says, "Each header field should be treated in its unfolded form for further syntactic and semantic evaluation." But TB! does not seem to do that; AFAICT, when TB! tries to match a header field using a regular expression, it uses the still-folded field, full of newlines. Can anyone confirm this (or, of course, correct me if I'm wrong)?
This question came up when I was building a filter to color replies to my own messages, using the References header. I only wanted to color them if one of my MIDs is last in the References field. I expected this to work: Header field References match remarqs\.net>$ But it gave false positives if my MID appeared anywhere in a folded References header field, apparently because the $ matched newlines in the middle of the field. Making sure those newlines aren't matched fixes the filter: Header field References match (?-m)remarqs\.net>$ (This is a simplified test case -- I know I need to look at In-Reply-To headers as well. Luckily, that's simpler. :) -- Mike The Bat! v. 3.80.06 Hamster Classic v. 2.1 (Build 2.1.0.11) Windows XP 5.1.2600 Service Pack 2 ________________________________________________ Current version is 3.80.06 | 'Using TBUDL' information: http://www.silverstones.com/thebat/TBUDLInfo.html
