imapsync
Full Sync possible?
Hey there. I have a hosting provider, who runs my public page and delivers my e-mails. However, I set up OpenXchange (and dovecot as IMAP server and postfix as MTA) in the local network. All outgoing mails are sent via the hosting provider, the incoming mails are fetched by imapsync from there. Works perfect, the benefit is that I do not have to care about the entire SPAM processing/detection/prevention. BUT: if I send a mail via OpenXchange/Thunderbird (you name it), the outgoing mail is placed into the folder "Sent" and is set back by the next run of imapsync (runs once per 5 mins). The same is true for reading and deleting the mails locally. Can I achieve a full sync (2-ways) with imapsync? Is more a feature request, hum?
I tried the mentioned offlineimap as well as doveadm sync, but they are not as simplified as imapsync with its structure (take this account of this server and sync it to this user of this server).
Two ways sync is impossible because imapsync is stateless. Each time imapsync runs, it considers messages and folders as if it was the first time it encounters them, it looks at messages and folders as they are now, not considering what they were before. Imapsync has no memory outside a run.
So why a stateless behavior cannot handle two ways sync between A and B? When a message is deleted from A, imapsync cannot know if it is a message deleted from A that has to be deleted in B or a message from B that has to be copied to A.
That said, I don't understand your issue yet. Why don't you use directly the hosting imap account?
That said, I don't understand your issue yet. Why don't you use directly the hosting imap account?
No worries :-)
One reason is the authentication. The hosted accounts use the auth system of the provider. It uses random usernames per mail account and the password cannot be changed easily by the user. The other reason is the traffic: several devices (laptop, tablet, smartphone) per user ask the service provider, now they ask locally with unified usernames and passwords.
The idea is: whatever happens to the service provider, it does not happen to me :-)
So why a stateless behavior cannot handle two ways sync between A and B? When a message is deleted from A, imapsync cannot know if it is a message deleted from A that has to be deleted in B or a message from B that has to be copied to A.
I see :-/ Guess I have to dive deeper into the other tools.
I see :-/ Guess I have to dive deeper into the other tools.
I'll be happy to know how they handle the two ways problem of a deleted message :-)
The idea is: whatever happens to the service provider, it does not happen to me :-)
Well, now I wonder why don't you use directly the local account?