6.0.0-beta1
▾
Tasks
New Task
Search
Photos
Wiki
▾
Tickets
New Ticket
Search
dev.horde.org
Toggle Alerts Log
Help
11/4/25
H
istory
A
ttachments
C
omment
W
atch
Download
Comment on [#2211] Inconsistent fetchmail behavior
*
Your Email Address
*
Spam protection
Enter the letters below:
.__..__..__..___.. , [__]| |[__] _/ \./ | ||__|| |./__. |
Comment
>> 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. > > > > This works for me (new messages are indicated via the 'INBOX (#)' > header and I am sent to the page with the first unread message. > > > >> 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. > > > > Once again, I can not duplicate this. And this makes no sense. the > maintenance stuff is done before the mailbox page is even loaded, so > when the mailbox is built all these messages are already in the > mailbox. > > > >> 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). > > > > This can probably be changed. > > > >> 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 > > > > this is exactly what the code does now (except for the last part). > > > > My testing is with IMP HEAD btw.
Attachment
Watch this ticket
N
ew Ticket
M
y Tickets
S
earch
Q
uery Builder
R
eports
Saved Queries
Open Bugs
Bugs waiting for Feedback
Open Bugs in Releases
Open Enhancements
Enhancements waiting for Feedback
Bugs with Patches
Enhancements with Patches
Release Showstoppers
Stalled Tickets
New Tickets
Horde 5 Showstoppers