[Tickets #2211] RESOLVED: Inconsistent fetchmail behavior

[bugs@bugs.horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/?id=2211
-----------------------------------------------------------------------
 Ticket             | 2211
 Updated By         | Michael Slusarz <slusarz at mail.curecanti.org>
 Summary            | Inconsistent fetchmail behavior
 Queue              | IMP
 Version            | HEAD
-State              | Feedback
+State              | Resolved
 Priority           | 1. Low
 Type               | Bug
 Owners             | Michael Slusarz
-----------------------------------------------------------------------


Michael Slusarz <slusarz at mail.curecanti.org> (2005-11-28 22:47) wrote:

> Fetchmail invoked manually drops me into Folder A, no matter where I 
> was before.  While that is a predictable behavior (no matter where 
> you are, you always end up in Folder A), I'd much favor the behavior 
> of where you were before you invoked Fetch Mail, thats where you end 
> up.  If you're in your INBOX,  you end up in the INBOX.

This is the same issue as with the empty trash and empty spam folders - we
would have to do in-depth parsing of the URL to enable us to return to the
same page.  i.e. we can't just say return to 'message.php' since message.php
requires certain parameters.  same with 'mailbox.php' since the mailbox may
have changed in the session in the meantime.  or what if we are currently in
a page that can only be reached through a previous POST/GET - there is no
way to return this page.  Thus, we pick a sensible default that will always
work as expected rather than a separate method that can never be guaranteed
to work all of the time.