| Summary | The "seen" flag does not stick |
| Queue | IMP |
| Queue Version | 6.1.5 |
| Type | Bug |
| State | No Feedback |
| Priority | 1. Low |
| Owners | |
| Requester | nsemenova (at) parallels (dot) com |
| Created | 12/04/2013 (4268 days ago) |
| Due | |
| Updated | 01/13/2014 (4228 days ago) |
| Assigned | 12/04/2013 (4268 days ago) |
| Resolved | 01/08/2014 (4233 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
of our users still have problems with non-persisting IMAP flags. Any
chance of figuring out what changed between the working 5.0.4 and
this version of Imp?
Including library/Horde package code. So that's not the way to
approach this.
The only proper way to approach is to determine what is occurring in
the current code, rather than trying to figure out the changes.
of our users still have problems with non-persisting IMAP flags. Any
chance of figuring out what changed between the working 5.0.4 and this
version of Imp?
correctly marking the message as seen during a non-peek FETCH. But
would need IMAP logs to verify.
right after page reload.
message is correctly flagged and on reload, the message is reset to
the previous flag state.
(hit F5) , the message is marked as 'unread' again.
correctly marking the message as seen during a non-peek FETCH. But
would need IMAP logs to verify.
To further debug this issue, we need details of the IMP -> IMAP/POP
communication.
To enable debugging, see instructions contained in
imp/config/backends.php (the 'debug' config parameter).
Debugging should not be enabled on a production server, Attach/post
only the portion of the log that directly deals with the problem
reported (it may be simplest to clear the log file and then perform
the event that causes the error).
imp-query-imap-cache --purge
but the problem still exists. Actually I did not believe purging imap
cache would help, because when we updated our Webmail servers last
Friday, all of them were rebooted and the imap caches started up as
being empty anyway.
We would be extremely grateful for a solution. Thanks for your help.
State ⇒ Feedback
-> 5.1.3) and have constant reports from users of different browsers.
I also saw similar with \Deleted flags: messages that were already
marked deleted were suddenly shown as not deleted ones when I deleted
another message.
The flag gets correctly written to the IMAP server, so IMP gets it
right after page reload.
State ⇒ Unconfirmed
Patch ⇒ No
Milestone ⇒
Queue ⇒ IMP
Summary ⇒ The "seen" flag does not stick
Type ⇒ Bug
Priority ⇒ 1. Low
(hit F5) , the message is marked as 'unread' again.
Steps to reproduce:
1. Send a message
2. Click on the message to "see" it (do not use mark as ... seen)
3. Make sure that the message is marked as seen (it is not bold any more)
4. Hit F5 to refresh the page
5. Check the message, it is marked as 'unseen' (bold) again