mirror of
https://github.com/d99kris/nmail.git
synced 2026-04-26 09:46:01 +03:00
[GH-ISSUE #112] [Bug] New messages sometimes not retrieved while idle #97
Labels
No labels
bug
enhancement
pull-request
question
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nmail#97
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @krackout on GitHub (Oct 7, 2022).
Original GitHub issue: https://github.com/d99kris/nmail/issues/112
Originally assigned to: @d99kris on GitHub.
Sometimes e-mail delivery is not happening until I manually refresh (pressing L); it happens in idle state only. Yet mails are mostly received in a timely fashion, I cannot make a correlation when nmail doesn't get the signal (of some kind, don't know the details) that new mail has arrived.
Yet I cannot speak of a bug, haven't got any hard evidence. I have this setting on,
idle_fetch_flags=1in case it's related. I'm thinking of changingserver_timestamps=0to 1 to see if it makes any difference.It seems to happen mostly on my work (Microsoft 365) account. But since I constantly use it, it's not easy to be certain about it; I'll try to leave it idling in the weekend and send test e-mails to check.
@Kabouik commented on GitHub (Oct 7, 2022):
Like you, I couldn't really correlate it to anything and so never reported the issue, but my impression is it's a valid one because I do experience it as well, on a work Exchange account and other non-Exchange accounts.
I don't know if it is related or not, but sometimes L cannot fetch anything new, while quitting nmail and relaunching it does, as if this would trigger a "deeper" fetching. Or would put nmail out of idle?
On 2022-10-07 16:12 krackout @.***> wrote:
@d99kris commented on GitHub (Oct 8, 2022):
Yes,
nmailsupportsIMAP IDLE. After no IMAP activity for 15 seconds,nmailfetches message uids and then enters idle. Upon idle notification,nmailfetches message uids and exits idle. After 29 mins in idle state,nmailstops and restarts idle.I have not encountered any issues relating to this myself, but reviewing the implementation I believe I've found some possible improvements. For example we could fetch message uids at every 29 min idle timeout.
However, I'll need to do some more checking and testing on this before I can prepare a fix.
@krackout commented on GitHub (Oct 8, 2022):
Plus to the other possible improvements, how about reducing time in idle state to 15-20 minutes?
Or perhaps leave everything as is and implement a refresh at a time interval option, set by configuration.
Στις 8 Οκτωβρίου 2022 12:09:14 μ.μ. EEST, ο/η Kristofer Berggren @.***> έγραψε:
@d99kris commented on GitHub (Oct 8, 2022):
Yep, we can certainly make the timeout configurable.
@d99kris commented on GitHub (Nov 13, 2022):
The above commit adds support for configuring idle timeout with
idle_timeoutin~/.nmail/main.conf.Will keep this issue open until other fixes have been committed.
@d99kris commented on GitHub (Nov 13, 2022):
The above commit implementes more robust detection of new emails while in idle.
Will keep this issue open until a few more related fixes have been committed.
@d99kris commented on GitHub (Nov 13, 2022):
The above commit adds better status reporting during idle.
Will keep this issue open until one more related fix has been committed.
@d99kris commented on GitHub (Nov 13, 2022):
The above fix detects when device is returning from sleep mode, and if in idle mode, ensures we exit idle mode (and indirectly try fetch messages again before re-entering idle).
This is the last idle-related fix for this Github issue.
@d99kris commented on GitHub (Nov 13, 2022):
Just like to add on - while the latest nmail idle functionality has been tested OK with several email service providers, there is one with problems: outlook.com
However, it seems to be a server-side problem according to
https://techcommunity.microsoft.com/t5/outlook/outlook-office-365-imap-idle-is-broken/m-p/3616242
Hopefully Microsoft fixes this soon. As a temporary workaround one can now set idle timeout to some lower value, effectively polling the server for new messages.