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 349346 - Message Filter "starts with" doesn't work
Message Filter "starts with" doesn't work
Status: RESOLVED DUPLICATE of bug 343450
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-07-30 21:06 UTC by Sebastian Noack
Modified: 2006-08-01 14:00 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Sebastian Noack 2006-07-30 21:06:11 UTC
Please describe the problem:
Message filters doesn't work anymore since i updated evolution from 2.4 to 2.6.2 if "starts with" is enabled. May be this is also the case if "ends with" is enabled. I don't have tested it. But however "contains" still works.

Steps to reproduce:
1. Add a new filter by selecting Edit->Message Filters->Add or Message->Create Rule->Filter on *...
2. Select "Subject" as first field. But the bug occurs also by Sender, Recipints, etc.
3. Select "starts with" as second field
4. Type for example "[Bug" into the third field.
5. Setup the Then-Section to do something for example move the affected mail into your Bugs-folder
6. Click "OK"
7. Wait until you receive a mail with a subject starting by "[Bug".

Actual results:
Nothing.

Expected results:
The mail should become moved into my Bugs folder, like it was done before I updated to evolution 2.6.

Does this happen every time?
yes.

Other information:
I'm on Gentoo Linux and use evolution-2.6.2-r1 and gtk+-2.8.19.
Comment 1 André Klapper 2006-08-01 14:00:35 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. Please check the workaround described at bug 343450.


*** This bug has been marked as a duplicate of 343450 ***