[asterisk-bugs] [Asterisk 0013234]: [patch] Incorrect behavior when moving messages to/from New/Old folders
Asterisk Bug Tracker
noreply at bugs.digium.com
Thu Aug 7 17:17:30 CDT 2008
The following issue has been RESOLVED.
======================================================================
http://bugs.digium.com/view.php?id=13234
======================================================================
Reported By: jaroth
Assigned To: putnopvut
======================================================================
Project: Asterisk
Issue ID: 13234
Category: Applications/app_voicemail/IMAP
Reproducibility: always
Severity: minor
Priority: normal
Status: resolved
Asterisk Version: SVN
SVN Branch (only for SVN checkouts, not tarball releases): trunk
SVN Revision (number only!): 130693
Disclaimer on File?: N/A
Request Review:
Resolution: fixed
Fixed in Version:
======================================================================
Date Submitted: 2008-08-04 10:43 CDT
Last Modified: 2008-08-07 17:17 CDT
======================================================================
Summary: [patch] Incorrect behavior when moving messages
to/from New/Old folders
Description:
When a message is moved from a folder (such as Work) to the New folder
(IMAP INBOX) it is not marked as unread, thus it looks as though it is in
the Old folder. Moving a message from the New folder (UNREAD) to the Old
folder (or vice versa) does not change its read/unread status so in effect
the move does not happen.
This patch adds a method imap_mark_read() that can be called to set a
message to either read or unread, based on the flag used. This method is
called when moving a message into the New or Old folder to be sure that the
message flag is set correctly.
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
2008-08-07 17:17 svnbot Status assigned => resolved
2008-08-07 17:17 svnbot Resolution open => fixed
======================================================================
More information about the asterisk-bugs
mailing list