On Thu Oct 13 10:48:54 2005, Michael Haardt wrote:
On Wed, Oct 12, 2005 at 10:16:21AM -0400, Barry Leiba wrote:
> >? My implementation evaluates the first test to be true, and the
second
> >to false for all subjects. Trailing white space is kept and
used,
> >because that was intuitive to me
> > It's intuitive to you that a message with this line
> Subject: banana
> should NOT match this test
> header :is "subject" "banana"
> ?
> What, you didn't notice the space character after the word
"banana" in > the subject line? Neither did anyone else.
In case there was a space after "banana", it's not there any more.
I am not sure what that means now.
In this case, it's because Barry uses a client which does
format=flowed text, so it's likely that the client itself stripped
the space before sending - a trailing space has meaning in
format=flowed. I don't think this weakens his argument.
If you're really intent on having some mechanism to test for "raw"
features of the header content, then my personal view is that there
needs to be a "header" test, which normalizes whitespace, strips
header and footer, and decodes RFC2047, and a "rawheader", which
provides the header field value with all spaces, encoded words, etc,
intact.
The majority of people will intend that "banana" matches "Subject:
banana ", "Subject: =?Q?iso-8859-1?banana?=", and "Subject:banana"
and all other variations - the golden rule being if it looks as it it
ought to have matched when they observe it in the MUA, then it ought
to have matched.
Dave.
--
You see things; and you say "Why?"
But I dream things that never were; and I say "Why not?"
- George Bernard Shaw