similar to: Doveadm-sync SSH practicalities

> If you mean https://wiki.dovecot.org/Tools/Doveadm/Sync the answers seem > implicit to what's been stated. Yes, I do mean that address, I read that page four times and was still none the wiser. <rant-mode>And to be completely frank with you, if documentation relies on "implicit" guesswork and expects the user to "read between the lines" then in my books it

Hi, The documentation is somewhat silent on this subject. What permissions does the SSH user need ? How associated does it need to be with things like dovecot directory ownership etc ? Obviously my dovecot daemon processes are running as restricted users with "nologin" shells etc., and I don't really want to go opening them up if I don't have to. So could someone kindly

Hi command im using command bellow on destination server rtying to make keep it in sync after initialy doing doveadm backup -R doveadm -Dv -o imapc_host=src.srv -o imapc_user=test at domain.tld -opop3c_user=test at domain.tld -o imapc_password='pass' -o pop3c_password='pass' -o mail_fsync=never -o mail_prefetch_count=20 sync -f -1 -R -u test at domain.tld imapc: Im using

Hi -- I'm used to dsync my two mailservers running 2.0.16. Today, I did upgrade one server to 2.1, and doveadm sync is throwing to following error: mail> doveadm sync -f -u test ssh vmail at remote-host.tld dsync -v -f -u test doveadm(test): Fatal: All your namespaces have a location setting. It should be empty (default mail_location) in the namespace to be converted. Same error with

Hello! dsync SSL still doesn't work for replication, so I've disabled it and tried to sync without. But I have a problem with temp directory. Is it possible to change path to temp folder? I don't want to set permissions but change temporary folder for replication. Thanks in advance. dovecot: doveadm: Error: safe_mkstemp(/tmp/dovecot.doveadm.) failed: Permission denied

Hi, Since I upgraded from 2.2.21 to 2.2.23, the user option -u seems to be ignored by doveadm sync, or at least it doesn't handle it correctly. If I run the following in the shell as user 'max': % doveadm sync -u foo at example.com -d doveadm(max): Error: User doesn't exist I get it to work if I set the USER environment variable to foo at example.com: % USER=foo at

Hi, I?m migrating an old Zarafa-installation to a dovecot using mdbox and sis on Debian Jessie. To copy over the emails, I use doveadm backup on the new box - or more precisely: vmail# doveadm -v -o imapc_user=$user -o imapc_password=$pass -o imapc_host=$host -o imapc_features=rfc822.size -o imapc_port=993 -o mailbox_list_index=no -o imapc_ssl_verify=no backup -R -x "Public folders*"

I'm no docker guru - so I'm more than a little out of my depth in this case. But clearly ssh is installed, because that's what I'm running, and the sshd allows a connect and I get a return from ls. So, it's working fine outside the container. And I only need to execute doveadm sync inside the container. [Because that's where docecot/doveadm is installed.] So, it sure

Hello, Currently doveadm tool can't be used with read-only source locations because it's trying to create lock files. I'd guess lock files shouldn't be necessary on a read-only media, because no one else is going to change anything while our doveadm instance is running anyway. Example: doveadm import -u test at example.com

Hi all, First sorry i really couldn't find it back been searching everywhere even the docs and its bit confusing. I am using # doveadm -D sync -u *@mydomain.net remote:myserver.net # which works perfect however for security reasons we now need to change the sshd port on the remote server. How do i tell doveadm to use a custom SSH port (would love to continue to use just the ssh

Most documents around there talk abour "dsync", but the modern way is "doveadm backup". This command is not documented in the wiki and there are a few details missing, like how to use it thru SSH. I am currently doing some tests about how to backup my mdbox. I can do tests in local using: $ doveadm backup -u jcea -m proveedores/dovecot mdbox:/tmp/aa/ This will

In the manual page this command is used for converting a mailbox doveadm sync -u test mdbox:~/mdbox -x INBOX -x INBOX/* Yet I am getting this error and the mdbox folder is not created. dsync-local(test): (version not received) doveadm(test): Fatal: execvp(mdbox:~/mdbox) failed: No such file or directory [@ dovecot]# doveconf | grep mail_locat mail_location =

Hi, I am trying to import a mail IMAP account using doveadm. Following https://serverfault.com/questions/605342/migrating-from-any-imap-pop3-server-to-dovecot I did it with: doveadm -D -v \ -o imapc_host=mail.oldserver.tld \ -o imapc_user=contact at domain.org \ -o imapc_password=xxxxxxx \ -o imapc_features=rfc822.size \ -o imapc_ssl=starttls \ -o

Hello, I'm trying to migrate mail accounts from an old server to a new one. As I need to migrate dozens of accounts which take about 1G each, I need to do stateful sync to make my migration in two times : 1 - I run a : doveadm -D -o mail_fsync=never -o imapc_user=user1 at olddomain.fr sync -s "" -R -1 -u user1 at newdomain.fr imapc: > /tmp/firstsync.log 2>&1 my

Hi, I'm experiencing serious issues using doveadm sync; mails are not replicating and/or mails are duplicating. I wanted to use this for migrating external mailboxes to my server (in order to overcome the time when some servers/clients still use the old server and some already my server, as described on <https://wiki2.dovecot.org/Tools/Doveadm/Sync>). Finally I was able to reproduce

Le 16/02/2015 20:40, Casey Stone a ?crit : > On Feb 13, 2015, at 3:42 PM, FUSTE Emmanuel <emmanuel.fuste at thalesgroup.com> wrote: > >> Le 13/02/2015 16:19, Casey Stone a ?crit : >>> On Feb 5, 2015, at 10:39 PM, Casey Stone <tcstone at caseystone.com> wrote: >>> >>>> Hello: >>>> >>>> I've been looking forward to

Hello: I've been looking forward to getting my mail server up to Dovecot 2.2+ to be able to use the sync mechanism. I run my own mail server just for myself, with a few different accounts, and want to keep a master and backup server in sync. I'm running the Ubuntu server 14.04.1 mail stack which features Dovecot 2.2.9 (and Postfix). My setup is to use system users (userdb passwd /

>> On 15/05/2020 07:10 Plutocrat <plutocrat at gmail.com> wrote: >> >> On 15/05/2020 10.56, Gregory Sloop wrote: >> > IMAP sync looks better and better. I'm a little puzzled why I don't just give up walking on the broken glass and use it - but it just bugs the heck out of me. >> If you can get the dovecot native sync to work, it seems to be a

> On 15/05/2020 07:10 Plutocrat <plutocrat at gmail.com> wrote: > > > On 15/05/2020 10.56, Gregory Sloop wrote: > > IMAP sync looks better and better. I'm a little puzzled why I don't just give up walking on the broken glass and use it - but it just bugs the heck out of me. > > If you can get the dovecot native sync to work, it seems to be a better option,

Dear all, I successfully migrated hundreds of mailboxes with Dovecot 2.2.24 on OpenBSD 6.0 (amd64. Old server is OpenBSD 5.1, i386, Dovecot-2.0.17), but got error while migrating 3 mailboxes: # doveadm -o mail_fsync=never sync -1 -R -s '' -u user at domain.com imapc: dsync(user at domain.com): Panic: file mailbox-alias-plugin.c: line 77 (mailbox_symlink_exists): assertion failed: (ret