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 617990 - [new-mail-notify] “INBOX only” setting not respected
[new-mail-notify] “INBOX only” setting not respected
Status: RESOLVED DUPLICATE of bug 534369
Product: evolution
Classification: Applications
Component: Plugins
2.30.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-plugin-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2010-05-07 06:47 UTC by Yves-Alexis Perez
Modified: 2010-10-01 11:49 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Yves-Alexis Perez 2010-05-07 06:47:58 UTC
Hey,

I'm using the new mail notify plugin, and it seems it doesn't detect correctly the “INBOX” setting. When checking it, no notification are ever generated.

Running gdb and breaking on org_gnome_mail_new_notify() I can see that t->is_inbox is indeed 0 even when the mail is definitely in my INBOX:

Breakpoint 1, org_gnome_mail_new_notify (ep=0x1c8e2a0, t=0x7f8b79466720)
    at mail-notification.c:992
992	mail-notification.c: No such file or directory.
	in mail-notification.c
(gdb) print t
$1 = (EMEventTargetFolder *) 0x7f8b79466720
(gdb) print t->is_inbox
$2 = 0
(gdb) print t->uri
$3 = (gchar *) 0x7f8b7a6cc820 "imapx://corsac@mail.corsac.net/INBOX"

I'm not sure yet how is_inbox is set, but maybe the fact that my Inbox is called “INBOX” in caps fools it.

I'm not sure either which component use t->is_inbox but it might be problematic for them too (in that case reassigning might be a good idea)

If you need more info, please ask.
Comment 1 Milan Crha 2010-10-01 11:49:58 UTC
Thanks for a bug report. It should be fixed in bug #534369 or the IMAPX folder lost its flag for Inbox, which I doubt. Please try with evolution 2.30.2+

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