[Tickets #13108] Re: keep auto saved message in compose window although session is expired

[noreply at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/13108
------------------------------------------------------------------------------
  Ticket             | 13108
  Updated By         | Michael Slusarz <slusarz at horde.org>
  Summary            | keep auto saved message in compose window although
                     | session is expired
  Queue              | IMP
  Version            | 6.1.7
  Type               | Bug
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2014-04-16 15:14) wrote:

> Yes, we enable  "Compose messages in a separate window? (Basic view  
> only)" because this is needed for the use of s/mime.

This is irrelevant for dynamic view.

> And yes, in generel the message will be saved in the drafts folder  
> after some minutes (or if I press the button to save in drafts...).
>
> The problem is that some users get horde to remove/delete this  
> already saved messages out of the draft (or it never was saved  
> there?). If the users call us for help they tell us horde said the  
> session had expired after clicking on the send button. So the  
> composed message text get lost in the closing window...

This is explicitly handled in the IMP_Application#appInitFailure() ...  
if compose data is seen in a POST and there is no session, the message  
should be saved to the user's VFS backend.  (We can't save to users'  
draft mailbox, since we don't have access to the IMAP server at this  
point).

I faintly remember fixing some issues relating to session expiration  
in the near past.  Although you may need to be running (unreleased)  
Horde 5.2 and/or IMP 6.2 and/or Horde_Core to see the fixes.

> The question is: Can we do anything to prevent this? I guess the  
> session expired to to other user acitivity in a 2nd... 3rd...  
> browser window.

This is already handled.