-
-
Notifications
You must be signed in to change notification settings - Fork 124
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] WARN fetch_envelopes_by_sequence{client=1}: imap_client::tasks: skipping invalid fetch (2028 occurrences) #525
Comments
I cannot investigate right now, but it may be related to modern-email/defects#38. |
I would also like to help debugging this issue and I can reproduce it 100%. The message triggering this does not contain any non-ASCII characters. |
Hello! If what you say is true, we may actually be facing two bugs in a trench-coat. |
Reproduction is actually very simple using https://github.com/foxcpp/maddy. Start up the server, create an imap account, send yourself a message. Done. |
Here is the maddy log with himalaya connecting. This is the highest log level available.
|
As I was sifting through thousands of mails with himalaya (great tool by the way!), I came across a weird instance where himalaya would report that my inbox only contained a single mail, whereas the ProtonMail web client reported a lot more.
Turning
--debug
on indicated that there were 2828WARN fetch_envelopes_by_sequence{client=1}: imap_client::tasks: skipping invalid fetch
warnings.Context (Environment)
I'm using himalaya on a Windows laptop, with ProtonBridge running.
Other than the reported issue, and the occasional error/panic, it mostly works, I was able to create folders, move many mails to those folders, delete folders, etc.
Steps to Reproduce
I want to help pinpoint and troubleshoot this issue, but the logs contain tons of PII that I cannot share.
I was sadly unable to send myself a mail that would reproduce the issue.
I've taken some troubleshooting steps and have been able to eliminate some possible causes:
--page-size
and--page
did not produce much difference. To get the 2828 warnings, I used the rather aggressive--page-size 10000
I am struggling to find more useful debugging steps, short of reading the code (which I may do this weekend, but being unfamiliar with IMAP and this codebase, I will probably struggle there too)
Here is one example of an invalid fetch:
And here is a shorter one:
Is there any step I can make to help pinpoint this?
Expected Behavior
I'd expect himalaya to be able to handle these 2828 mails just fine, as ThunderBird is able to.
Current Behavior
Many
WARN fetch_envelopes_by_sequence{client=1}: imap_client::tasks: skipping invalid fetch
warningsThe text was updated successfully, but these errors were encountered: