[Tickets #2211] NEW: 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
 Created By         | kevin_myer at iu13.org
 Summary            | Inconsistent fetchmail behavior
 Queue              | IMP
 Version            | HEAD
 State              | Unconfirmed
 Priority           | 1. Low
 Type               | Bug
 Owners             | 
-----------------------------------------------------------------------


kevin_myer at iu13.org (2005-07-01 15:16) wrote:

The fetchmail/accounts code in IMP behaves inconsistently, depending on the
results of a fetchmail operation.  In addition, the message index is not
updated if new messages are received.

mailbox_start=1
sort_by=0
sort_dir=0

Examples:

On initial login, with unread or read messages in the INBOX, if you have
fetchmail configured as a maintenance task and confirm that, and no new
messages are on the remote server, you are dropped into your INBOX, at the
first unread message.  This works as expected.

On initial login, with no unread message in the INBOX, if you have fetchmail
configured as a maintenance task and confirm that, you're dropped into your
INBOX and the notification is that Fetchmail: N messages in Account name. 
However, the message index is not updated to reflect the fact that you have
a new message and you are positioned at the beginning of the messages.  I
would expect that the number of new messages would be reflected in the INBOX
and that you would be taken to the first new unread message.  But I need to
refresh to get that to happen.

On initial login, with one or more unread messages in your INBOX, if you
have fetchmail configured as a maintenance task and confirm that, you're
dropped into your INBOX and the notification is that Fetchmail: N messages
in Account name.  However, the message index is not updated to reflect the
fact that you have a new message and you are positioned at the first unread
"old" message.  Again, you have to refresh your INBOX to see the new message
count.

After initial login, if you go to the Accounts icon in the menu of IMP and
force a check for new messages, you are presented with a confirmation
screen.  After you confirm, your accounts are checked.  And you are returned
to the confirmation screen, with Fetchmail: N messages in Account name.  My
expectation is that you'd be returned to your INBOX (or whatever folder you
were in when you invoked fetchmail).

I think the algorithm for fetchmail should go something like this
(everywhere its invoked from):

Check for confirmation and which accounts to check
Check for mail in remote accounts
Update folder index with new message index
Return to either the folder that fetchmail was called from, or initial_page
(if initial login and there was no folder that fetchmail was called from)
and honor the value of mailbox_start