similar to: doveadm sync only creates directories, don't sync messages?

Displaying 20 results from an estimated 40000 matches similar to: "doveadm sync only creates directories, don't sync messages?"

2013 Sep 25
1
still having dsync issues after upgrading to latest
Trying to migrate a bunch of users with mbox format to maildir format. dsync creates some directories, but otherwise does nothing. (Complained about the lack of "/" as separator until I added that to config, now is silent when running dsync except with the -D flag) I have tried dumping all the dovecot that came with my OS and built the latest sources, hoping I'd at least get a
2015 Mar 13
0
doveadm sync subscribed folders only
Heya, is there a simple way to use "doveadm sync" for subscribed folders only? Since the migration from UW-IMAP, our users can actually subscribe to non-mbox files and now, when we are pushing new servers out, we are migrating our mboxes to dbox format and we would like to migrate only subscribed folders. I know, there is a -m switch which can be used to transfer subscribed
2014 Sep 29
0
"doveadm backup/sync" don't follow message moving even with MDBOX
Using mdbox as the storage backend, moving a message from a mailbox to another just update a reference. The message is not fisically moved on the disk. I would expect "dsync" to use this fact when source and destination are mdbox. But it doesn't. Anybody else can confirm?. Any plan to implement it?. Thanks!. -- Jes?s Cea Avi?n _/_/ _/_/_/
2014 Dec 01
0
Panic: from mbox-sync.c; doveadm zlib-plugin
Upgraded to dovecot 2.2.15 (built from sources on Fedora linux), saw intermittent panics: From dovecot:imap Error: Next message unexpectedly corrupted in mbox file /home/xxxx/mail/Junk E-mail at 1202197 Panic: file mbox-sync.c: line 152 (mbox_sync_read_next_mail): assertion failed: (sync_ctx->input->v_offset != mail_ctx->mail.from_offset || sync_ctx->input->eof) Error: Raw
2011 Sep 22
2
doveadm mailbox list shows file system directories as mailboxes
Hello. In our dovecvot we use mbox format with the default filesystem layout. Therefore it is not possible to have mailboxes which are subfolders of other mailboxes containing messages. The command "doveadm mailbox list" includes the file system directories, that contain only subfolders, as normal mailboxes in the output: archiv archiv/daemon archiv/dovecot Did I miss something
2019 May 13
0
Doveadm sync, Error: read(remote) failed: EOF, Error: read(remote) failed: EOF
<!doctype html> <html> <head> <meta charset="UTF-8"> </head> <body> <div> Hi, you need to put mdbox parameter as last. </div> <div> <br> </div> <div> Aki </div> <blockquote type="cite"> <div> On 13 May 2019 18:55 Marc Roos via dovecot < <a
2013 Jun 10
1
doveadm index crashes when indexing shared mailboxes
Hi, We store our mail archive in a tree of subfolders. I am trying to speed up text searching on our mail archive but when running "doveadm -D -v index -u neil shared/Exalon/Aandeelhouders" the following output is produced: doveadm(neil): Debug: Loading modules from directory: /usr/lib/dovecot/modules doveadm(neil): Debug: Module loaded:
2019 May 13
2
Doveadm sync, Error: read(remote) failed: EOF, Error: read(remote) failed: EOF
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 =
2013 Feb 26
1
dsync can't sync mbox2mdbox two times
Hi, I have a server with Dovecot 2.1.x and I'm trying to convert mbox-storages to mdbox-storages. # 2.1.7: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-amd64 x86_64 Debian 6.0.7 mail_location = mbox:~/mail During the first run everything's okay, but if I run the migration a second time, the later migration is broken: root at mailstore1:/srv/vmail/cklein# rm -R mdbox/ root at
2015 Nov 17
0
doveadm import/sync with read-only source location
+1 to that idea. Ask the same couple month before during migration from 1.x to 2.x but got no answer from someone who able to change this. On Tue, 17 Nov 2015 10:35:11 +0200 Teodor Milkov <tm at del.bg> wrote: > 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
2015 Nov 17
2
doveadm import/sync with read-only source location
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
2019 Aug 26
1
doveadm mailbox handling for directory only
2016 Apr 11
2
doveadm sync ignores -u option
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
2014 Jun 18
1
Problem syncing mailboxes using doveadm sync
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
2016 Dec 18
1
Error while migrating mailbox with 'doveadm sync'
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
2020 May 15
1
doveadm sync backup from old to new server
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
2014 Nov 18
1
custom ssh port doveadm sync
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
2016 Apr 05
2
doveadm sync -1 -R
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*"
2012 Feb 18
3
Failing: doveadm sync <--remote host--> dsync mirror
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
2017 Aug 04
0
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