“The behaviour you’re suggesting would essentially end up by showing the notification while unread email is present.”
Yes, exactly, and with an “external variable” eM Client could save actually unread message, so next sync it could compare this value with the new one: only if this number is greater of the previous one, play the sound (so it will not sound every sync, if the unread emails are the same)
By the way, I’ll waiting for version 7… maybe it’ll be the right time to uninstall Windows Live Mail…
I am experiencing this problem too and together with one other bug (I just posted), it keeps me from buying your great email client. Can you please reconsider?
I am quite sure that you are able to check the subfolders for new email too. It might be somewhat more difficult than the INBOX itself, but it is technically possible. Thunderbird does it (and I want to get rid of TB so that’s why I am here).
If it is an expensive operation, you could, like in Thunderbird, give the user the option to select which folders should be checked/synchronized.
The solution of letting eM do the filtering to folders is not an option for me. I use my email account on different computers and not all of them allow me to set those kind of rules. I let my email server handle the sorting because of this.
I moved from Thunderbird to eM just some days ago and I really like eM since it is on my PC.
But, I experience the exact same situation as described above. Hope there will be some solution for that in version 7.
Btw. I using a IceWarp Server together with Nine on my Android phone. Nine also manages this situation…
I feel that I must chime in here and say that I completely do not understand your stated reasoning why emClient cannot indicate/notify of new messages in subfolders. To be clear, I think emClient is great so far, but of course there is always room for improvement.
Is the original poster using POP3 or IMAP? I’ll assume IMAP.
Every other email client I have ever used (including Thunderbird) behaves as expected in this regard (shows new messages quantities in any folder).
Clearly, emClient is detecting/indicating new emails are present in the subfolder, as indicated by the “…” icon. Then, when the folder is selected, emClient downloads the message headers and changes the icon to indicate the number of new messages.
OKAY…so how about we just make emClient automatically download new message headers in any subfolders??? This function is no different than in the INBOX. With all due respect, it makes NO sense to say otherwise. An IMAP message is an IMAP message, no matter where it is located in folders.
If for some reason it is undesirable in some cases to have this behavior, then you could make it an option.
I cannot see anything difficult about this from a programmatic perspective. The fact is emClient already does this for the INBOX.
Hi Matthew,
if you set your IMAP account to download messages for offline use you will see the number of new messages even in subfolders.
You can set this in Tools>Accounts under the IMAP tab of your chosen account. Just check the option to “Download messages for offline use”.
However, I don’t want to “download messages for offline use”, as this would consume a large amount of space on my local PC.
With IMAP protocol, it is not necessary to download messages to determine unread messages. Allow me demonstrate how simple it is, using a raw telnet session connecting to a demo email account with 5 emails, several of which are unread…
(Note for the casual observer… this “language” and sequence of commands is how emClient and other email clients communicate “under the hood”, “behind the scenes” with your email server)
(commands that I enter are in bold , the server’s responses of interest are in _ bold _, and any of my comments are bold and underlined )
$ telnet mymailserver.com imap
Trying 56.23.45.78…
Connected to mymailserver.com.
Escape character is ‘^]’.
* OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE NAMESPACE STARTTLS AUTH=PLAIN AUTH=LOGIN] Dovecot ready. LOGIN [email protected] mypassword
a OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS BINARY MOVE NAMESPACE SPECIAL-USE COMPRESS=DEFLATE QUOTA] Logged in a LIST “” "*"
* LIST (\HasChildren) “.” INBOX
* LIST (\HasNoChildren \Junk) “.” INBOX.Junk
* LIST (\HasNoChildren \Sent) “.” INBOX.Sent
* LIST (\HasNoChildren \Drafts) “.” INBOX.Drafts
* LIST (\HasNoChildren \Trash) “.” INBOX.Trash
* LIST (\HasNoChildren \Archive) “.” INBOX.Archive
a OK List completed (0.000 + 0.000 secs). a examine INBOX
* OK [CLOSED] Previous mailbox closed.
* FLAGS (\Answered \Flagged \Deleted \Seen \Draft)
* OK [PERMANENTFLAGS ()] Read-only mailbox.
* 5 EXISTS
* 0 RECENT
* OK [UNSEEN 4] First unseen.
* OK [UIDVALIDITY 1371737469] UIDs valid
* OK [UIDNEXT 10] Predicted next UID
* OK [HIGHESTMODSEQ 14] Highest
a OK [READ-ONLY] Examine completed (0.000 + 0.000 secs). a SEARCH UNSEEN
* SEARCH 4 5
a OK Search completed (0.001 + 0.000 secs). a EXAMINE INBOX.Trash
* OK [CLOSED] Previous mailbox closed.
* FLAGS (\Answered \Flagged \Deleted \Seen \Draft)
* OK [PERMANENTFLAGS ()] Read-only mailbox.
* 1 EXISTS
* 0 RECENT
* OK [UNSEEN 1] First unseen.
* OK [UIDVALIDITY 1371737473] UIDs valid
* OK [UIDNEXT 2] Predicted next UID
* OK [HIGHESTMODSEQ 2] Highest
a OK [READ-ONLY] Examine completed (0.000 + 0.000 secs). a SEARCH UNSEEN ** **
* SEARCH 1
a OK Search completed (0.001 + 0.000 secs).
As you can plainly see, there are:
2 unread messages (#4 and #5) in Inbox
1 unread message in Trash
So, this demonstrates how very simple it is for the email client to determine unread message counts for any folder. There is no need to “download messages for offline”.
Why can’t emClient do this? Many other email clients do this (Thunderbird, etc)
Also, using the “download messages for offline use” creates an enormous amount of logins on the mail server. My limit is at 1000 I think, which should be sufficient with one mail client running all day, but every minute a new login is done to check one of the 10+ subfolders, getting me at that limit very quickly. This problem can be fixed by you of course, but then there is also what Matthew said: there is a reason for these subfolders, we have a huge amount of emails and there is no need to store them locally at all.
Hello
I would really appreciate having notifications for subfolders (rules are done on server side).
I use Em client only for month and this is thing I absolutely miss here.
I will by pro with free upgrades hoping this feature will arrive soon, because otherwise it is awesome client.
As written elsewhere: you will not see this features in version 7 nor in any other update this year.
Trust me this company won’t include any deal-breakers the next version as they weren’t the last few years. OK conversation view is the one and only, I have to admit, but that’s it!
FWIW, using smart folders with the unread search folder is also not very helpful when you are using loacal folders and move your unread messages inside.
Smart folders don’t show unread items when they are moved to local (sub-)folders. This is very very annoying and half-baken!
I investigated this a bit further, and I now understand better what emClient is saying in terms of their current limitations. I also understand better how emClient can solve this - and it’s not too difficult.
I can explain what I learned, for anyone who cares…
For starters, this entire thread is based on the need to filter emails on the server, and not on the email client. The former is more consistent with IMAP, where the server is the central “repository” of emails, and all clients are just “viewing” what is on the server.
With IMAP specifically, there are 2 ways to check for new email…
The client can “poll” (ask) the server periodically.
The server can send “push” notifications to the email client only when new email arrives.
As you might imagine, method #1 above is less efficient (generates more traffic) than method #2.
To use method #2, IMAP servers support a function called “IDLE” which allows a client (like emClient) to request notification of activity in a particular folder. The “IDLE” command can be activated on any folder (key point there). So, when a client sends an “IDLE” command, the server knows to send notification of actions (like new email) in the specific folder selected.
Paul@emClient points out that emClient does not notify of new emails in subfolders because the server only notifies emClient of new emails in the main INBOX. This is true, but there is a bit more to it. Actually, this is not a limitation of the server. The server can notify of activity on any folder. emClient (or any client) just has to request it. It simply means emClient has to use separate threads (TCP connections) for each folder which needs to be “watched”, because it’s a 1-to-1 relationship… i.e., a client can be in “IDLE” mode once per connection.
So, the ideal solution (in my view) is as follows:
Modify emClient such that it can open multiple connections to an IMAP server (clearly it can already open multiple connections, since multiple email accounts are supported, so I doubt this would be a problem).
Add an option to emClient allowing the user to select which folders to “watch” for activity. I’m not sure if the default should be “off” or “on”. I would choose “on”. Then emClient just opens a connection to each selected folder and uses “IDLE” mode on each connection to monitor for activity in the folder.
you are right about the “push” vs. “pull” but unfortunately em client does not support push. If it would new emails on the server would be arrive instantly (as soon as the server announces it) and there would be no intervals in checking the mail folders.
Also (as you wrote) the push protokoll needs permanent open connections for each account/folder so this really should be an optional feature and not mandantory.
But, actually I was referring to “push” in the context of IMAP IDLE, which emClient does support, which uses a persistent connection. (But emClient only supports it for the INBOX).
This does allow asynchronous and immediate notification to emClient the moment new email arrives on the server, without periodic polling (“pulling”) by emClient. You can verify this with Wireshark, as I have. The first thing that happens when a new email arrives at the server is a response packet from the email server to emClient.
So, again, what I am suggesting here is the same as what already exists for the INBOX, only expanding to use one connection per folder needing to be monitored.
I am curious as to whether you had any thoughts about my last comment from some months back?
As I have tried to explain in my previous comment, emClient already supports the IMAP IDLE mechanism necessary to achieve the notification on any folder. As I have written in my previous comment, all this feature requires is for emClient to make additional connections for any folder needing notification. I think most users would totally thrilled with something as simple as a “right-click” context menu “new mail notify” on/off option on folders. It could default to “off” for all folders, except INBOX which would of course be “on” as it is now.
What are yours or emClient’s thoughts on this?
Would it be helpful to open a new thread that more specifically defines this exact requirement? I realize there is much back and forth in this thread, and thus it may not seem immediately clear what is being asked for.
Hello Rally,
this is not a problem but the way the product is designed to work. Notifications only appear for Inbox.
Sorry if that is an inconvenience for you.
Thank you for reply. I think it is clear that only Inbox notifications are supported in version 6 or 7.
However, I was curious if you had some thoughts on the recent suggestions in this thread regarding support for new-mail notification on any user-selected folder?
I’m not certain about other email users, but many of my email providers allow server-side filtering into subfolders (Google Mail, to name one).
That being said, I would seem important to receive notification of new email in folders other than Inbox. Would you agree?
So then, do you suppose eMClient might consider supporting this?
As explained in previous posts, from a technical perspective this should not be difficult to accomplish, since it can use the exact same mechanism that is being used for Inbox notification.
I agree with Matthew here. This is a design flaw in eMClient. When eMClient syncs with the mail server, it should (at least have the option to) sync with all folders, not just inbox.
