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
APPEND issue... #262
Comments
Could you please provide your configuration file? Remove private data! |
[general] [Account Exchange] [Repository Local] [Repository Remote] [Account SLI] [Repository Local-SLI] [Repository Remote-SLI] [Account TOP] [Repository Local-TOP] [Repository Remote-TOP] [Account JMI] [Repository Local-JMI] [Repository Remote-JMI] [Account Shopping] [Repository Local-Shopping] [Repository Remote-Shopping] [Account Stuff] [Repository Local-Stuff] [Repository Remote-Stuff] |
I wonder if there's a bug around |
I tried and that didn't solve the problem. It's definitely an issue with large files. In the past, it was an email with a 23mb attachment; this time it's an email with an 20mb attachment. Offlineimap keeps duplicating the file as it fails to copy it. For instance, at this point, I have 5 copies of that 20mb file in one of my folders. The duplicates are 100% from offlineimap as I (obviously) only sent the file once. Specifically: I sent the file from my regular server; offlineimap synced it to Gmail; as of now, there are 5 copies of the file on my server and 1 copy in Gmail. The duplicates that offlineimap created and the fact that there are 5 copies on one server and only 1 on the other must be confusing the program in some way and causing it to throw the error, right? As I noted, I've had this problem with other large files. Unfortunately, the only solution is to delete the files from both servers, which, frankly, isn't much of a solution really. |
Hello, I too experience this issue and can provide information if needed. I see similar behavior, but I think it doesn't depend on the file size but on the uploading time. I had bad connection yesterday, so the bug triggered even on 2mb attachment. Now I see the message copied 119 times :) What is more funny is that the messages are fully copied, it's only the offlineimap who thinks it didn't succeed in uploading. Relevant part from the logfile (with extra linebreaks to fit into the column:
Thank you for taking the time for this issue and all your work on offlineimap! |
There was a fix about APPEND, very recently. Please try git Needing logs with imap debug logs enabled. |
I've just released v6.6.0 so you could use this. :-) |
I tried v6.6.0, but it still crashes. I tried sending an email with 18mb attachment and increasing timeout. But still no luck. Detailed log can be found here: https://www.dropbox.com/s/dcjoo7yxzary1kk/append_issue.log?dl=0 |
OMG. 93Mo is a lot. If the issue is reproducible, please try a new run until there's almost only the issue left is the logs. |
Quite old. Please, open a new issue if still valid. |
Still happening. In my case I had a message that was 40MB and I wanted to move it from my inbox folder to the archive folder. After some time I always get:
Looks to me like the transfer takes >120 sec (quite an arbitrary time) and offlineimap doesn’t tell the server it’s still transferring, so the server aborts. |
@Profpatsch Please, open a new issue. |
I opened this issue which we closed recently because nothing had happened with it in a while (#172). Well, it's back, and I'm 99.9999% sure I know the source of the problem (though not the solution): large file attachments. I sync from an Exchange server to Gmail and both of them have an attachment limit of 25mb. Syncing a 20mb will trigger the error. I haven't tested to see if there's a max file size offlineimap can sync without triggering the error, but if I had to take a guess, it's any file size that takes less than 60 seconds to sync because when the syncing goes on longer than 60 seconds, offlineimap (I think) thinks it's timing out.
Does this make sense? And, in a practical sense, is there a way to either: (a) tell offlinimap to ignore attachments above a certain size, (b) manually mark a message as "synced" so that offlineimap will ignore that particular message in the future, or (c) something else so that offlineimap doesn't crash when it hits very large attachments that take an unusually long time to either upload or download to or from the syncing servers?
The text was updated successfully, but these errors were encountered: