After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 343316 - filtering on "specific header" using "is" requires unexpected whitespace in string to match
filtering on "specific header" using "is" requires unexpected whitespace in s...
Status: RESOLVED NOTABUG
Product: evolution
Classification: Applications
Component: Mailer
2.6.x (obsolete)
Other All
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
evolution[filters]
Depends on:
Blocks:
 
 
Reported: 2006-05-29 18:16 UTC by Dooglus
Modified: 2006-06-08 13:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description Dooglus 2006-05-29 18:16:16 UTC
Please describe the problem:
I would like to filter emails based on this header:

  X-Bugzilla-Product: Firefox

I set the filter up as:

  [Specific header] [X-Bugzilla-Product] [is] [Firefox]

but it didn't match.

After trying various things (like including the ':' in the header name) I found
that what I had to do to make it work is:

  [Specific header] [X-Bugzilla-Product] [is] [ Firefox]

ie. with a space before the word 'Firefox'.

The header in the message is exactly as pasted above.  That is copied from the
source of the email.  It is a raw header.  It is also how it is displayed in
evolution's preview panel when all headers are displayed.  It is a single space.

Steps to reproduce:
1. send an email to yourself with subject "test"
2. create a filter on [Specific header] [Subject] [is] [test] moving the message
to a different folder
3. use control-y to run the filter on the message
4. notice the filter doesn't trigger
5. edit the filter to be [Specific header] [Subject] [is] [ test]
6. use control-y to run the filter again
7. notice the filter works now that there's an extra space before 'test'

Actual results:


Expected results:


Does this happen every time?
yes

Other information:
Comment 1 Jeffrey Stedfast 2006-05-30 14:11:10 UTC
you are asking for an exact match, that's what "is" is. If you don't want an exact match, use "contains"
Comment 2 Dooglus 2006-05-30 17:05:21 UTC
I used evolution to create the email.  I told it to use subject "test".

I used evolution to filter the email.  I told it to filter on subject "test".

It doesn't filter.

Either the email was created with the wrong subject, or the filter isn't detecting the subject correctly, but I set the subject to the same value I'm matching on, and it doesn't match.

How can that be correct behaviour?
Comment 3 Johan Walles 2006-06-08 13:47:14 UTC
I'm also curious about how the behaviour described in comment 2 can be considered correct.  Would re-open if I could to get a reply, but I can't...