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 692535 - option to have filters active on an account should be enabled by default
option to have filters active on an account should be enabled by default
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Mailer
3.6.x (obsolete)
Other Linux
: Normal enhancement
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2013-01-25 14:55 UTC by Alexander van Loon
Modified: 2015-03-10 15:14 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
default filter settings for an account (276.02 KB, image/png)
2013-01-25 14:55 UTC, Alexander van Loon
Details

Description Alexander van Loon 2013-01-25 14:55:25 UTC
Created attachment 234412 [details]
default filter settings for an account

You want to filter some e-mails and create some filter rules. However, for some reason the filters don't work. It turns out that filters are not applied to new messages arriving in the inbox because of a "hidden" default setting. See the attached screenshot. By default both settings to apply filters are not enabled.

This way users have no idea why their filters don't work. I suggest that at least the second option to apply filters on new messages coming to the inbox is enabled by default.
Comment 1 Milan Crha 2015-03-10 15:14:03 UTC
Thanks for a bug report. This was supposed to be fixed with commit 5f9ee92d and I still see there that change, thus the issue might be somewhere else. I checked what current evolution does (3.12.11) and it has the option checked by default, the same as it sticks after I finish the new account wizard. I also tried a Google account configured through GNOME Online Accounts, and it has the option preselected as well. Thus I believe this got fixed meanwhile.