Summary | saved new message gets deleted on forced logut |
Queue | IMP |
Queue Version | 6.2.8 |
Type | Bug |
State | Assigned |
Priority | 2. Medium |
Owners | Horde Developers (at) |
Requester | michael.menge (at) zdv (dot) uni-tuebingen (dot) de |
Created | 06/30/2015 (3606 days ago) |
Due | |
Updated | 01/22/2016 (3400 days ago) |
Assigned | 01/22/2016 (3400 days ago) |
Resolved | |
Milestone | |
Patch | No |
message sending, because in this case the cleanup is executed first.
If you timeout in the base window and then send from the compose
window, it should work though.
when the session is destroyed, the message is saved in VFS and
restored on the next login, no matter how the session ended.
(Postgres 9.3) as VFS Backend
Assigned to
State ⇒ Assigned
up in IMP_Application#logout() which is called from the
Horde_Registry#clearAuth(). At this point we do not know why the
logout happened. We don't even know in clearAuth().
We probably have to propagate the logout reason down the whole way to
the application's logout() method.
when the session is destroyed, the message is saved in VFS and
restored on the next login, no matter how the session ended.
Priority ⇒ 2. Medium
Type ⇒ Bug
Summary ⇒ saved new message gets deleted on forced logut
Queue ⇒ IMP
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
on forced logout
(e.g. session older than max session lifetime). As
https://bugs.horde.org/ticket/13108#c8 indicates
these draft should be deleted on normal log out but not on session time out.
This is not the normal session timeout (php garbage collection) but
Horde_Auth::REASON_SESSION
See http://comments.gmane.org/gmane.comp.horde.imp/32928 for more details