search for: b3093cxxxxxx

...er P> ... perhaps someone here can explain? However what worked for me P> was using doveadm dsync-server on the 'receive' end. Maybe that P> puts it in 'listen' mode? So maybe try P> doveadm backup -u user at abc.net \ P> ssh root at po.abc.net \ P> docker exec b3093cxxxxxx doveadm dsync-server -u user at abc.net P> I've tried to get along with docker before, but it always just P> seems to add another level of complexity into everything, so thus P> far I've managed to avoid it apart from general experiments! P> P. P> On 15/05/2020 07.00, Gre...

So that was really helpful for me to understand that a lot more clearly. Thanks! [Many, many thanks @Plutocrat!!] But I'm still getting a similar failure. Let me give the command I'm using. doveadm backup -D -u user at abc.net \ ssh root at po.abc.net \ docker exec b3093cxxxxxx doveadm sync -D -u user at abc.net The "local" server is where the data/mail currently is. The remote or docker container/volume is where dovecot is installed. (The data is in a different docker container.) So, I think I'm "backing up" the data from the local machine and p...

...sync doveadm sync doveadm dsync-server ... perhaps someone here can explain? However what worked for me was using doveadm dsync-server on the 'receive' end. Maybe that puts it in 'listen' mode? So maybe try doveadm backup -u user at abc.net \ ssh root at po.abc.net \ docker exec b3093cxxxxxx doveadm dsync-server -u user at abc.net I've tried to get along with docker before, but it always just seems to add another level of complexity into everything, so thus far I've managed to avoid it apart from general experiments! P. On 15/05/2020 07.00, Gregory Sloop wrote: > So that...

...oduced by docker, and on file/container permissions, environment variables, paths etc. > > How about if you just try a simple doveadm command over ssh from the remote server to make sure that works. eg. from "Sending" server do > > ssh root at po.abc.net \ > docker exec b3093cxxxxxx doveadm user user at abc.net > > That should execute the doveadm user command on the remote (receiving) server. If that works, then at least you can satisfy yourself that the docker bit is working correctly. Not sure why I'm getting involved in someone else's troubleshooting nightmar...

...duced by docker, and on file/container permissions, environment variables, paths etc. >> How about if you just try a simple doveadm command over ssh from the remote server to make sure that works. eg. from "Sending" server do >> ssh root at po.abc.net \ >> docker exec b3093cxxxxxx doveadm user user at abc.net >> That should execute the doveadm user command on the remote (receiving) server. If that works, then at least you can satisfy yourself that the docker bit is working correctly. Not sure why I'm getting involved in someone else's troubleshooting nightmare...

...nd the complications introduced by docker, and on file/container permissions, environment variables, paths etc. How about if you just try a simple doveadm command over ssh from the remote server to make sure that works. eg. from "Sending" server do ssh root at po.abc.net \ docker exec b3093cxxxxxx doveadm user user at abc.net That should execute the doveadm user command on the remote (receiving) server. If that works, then at least you can satisfy yourself that the docker bit is working correctly. Not sure why I'm getting involved in someone else's troubleshooting nightmare! ;-) P...

...uced by docker, and on file/container permissions, environment variables, paths etc. >> How about if you just try a simple doveadm command over ssh from the remote server to make sure that works. eg. from "Sending" server do >> ssh root at po.abc.net \ >> docker exec b3093cxxxxxx doveadm user user at abc.net >> That should execute the doveadm user command on the remote (receiving) server. If that works, then at least you can satisfy yourself that the docker bit is working correctly. Not sure why I'm getting involved in someone else's troubleshooting nightmare...

...e/container permissions, environment variables, paths etc. > > >> How about if you just try a simple doveadm command over ssh from the remote server to make sure that works. eg. from "Sending" server do > > >> sshroot at po.abc.net\ > >> docker exec b3093cxxxxxx doveadm useruser at abc.net > > >> That should execute the doveadm user command on the remote (receiving) server. If that works, then at least you can satisfy yourself that the docker bit is working correctly. Not sure why I'm getting involved in someone else's troubleshootin...

So I've done quite a lot of searching on the list and on the web - and perhaps my google-fu is really bad - but I can't find any real recipes on how to sync mail from the old server to the new. As an FYI - the old server is a CPanel/WHM setup on a VPS. The new is mailcow - which uses docker. However, I don't think either of these platforms is what's causing the issue - but