Hi Oswald, On 5/31/20 2:08 PM, Oswald Buddenhagen wrote: > On Sat, May 30, 2020 at 08:03:30PM +0200, Uwe Kleine-König wrote: >> Is that what you intended? >> > certainly not. > to be able to help you i need to know a sufficient part of the mailbox > layout on both the server and the client, including examples of what you > *don't* want to sync (if anything). just give a list of paths, like the > output of 'find'.
Not sure how to report the IMAP structure with something like find, so
describing in some prose instead.
The remote side is a dovecot serving my Maildir in (I think) Mailbox++
format, that I have:
/home/$user/Maildir/{cur,new,tmp}
/home/$user/Maildir/.intlist.customer.AAA/{cur,new,tmp}
/home/$user/Maildir/.lists.barebox/{cur,new,tmp}
/home/$user/Maildir/.lists.linux-arm-kernel/{cur,new,tmp}
and I want to replicate that in (respectively)
/home/$user/Maildir/.work/{cur,new,tmp}
/home/$user/Maildir/.work.intlist.customer.AAA/{cur,new,tmp}
/home/$user/Maildir/.work.lists.barebox/{cur,new,tmp}
/home/$user/Maildir/.work.lists.linux-arm-kernel/{cur,new,tmp}
Does this give you the information you need?
Currently my .msyncrc looks as follows:
IMAPAccount work
Host ...
User ...
Tunnel ...
SSLType STARTTLS
IMAPStore work-remote
Account work
MaildirStore work-local
Path /home/uwe/Maildir/.work/.
Inbox /home/uwe/Maildir/.work
SubFolders Verbatim
Flatten .
Channel work-inbox
Master :work-remote:
Slave :work-local:
Create Both
Patterns *
SyncState *
CopyArrivalDate yes
Group work
Channel work-inbox
Best regards and thanks for your support
Uwe
signature.asc
Description: OpenPGP digital signature
_______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
