-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Don't retry failing uploads indefinitely #3986
Comments
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
I may be having the same issue as described here. Sent messages are not stored on the server (although they are shown in the local sent folder). Read status is not updated, etc. Therefore I attach a log here. EnvironmentK-9 Mail version: Android version: Account type (IMAP, POP3, WebDAV/Exchange): Please let me know if more information is needed |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
@chrisgee: Thanks for the log. The message being uploaded is quite large. Chances are the server is closing the connection because it considers the message too large. Or maybe the quota is exceeded. |
Thanks for the info. I guess this should be considered a bug, namely that the failing task breaks a lot of other functionality.
Bzw, it's not my quota.
Any way to recovery without reinstalling and deleting all the not uploaded messages?
Thanks,
Christoph
Am 29. Juni 2019 18:03:57 MESZ schrieb cketti <notifications@github.com>:
…
@chrisgee: Thanks for the log. The message being uploaded is quite
large. Chances are the server is closing the connection because it
considers the message too large. Or maybe the quota is exceeded.
Unfortunately, K-9 Mail considers this to be a temporary error and will
try to upload the message over and over again. All other command wait
in the queue until the upload command succeeds (or fails permanently;
which, in this case, it never does). That explains why the read status
is never updated.
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
#3986 (comment)
--
Christoph Gohle
|
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
It's unclear how this situation should be handled best. A connection could be closed at any time without it being a permanent error. |
How is this handled now? |
I am quite ignorant with respect to what is going on in K9 internally. If there is a list of commands to the server to be processed, wouldn't Just an idea... |
... but it sounds like a good one. |
Every 3 months or so I have a problem accessing my web.de account: When I activate the directory list (in German 'Ordnerliste'), I see that ever folder has an error message (the beginning is 'SSLException: Write error:'; how can I see the rest?). From now on, fetching the mails is approximately 10x slower, and storing changed mails (e.g. with a changed read status) is not working at all. The only solution that I know of is a fresh install, what of course repeats every 3 months.
The text was updated successfully, but these errors were encountered: