I am sorry, I mixed that up, you are right, you cannot switch both hosts.

Anyways, it syncs both hosts, and therefore it syncs in both directions by default.
So there is no need to switch the 2 hosts.
Thats why its called imapsync, and not imapcopy 😉

    worryboy

    Ah yes, you are using the other direction. Imapsync can’t properly 2-way sync:
    https://imapsync.lamiral.info/#CANTDO

    Imapsync is not suitable for maintaining a synchronization between two active imap accounts while the user is working on both sides. See why in the Two Ways Sync document. Use offlineimap (written by John Goerzen) or mbsync (written by Michael R. Elkins) for bidirectional (2 ways) synchronizations.

    As you cannot easily modify the sync jobs the other way around in mailcow, it seems you need to do this outside of mailcow.
    Try this:
    https://hub.docker.com/r/gilleslamiral/imapsync/

        esackbauer

        this may work but as “KarstenDE” wrote

        "Benefit of the existing solution is that I do not need the passwords of the existing mailcow mailboxes.
        Is it possible to change the used commandline?"
        .. i.e. via cron job

          21 days later

          esackbauer

          will work but evry update this will be reverted or ?
          on the other and only that way will work , sync in dosent work anymore

              worryboy
              Of course it would not survive an update.
              Another solution is to use an imapsync container outside of mailcow. You lose the integration, but you get all the flexibility.

                  esackbauer

                  sure , but as KarstenDE wrote the integration is the Plus of mailcow. “Benefit of the existing solution is that I do not need the passwords of the existing mailcow mailboxes.”

                  how can i request a feature ?

                      No one is typing