Say I have 2 IMAP folders - from an Exchange server if it matters. "Inbox" and "Helpdesk" The exchange server itself is filtering messages to individual folders. Most messages I get go to Helpdesk, because I work a helpdesk. A few others go to Inbox, which are also critical notifications. I require to be notified of _both_ if Claws is not foreground, via the notification area, a beep, libnotify...eg, the ways that the Notification plugin normally notifies me. The problem exists that if I have the current folder of Inbox selected, all new messages to Inbox fail to cause a notification. Further, there is no indication whatsoever if Claws is not visible in some way that I have even had new email. I've missed countless helpdesk tickets for HOURS because I have failed to set the context of Claws' folder selection treeview to something useless - like the "Mailbox (MH)" "Inbox" subfolder. This gets 0 messages - they all come via IMAP But as long as the new message arrives in a different folder than is currently selected, Claws notifies me. How can I get notifications for ALL emails, regardless of application folder state/context?
The plugin notifies about all incomming new mails, regardless of folder selection. Do the messages really have a "new" status, and not just "unread"?
What would I be looking for regarding the 'new' vs 'unread' status? This also does not describe the behavior I see... shouldn't this simply fail to notify of -any- message, if the 'unread' status was the issue? I reliably can make it notify of all messages, but only if the 'folder the message is going into' is not the currently selected/highlighted folder in the folder list view. I will take a video to illustrate the issue better as soon as I return to work.
http://youtu.be/Q-3G9cnyLQQ is a video expressing the issue. Now, this _may_ be related to the "notoification does not work on imap.gmail.com" bug, # 2451 However, notifications _DO_ work for me, AS LONG AS I RECEIVE MAIL TO A FOLDER WHICH IS NOT HIGHLIGHTED. This seems to me, at first and second glances, to be a different issue. Comment9 on the previously mentioned bug, http://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=2451#c9 , also indicates that this is a different issue. What _particularly_ am I looking for, in the IMAP protocol chatter, that CLAWS is also looking for to denote "new" vs "only unread"? Why do messages delivering to the non-selected folder still show "new" until I click the folder, and then click away, and then I have no more new messages?
An attentive watcher of the video will also notice that Claws thinks there is 1 'new' Helpdesk Tickets message, but 0 new Rancid messages within the treeview, after I receive both messages. There is something strange about Claws' context-sensitivity which is not implyed nor inferrable by these results.
From what you showed, the plugin is working as expected: If informs you about your new message in the helpdesk folder, but not about the unread, but not new message in your Rancid folder. That's how it is supposed to work. Now, if your question is why your Rancid message is not comming in as "new" - it could be your mailserver, or maybe some other bug in Claws Mail (that's why I am reassigning to IMAP folders, and leaving the bug open to IMAP experts to comment).
showing some --debug output would be more useful than a video.