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 659726 - Search Folders contain ambiguous reference to accounts
Search Folders contain ambiguous reference to accounts
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Mailer
3.2.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
evolution[vfolders]
: 659729 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2011-09-21 14:39 UTC by Ian B. MacDonald
Modified: 2013-09-13 01:04 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Ian B. MacDonald 2011-09-21 14:39:02 UTC
I have some search folders configured to work on two IMAPx account Inboxes.  

Due to a separate issue where they were not properly upgraded between 2.32 and 3.1.91 I have to recreate them.

I noticed that when adding back in the local Inbox folders to my search folder criteria, they both appear with the same name.  In this case, I have to remember which one I added first because it is not obvious which one it was.  In the list of folders they appear as:

folder:/INBOX
folder:/INBOX

Previously they appeared as

imapx:mailboxname1/INBOX
imapx:mailboxname2/INBOX

Effectively this means that any time I make a change, to include maybe a new Inbox that the filter also applies to, I have to remove them all and manually add them.  Additionally if I later go inspect them I can not confirm that I actually have the correct Inboxes selected.
Comment 1 Ian B. MacDonald 2011-09-27 19:21:08 UTC
confirmed downstream in a related bug report
Comment 3 Ian B. MacDonald 2011-09-29 00:01:04 UTC
Patch fixes my problems against 3.2.0 in current Ubuntu 11.10 B2. 

Also corrects related https://bugzilla.gnome.org/show_bug.cgi?id=659729

thanks
Comment 4 Milan Crha 2012-05-31 12:10:33 UTC
*** Bug 659729 has been marked as a duplicate of this bug. ***