-
-
Notifications
You must be signed in to change notification settings - Fork 363
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
Can't copy external mail older than maxage to local maildir (related to 681e27) #581
Comments
I'd say that's what maxage is all about : "ignore emails older than maxage". I understand that this is not what you want in this case. Having exceptions for maxage is implemented. |
The problem is that it isn't ignoring the local email-- it's deleting it. I think the right behavior would be for it to ignore the email on step 2. But if it doesn't do that (and instead treats this as "new" on the local side) then it should treat both local and remote copies as "new". Instead, it is treating one as new and one as old, which is causing the local one to be deleted. As it stands, I can't copy old emails to my inbox because offlineimap deletes them. |
I think this issue could be related to 0d6a9a4. What is the version of offlineimap with the expected behaviour? |
I think it's actually 681e27. It's wrong in version 7.1.4 (which looks like is before the commit you mentioned was included) as well as in every subsequent release, but fixed if you revert 681e27 in version 7.1.4. (I can't test with that commit reverted in a later release because stuff seems to have changed around it and it no longer reverts cleanly.) |
It can't be 681e27 because this commit doesn't touch code and is not a merge. Reverting this commit won't change anything. Does it work as expected with v7.1.3? |
Github-ref: OfflineIMAP#581 Signed-off-by: Nicolas Sebrecht <nicolas.s-dev@laposte.net>
Could you please test this patch : nicolas33@db2547d |
Notice: the expected behavior with this patch is to upload the copied email even when older than maxage because it's considered new in the maildir. However, there should be no more deletion once the folder is synced. |
That fixes the issue for me! (tested on version 7.2.1) |
Github-ref: #581 Tested-by: https://github.com/ianbrody Signed-off-by: Nicolas Sebrecht <nicolas.s-dev@laposte.net>
Thank you much. Applied. |
General information
offlineimap -V
): 7.2.1Configuration file offlineimaprc
Steps to reproduce the error
Desired behavior: offlineimap shouldn't be looking at this email at all, because it's older than maxage.
If I downgrade to 7.1.4, this behavior still happens, and if I revert commit 681e27 there, the problem goes away (nothing is copied, and nothing is deleted). I believe this commit is at fault in the more recent versions, but it seems something else has changed around it, and I can't revert cleanly.
Log messages
Running with -d imap,maildir,thread I get
on the first run, and
on the second run. Note that 21-Aug-2010 00:04:35 -0500 is the date of the message copied.
The text was updated successfully, but these errors were encountered: