| Summary | equally adjusted folders have different behaviour when new mail arrives |
| Queue | IMP |
| Queue Version | Git master |
| Type | Enhancement |
| State | Resolved |
| Priority | 1. Low |
| Owners | |
| Requester | l.kiraly (at) madalbal (dot) hu |
| Created | 07/10/2013 (4350 days ago) |
| Due | |
| Updated | 07/24/2013 (4336 days ago) |
| Assigned | 07/11/2013 (4349 days ago) |
| Resolved | 07/24/2013 (4336 days ago) |
| Milestone | |
| Patch | No |
State ⇒ Resolved
Priority ⇒ 1. Low
commit 28982a5c1e61a4356fed407fc3b324f58df513e1
Author: Michael M Slusarz <slusarz@horde.org>
Date: Wed Jul 24 00:52:39 2013 -0600
[mms] When checking for newmail in a mailbox, use the total
number of recent messages seen at any time during the page access
(
Request #12447).imp/docs/CHANGES | 2 ++
imp/lib/Block/Summary.php | 6 +++---
imp/lib/Mailbox.php | 6 +++---
.../Handler/Decorator/NewmailNotify.php | 6 +++---
imp/package.xml | 4 +++-
5 files changed, 14 insertions(+), 10 deletions(-)
http://git.horde.org/horde-git/-/commit/28982a5c1e61a4356fed407fc3b324f58df513e1
will remove the recent flag. E.g. ingo filtering using the imap
backend.
There is no way of reliably detecting "new" mail on a disconnected
client (even MODSEQ doesn't help us here). Unless we start doing
something like keeping track of all UIDs in the mailbox - or at least
a hash - which would become *very* expensive on large mailboxes.
State ⇒ Feedback
notifications for new mail, but this is independent from the folder
where new mail arrives.
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ equally adjusted folders have different behaviour when new mail arrives
Queue ⇒ IMP
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
$_prefs['newmail_audio']['value'] = 'reminder.wav';
$_prefs['newmail_notify']['value'] = 1;
but if I get email in the inbox or other non default folder I don't
get notification and sound signal.
However I have a folder where if I get new mail I get the notifications.
All those folders have the "Check for New Mail" option.