Skip to content
This repository has been archived by the owner on Apr 20, 2022. It is now read-only.

dsync and larch don't do the same thing #47

Open
taoeffect opened this issue Nov 23, 2014 · 3 comments
Open

dsync and larch don't do the same thing #47

taoeffect opened this issue Nov 23, 2014 · 3 comments

Comments

@taoeffect
Copy link
Owner

taoeffect commented Nov 23, 2014

Larch will preserve the INBOX. prefix that's found on many servers, whereas dsync, with the way we're using it, won't. This will result in a situation where if both methods are used to sync mail, a whole bunch of duplicate folders will be created.

Meaning, larch will create .INBOX.foobar and dsync will create .foobar.

Since larch does this on its own and there doesn't seem to be a way to fix it, I think we should change dsync to behave like larch does (since I'm guessing that's a possibility).


Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

@taoeffect
Copy link
Owner Author

I honestly don't know what the "proper" behavior here is, and it doesn't help that I have no idea why these INBOX. folders are created in some instances and not in others.

@bgw
Copy link
Collaborator

bgw commented Nov 28, 2014

The INBOX folders seem unnecessary, and we could use the --to-folder option to remove it. I think doing so would fix #50 and #52. I would like to verify first though, that for accounts that aren't migrated, dovecot won't produce the INBOX folder automatically. As far as I can tell, it shouldn't.

@taoeffect
Copy link
Owner Author

The INBOX folders seem unnecessary, and we could use the --to-folder option to remove it.

How exactly would that work? The default for larch is INBOX, and we're using --all which seems to possibly be mutually exclusive to that..?

See also this comment.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants