Re: doveadm backup empties the remote host? SERIOUSLY???

On 4/27/24 16:30, Nils via dovecot wrote: I have a file backup and since that backup, new emails have been received. Also, not all of the emails were deleted - many folders weren't affected. Additionally I was able to restore a few of the deleted emails with ext4magic. So now I have three

Re: doveadm backup empties the remote host? SERIOUSLY???

> On 29/04/2024 12:02 EEST Nils via dovecot wrote: > > > On 4/27/24 16:30, Nils via dovecot wrote: > > I have a file backup and since that backup, new emails have been > > received. Also, not all of the emails were deleted - many folders > > weren't affected. Additionally I was able to

Re: doveadm backup empties the remote host? SERIOUSLY???

On 4/27/24 16:30, Nils via dovecot wrote: I have a file backup and since that backup, new emails have been received. Also, not all of the emails were deleted - many folders weren't affected. Additionally I was able to restore a few of the deleted emails with ext4magic. So now I have three

Re: doveadm backup has problems with some accounts

Because, that perhaps the version missmatch of the servers coul'd be the issue , and centos 7 eol comes in two months, i setup a complete new main mailserver, based on ubuntu 22.04 (24.04 was not out on starting to setup the stuff) so now both servers had dovecot 2.3.16. But it doesn't help,

Re: doveadm backup empties the remote host? SERIOUSLY???

On 4/27/24 12:31, Aki Tuomi via dovecot wrote: Yeah. Backup command, without -R backs to location, not from location. Mailman archive is athttps://www.dovecot.org/mailman3/mailman3/lists/ Aki ___ dovecot mailing list --dovecot@dovecot.org To

Re: doveadm backup empties the remote host? SERIOUSLY???

doveadm service on the old server and then call "doveadm backup -Ru username tcp:host:port" on the new server? So the reason that doveadm deleted everything yesterday was that I forgot the -R option?   "The doveadm backup command forces the destination

Re: doveadm backup empties the remote host? SERIOUSLY???

On 4/26/24 14:04, Aki Tuomi wrote: We have migration guide, see https://doc.dovecot.org/admin_manual/migrating_mailboxes/ Aki regarding this guide: I am supposed to set up doveadm service on the old server and then call "doveadm backup -Ru username tcp:host:port" on the new

doveadm backup empties the remote host? SERIOUSLY???

This is the magic incantation I use: #> doveadm -o mail_fsync=never -R -u u...@foo.bar imapc: ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org

RE: doveadm backup empties the remote host? SERIOUSLY???

> > Sure it's my own fault - no discussion about that, but seriously? How > dangerously unintuitive it that? > I don't really get what is going on with remote host. How is a host name even relevant other than setting up the initial connection. I don't even see it in my storage mail files.

Re: doveadm backup empties the remote host? SERIOUSLY???

  On 26/04/2024 14:46 EEST Nils via dovecot wrote:     Sure it's my own fault - no discussion about that, but seriously? How dangerously unintuitive it that?   I found it when I was searching for a good practice to migrate a mail server with rsync and

doveadm backup empties the remote host? SERIOUSLY???

Sure it's my own fault - no discussion about that, but seriously? How dangerously unintuitive it that? I found it when I was searching for a good practice to migrate a mail server with rsync and I mistakably assumed it works in the same direction as rsync. Luckily i have a backup from all

doveadm-backup and quota question

because of 'over quota'. Here is an example: # doveadm quota get -u i...@domain.abc Quota name   Type    Value Limit % User quota   STORAGE 16798 16777216 0 User quota   MESSAGE   628 - 0 Domain quota STORAGE 32282 67108864 0 Domain quota MESSAGE   645 - 0 [root@vmi792826 ~]# doveadm backup -u i

Re: doveadm backup has problems with some accounts

: Error: Mailbox INBOX sync: >> mailbox_delete failed: INBOX can't be deleted. > The other 450 accounts on the server have no issue and doveadm backup works > as expected. > I don't have any special namespaces configured on the server or acls. The > server is a simple set

Re: doveadm backup has problems with some accounts

> On 01/12/2023 11:34 EET roger.meier--- via dovecot > wrote: > > > I try to setup for our mailserver (in a dc) a job backup to a secondary > server (in our office) with "doveadm backup" via the -R option. (rsync , > rsnapshot and so on tooks too long at the

doveadm backup has problems with some accounts

I try to setup for our mailserver (in a dc) a job backup to a secondary server (in our office) with "doveadm backup" via the -R option. (rsync , rsnapshot and so on tooks too long at the moment) For the most user accounts all work as expected, but for three users it always fails

Re: Bug - doveadm backup out-of-memory kill/crash when no separators set

James Harrison wrote: > I hit a fun issue with doveadm when migrating from dovecot 2.2.36 > (1f10bfa63) to 2.3.19.1 (9b53102964) (CentOS 7 to Debian 12). > When running doveadm -v -D backup -R -u "user@name" tcp:localhost:1234, > I found that the first sync would always work, but subsequent runs

Bug - doveadm backup out-of-memory kill/crash when no separators set

inbox namespace. Having identified the convert_name_to_remote_sep function as the likely trigger point I set the separator to / on both ends, and doveadm backup now runs without issue. Can provide config if helpful but I think probably irrelevant to this one - the namespace config is the default

Doveadm backup stateful synchronization trouble

, but not each time. The command I used for the first time is : doveadm backup -A -s "" -d > state.txt After that there is a daily calls (as vmail user, my config only handle virtual users) to : doveadm backup -A -s "$( state.txt.tmp && mv state.txt.tmp state.txt doveconf -n out

Re: doveadm backup|sync works for every folder but INBOX

Hi Aki, Am 08.11.22 um 12:02 schrieb Ralf Becker: Hi Aki, Am 08.11.22 um 10:07 schrieb Aki Tuomi: I send the full log again to your private address. Ralf Seems I can reproduce this issue, we'll look into this. Aki Hi! Can you try if

Re: doveadm backup|sync works for every folder but INBOX

Hi Aki, Am 08.11.22 um 10:07 schrieb Aki Tuomi: I send the full log again to your private address. Ralf Seems I can reproduce this issue, we'll look into this. Aki Hi! Can you try if

Re: doveadm backup|sync works for every folder but INBOX

> > I send the full log again to your private address. > > > > Ralf > > > > Seems I can reproduce this issue, we'll look into this. > > Aki Hi! Can you try if https://github.com/dovecot/core/compare/a485443e00a7e1b93ed9b7d065c89fcd2eb90865%5E..0f67c79e48fa783b658606a99cf18db8daf7884e.patch

Re: doveadm backup|sync works for every folder but INBOX

/2022 09:46 EET Ralf Becker wrote: I'm trying to migrate an old Cyrus 2.5 server to Dovecot 2.3.19 using doveadm backup -R, which works for all folders but the INBOX itself, which always stays empty. The Cyrus side uses altnamespace:no and unixhierarchysep:no, it's used as imapc: remote

Re: doveadm backup|sync works for every folder but INBOX

;> Am 03.11.22 um 09:12 schrieb Aki Tuomi: > >>>>>>>>> On 03/11/2022 10:09 EET Ralf Becker wrote: > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> Hi Aki, > >>>

Re: doveadm backup|sync works for every folder but INBOX

to Dovecot 2.3.19 using doveadm backup -R, which works for all folders but the INBOX itself, which always stays empty. The Cyrus side uses altnamespace:no and unixhierarchysep:no, it's used as imapc: remote in doveadm backup -R with imapc_list_prefix=INBOX Dovecot uses the following namespace

Re: doveadm backup|sync works for every folder but INBOX

gt; >>>> > > >>>> Am 03.11.22 um 09:12 schrieb Aki Tuomi: > > >>>>>> On 03/11/2022 10:09 EET Ralf Becker wrote: > > >>>>>> > > >>>>>> > > >>>>>> Hi Aki,

Re: doveadm backup|sync works for every folder but INBOX

2 10:09 EET Ralf Becker wrote: > >>>>>> > >>>>>> > >>>>>> Hi Aki, > >>>>>> > >>>>>> Am 03.11.22 um 08:50 schrieb Aki Tuomi: > >>>>>>>> On 03/11/2022 09:46 EET Ralf Becker wrote

Re: doveadm backup|sync works for every folder but INBOX

: Hi Aki, Am 03.11.22 um 08:50 schrieb Aki Tuomi: On 03/11/2022 09:46 EET Ralf Becker wrote: I'm trying to migrate an old Cyrus 2.5 server to Dovecot 2.3.19 using doveadm backup -R, which works for all folders but the INBOX itself, which always stays empty. The Cyrus side uses

Re: doveadm backup|sync works for every folder but INBOX

Hi Aki, Am 03.11.22 um 08:50 schrieb Aki Tuomi: On 03/11/2022 09:46 EET Ralf Becker wrote: I'm trying to migrate an old Cyrus 2.5 server to Dovecot 2.3.19 using doveadm backup -R, which works for all folders but the INBOX itself, which always stays empty. The Cyrus side uses

Re: doveadm backup|sync works for every folder but INBOX

:12 schrieb Aki Tuomi: > >>>> On 03/11/2022 10:09 EET Ralf Becker wrote: > >>>> > >>>> > >>>> Hi Aki, > >>>> > >>>> Am 03.11.22 um 08:50 schrieb Aki Tuomi: > >>>>>> On 03/11/2022 09:46 EET Ralf Bec

Re: doveadm backup|sync works for every folder but INBOX

: I'm trying to migrate an old Cyrus 2.5 server to Dovecot 2.3.19 using doveadm backup -R, which works for all folders but the INBOX itself, which always stays empty. The Cyrus side uses altnamespace:no and unixhierarchysep:no, it's used as imapc: remote in doveadm backup -R with imapc_list_prefix

Re: doveadm backup|sync works for every folder but INBOX

:50 schrieb Aki Tuomi: > >>>> On 03/11/2022 09:46 EET Ralf Becker wrote: > >>>> > >>>> > >>>> I'm trying to migrate an old Cyrus 2.5 server to Dovecot 2.3.19 using > >>>> doveadm backup -R, which works for all folders but the INBOX it

Re: doveadm backup|sync works for every folder but INBOX

Hi Aki, Am 03.11.22 um 09:12 schrieb Aki Tuomi: On 03/11/2022 10:09 EET Ralf Becker wrote: Hi Aki, Am 03.11.22 um 08:50 schrieb Aki Tuomi: On 03/11/2022 09:46 EET Ralf Becker wrote: I'm trying to migrate an old Cyrus 2.5 server to Dovecot 2.3.19 using doveadm backup -R, which

Re: doveadm backup|sync works for every folder but INBOX

> On 03/11/2022 10:09 EET Ralf Becker wrote: > > > Hi Aki, > > Am 03.11.22 um 08:50 schrieb Aki Tuomi: > >> On 03/11/2022 09:46 EET Ralf Becker wrote: > >> > >> > >> I'm trying to migrate an old Cyrus 2.5 server to Dovecot 2.3.19 usi

Re: doveadm backup|sync works for every folder but INBOX

Hi Aki, Am 03.11.22 um 08:50 schrieb Aki Tuomi: On 03/11/2022 09:46 EET Ralf Becker wrote: I'm trying to migrate an old Cyrus 2.5 server to Dovecot 2.3.19 using doveadm backup -R, which works for all folders but the INBOX itself, which always stays empty. The Cyrus side uses

Re: doveadm backup|sync works for every folder but INBOX

> On 03/11/2022 09:46 EET Ralf Becker wrote: > > > I'm trying to migrate an old Cyrus 2.5 server to Dovecot 2.3.19 using > doveadm backup -R, which works for all folders but the INBOX itself, > which always stays empty. > > The Cyrus side uses altnamespace:no and u

doveadm backup|sync works for every folder but INBOX

I'm trying to migrate an old Cyrus 2.5 server to Dovecot 2.3.19 using doveadm backup -R, which works for all folders but the INBOX itself, which always stays empty. The Cyrus side uses altnamespace:no and unixhierarchysep:no, it's used as imapc: remote in doveadm backup -R

Re: Having an issue migrating mailboxes with the doveadm backup tool...

emails, > and we're trying to do so with the doveadm backup tool - figuring that it > will probably "do" Dovecot better than a generic IMAP to IMAP tool. So far, > no dice - we get the following error message: > > Jul 13 16:00:00 doveadm(u...@example.com): Fatal: Al

Having an issue migrating mailboxes with the doveadm backup tool...

server is running dovecot. We need to get these users cleanly migrated over, with all of their emails, and we're trying to do so with the doveadm backup tool - figuring that it will probably "do" Dovecot better than a generic IMAP to IMAP tool. So far, no dice - we get the following err

Re: Doveadm backup...

> "Sami" == Sami Ketola writes: >> On 27. Mar 2022, at 23.09, John Stoffel wrote: >> >>> "Stephane" == Stephane Magnier writes: >> >> Sorry, I deleted your most recent email post before I could reply. >> But why don't you just do 'imapsync' instead from your production >> dovecot box

Re: Doveadm backup...

> On 27. Mar 2022, at 23.09, John Stoffel wrote: > >> "Stephane" == Stephane Magnier writes: > > Sorry, I deleted your most recent email post before I could reply. > But why don't you just do 'imapsync' instead from your production > dovecot box to some other backup system? Otherwise

Re: Doveadm backup...

; I'm not sure what you are attempting to do here. It looks like you just ran a doveadm backup Stephane> and the process completed for userx with a warning that the remote system (your nfs mount) Stephane> lost a particular mailbox (possibly your indexes changed or a mailbox was de

Re: Doveadm backup...

t to discover it while running into trouble.. Stephane> On 2/28/22 19:03, Ben Burk wrote: Stephane> I'm not sure what you are attempting to do here. It looks like you just ran a doveadm backup Stephane> and the process completed for userx with a warning that the remote system

Re: Doveadm backup...

Hi Stephen, Does it work if you delete the Maildir/ on the destination first and then initiate the backup? I ran into this problem recently - see my post on 21 Feb.  Looks very similar if not the same root cause. On 1/03/2022 6:46 am, Stephane Magnier wrote: I've seen in a previous

Re: Doveadm backup...

to do here. It looks like you just ran a doveadm backup and the process completed for userx with a warning that the remote system (your nfs mount) lost a particular mailbox (possibly your indexes changed or a mailbox was deleted). From the logs you pasted it appears the process completed normally. I

Re: Doveadm backup...

I'm not sure what you are attempting to do here. It looks like you just ran a doveadm backup and the process completed for userx with a warning that the remote system (your nfs mount) lost a particular mailbox (possibly your indexes changed or a mailbox was deleted). From the logs you pasted

Re: Doveadm backup...

nally NOT to do a backup ( Doveadm backup ) but a replication process ? ( https://wiki.dovecot.org/Replication  ) ? On 2/28/22 06:24, Ben Burk wrote: Did you try running dsync? On 2/27/22 23:15, Stephane Magnier wrote: HI, Any idea ? Any clue ? On 2/25/22 21:50, Stephane Magnier wrote: Hi

Re: Doveadm backup...

Did you try running dsync? On 2/27/22 23:15, Stephane Magnier wrote: HI, Any idea ? Any clue ? On 2/25/22 21:50, Stephane Magnier wrote: Hi I've recently tried to use the Dovecadm backup to backup the emails..  with the following syntax doveadm -Dv backup -u userx

Re: Doveadm backup...

HI, Any idea ? Any clue ? On 2/25/22 21:50, Stephane Magnier wrote: Hi I've recently tried to use the Dovecadm backup to backup the emails..  with the following syntax doveadm -Dv backup -u userx maildir:/mnt/nfs-backup/userx Sounds to be OK with few emails... Some of them got a lot of

Doveadm backup...

Hi I've recently tried to use the Dovecadm backup to backup the emails..  with the following syntax doveadm -Dv backup -u userx maildir:/mnt/nfs-backup/userx Sounds to be OK with few emails... Some of them got a lot of emails and one f them got an error and stop ! dsync(userx): Debug:

Re: doveadm backup : Warning: Deleting mailbox GUID= is missing locally

> On 27. Jan 2022, at 19.32, Laura Smith > wrote: > > So I should not be using "-R" with "doveadm backup" then ? > > For "-R" the docs say "will instead pull messages from the remote to the > local storage." > > for &qu

Re: doveadm backup : Warning: Deleting mailbox GUID= is missing locally

docs (https://wiki.dovecot.org/Tools/Doveadm/Sync) I'm presently > > running doveadm backup multiple times with a view to eventual server > > migration. > > > > I am seeing messages such as this: > > > > Warning: Deleting mailbox 'Junk': UID=1826 GUID= is missi

Re: doveadm backup : Warning: Deleting mailbox GUID= is missing locally

> On 27. Jan 2022, at 16.27, Laura Smith > wrote: > > Hi, > > As per the docs (https://wiki.dovecot.org/Tools/Doveadm/Sync) I'm presently > running doveadm backup multiple times with a view to eventual server > migration. > > I am seeing messages such as thi

doveadm backup : Warning: Deleting mailbox GUID= is missing locally

Hi, As per the docs (https://wiki.dovecot.org/Tools/Doveadm/Sync) I'm presently running doveadm backup multiple times with a view to eventual server migration. I am seeing messages such as this: Warning: Deleting mailbox 'Junk': UID=1826 GUID= is missing locally Is it anything to worry about

doveadm backup Error: Mailbox INBOX sync

Hi, the command  "doveadm  backup -u {user@mail} maildir:/home/backup/{user@mail}/mails/" returns the following error : dsync(user@mail): Error: Mailbox INBOX sync: mailbox_delete failed: INBOX can't be deleted. ...and nothing in dovecot logs  dovecot actual version 2.3.

Re: migration with doveadm backup to new cluster running dovecot 2.2.36 and replicator

When doing migration, it is very useful to construct a temporary dovecot-migration.conf which lacks *any* automatic mailbox creation and has only the bare minimum you need (sieve needs to be configured, and mailbox attributes). This means no autocreate/autosubscribe loaded, and no

Re: migration with doveadm backup to new cluster running dovecot 2.2.36 and replicator

> > >>> Please try to migrate with the same format. > >>> > >>> Andrea > >>> > >>> Il 05/01/21 15:02, Thomas Winterstein ha scritto: > >>>> No one? > >>>> > >>>> If there are limitations in reg

Re: migration with doveadm backup to new cluster running dovecot 2.2.36 and replicator

(maildir) to 2.2.36 (mdbox). The new cluster has two backend mail servers which replicate through doveadm replicator. To move the data initially we use doveadm backup (imapc). arb Our migration command    doveadm -o mail_fsync=never backup -R -u $user imapc: To test the replication of new and purge

Re: migration with doveadm backup to new cluster running dovecot 2.2.36 and replicator

has two backend mail servers which replicate through doveadm replicator. To move the data initially we use doveadm backup (imapc). arb Our migration command   doveadm -o mail_fsync=never backup -R -u $user imapc: To test the replication of new and purge of old mails with live data changes we ran

Re: migration with doveadm backup to new cluster running dovecot 2.2.36 and replicator

> > documentation. > > > > On 23.12.2020 20:33, Thomas Winterstein wrote: > >> Hello everyone, > >> > >> > >> we are working on migrating from dovecot 2.0.9 (maildir) to 2.2.36 > >> (mdbox). The new cluster has two backend mail servers which

Re: migration with doveadm backup to new cluster running dovecot 2.2.36 and replicator

luster has two backend mail servers which replicate >> through doveadm replicator. To move the data initially we use doveadm >> backup (imapc). >> >> arb >> Our migration command >>   doveadm -o mail_fsync=never backup -R -u $user imapc: >> >> >> To t

Re: doveadm backup only working once?

o  Mon Jan 04 17:56   29/1016  Testmail 1 > >>>  U  2 torrem...@mail.to  Mon Jan 04 17:56   28/982   Testmail 2 > >>> > >>> After the 2nd backup command (same command) it contains: > >>> > >>> root@server2:/var/mail# mail -f synctest >

Re: doveadm backup only working once?

/1016 Testmail 1 > >>> U 2 torrem...@mail.to Mon Jan 04 17:56 28/982 Testmail 2 > >>> > >>> After the 2nd backup command (same command) it contains: > >>> > >>> root@server2:/var/mail# mail -f synctest > >>> Mail

Re: doveadm backup only working once?

R INTERNAL DATA Looks like for some reason the inbox file is reset/recreated? Anybody any idea what could cause this behaviour? Running the doveadm backup command a 3rd of 4th time does not change the /var/mail/synctest file anymore. Also the date/time of the file is not updated anymore I can't hel

Re: doveadm backup only working once?

t; >Mail version 8.1.2 01/15/2001.  Type ? for help. > >"synctest": 1 message > >>   1 MAILER-DAEMON@ser  Wed Jan 06 14:05   13/534   DON'T DELETE THIS > >MESSAGE -- FOLDER INTERNAL DATA > > > >Looks like for some reason the inbox file is reset/

Re: doveadm backup only working once?

il -f synctest >Mail version 8.1.2 01/15/2001.  Type ? for help. >"synctest": 1 message >>   1 MAILER-DAEMON@ser  Wed Jan 06 14:05   13/534   DON'T DELETE THIS >MESSAGE -- FOLDER INTERNAL DATA > >Looks like for some reason the inbox file is reset/recreated? A

Re: doveadm backup only working once?

DON'T DELETE THIS MESSAGE -- FOLDER INTERNAL DATA Looks like for some reason the inbox file is reset/recreated? Anybody any idea what could cause this behaviour? Running the doveadm backup command a 3rd of 4th time does not change the /var/mail/synctest file anymore. Also the date/time of the f

Re: migration with doveadm backup to new cluster running dovecot 2.2.36 and replicator

(mdbox). The new cluster has two backend mail servers which replicate through doveadm replicator. To move the data initially we use doveadm backup (imapc). arb Our migration command  doveadm -o mail_fsync=never backup -R -u $user imapc: To test the replication of new and purge of old mails

doveadm backup only working once?

All, For the past 2 weeks I have been trying to get dovecot mail backup working between 2 debian 10 machines. Both machines are running the same OS (Debian 10) and configuration wise they are similar (except of course ip addresses, hostnames etc). My "main" machine is called "server" and

migration with doveadm backup to new cluster running dovecot 2.2.36 and replicator

Hello everyone, we are working on migrating from dovecot 2.0.9 (maildir) to 2.2.36 (mdbox). The new cluster has two backend mail servers which replicate through doveadm replicator. To move the data initially we use doveadm backup (imapc). Our migration command doveadm -o mail_fsync=never

RE: doveadm backup -f -n inbox doing writes?

Hmmm, but I have made a few files with accounts to sync, if I use the list with the oldest least changing mailaccounts I get this spike during the doveadm backup. And if I issue the same command 30s later, the spike is back for the duration of the check. And since it was finished quite

Re: doveadm backup -f -n inbox doing writes?

> On 22/12/2020 00:12 Marc Roos wrote: > > > If I start a 'doveadm backup -f -n inbox' on the source server, why do > also disk writes increase on the source server (indexes mostly?) Probably because your indexes are not up to date? Aki

doveadm backup -f -n inbox doing writes?

If I start a 'doveadm backup -f -n inbox' on the source server, why do also disk writes increase on the source server (indexes mostly?)

Re: Doveadm Backup (other) issues

n server. For that purpose, I defined the following parameters : imapc_host = imapc_user = imapc_password = imapc_features = rfc822.size ( has format: n...@example.com <mailto:n...@example.com>, and  is the name of the imap remote server that I use for getting mails) … and then  I iss

Re: Doveadm Backup (other) issues

is the name of the imap remote server that I use for getting mails) … and then I issued the following command: doveadm backup -R -u <mailto:n...@example.com>> imapc: ... but doing this, I get the following answer: dsync(): Info: imapc(:143): Connected to IP address>:143 (loca

Re: Doveadm Backup (other) issues

> On 8. Jun 2020, at 17.39, John Stoffel wrote: > >> "Sami" == Sami Ketola > > writes: > >>> On 7. Jun 2020, at 18.20, John Stoffel wrote: >>> "Gingko" == Gingko writes: >>> > Gingko> I also have issues using Dovecot Backup. >>> >

Re: Doveadm Backup (other) issues

> "Sami" == Sami Ketola writes: >> On 7. Jun 2020, at 18.20, John Stoffel wrote: >> >>> "Gingko" == Gingko writes: >> Gingko> I also have issues using Dovecot Backup. >> Gingko> I am trying to Backup (or possibly Sync - one way) a single Gingko> user IMAP account from a remote

Re: Doveadm Backup (other) issues

> On 7. Jun 2020, at 18.20, John Stoffel wrote: > >> "Gingko" == Gingko writes: > > Gingko> I also have issues using Dovecot Backup. > > Gingko> I am trying to Backup (or possibly Sync - one way) a single > Gingko> user IMAP account from a remote server, unknown type, to my > Gingko>

Re: Doveadm Backup (other) issues

rpose, I defined the following parameters : > > imapc_host = > imapc_user = > imapc_password = > imapc_features = rfc822.size > > ( has format: n...@example.com <mailto:n...@example.com>, and > is the name of the imap remote server that I use for getting > mails

Re: Doveadm Backup (other) issues

> "Gingko" == Gingko writes: Gingko> I also have issues using Dovecot Backup. Gingko> I am trying to Backup (or possibly Sync - one way) a single Gingko> user IMAP account from a remote server, unknown type, to my Gingko> own server. I think this is the key problem here, doveadm only

Doveadm Backup (other) issues

= imapc_features = rfc822.size ( has format: n...@example.com, and is the name of the imap remote server that I use for getting mails) … and then  I issued the following command: doveadm backup -R -u imapc: ... but doing this, I get the following answer: dsync(): Info: imapc(:143): Connected to address

Re: Doveadm Backup issues

On Sat, 6 Jun 2020, @lbutlr wrote: On 05 Jun 2020, at 17:09, Bernardo Reino wrote: USERS=$(cat /etc/dovecot/virtual_passwd | cut -d: -f1) Is that a standard file? It's not one I have. No, of course not! :) That's just my userdb/passdb (passwd-file). I would use (not that I have, but it

Re: Doveadm Backup issues

On 05 Jun 2020, at 17:09, Bernardo Reino wrote: > USERS=$(cat /etc/dovecot/virtual_passwd | cut -d: -f1) Is that a standard file? It's not one I have. I would use (not that I have, but it seem like the way to get a list of users) USERS=$( doveadm user '*' ) -- You start a conversation you

Re: Doveadm Backup issues

On 6 Jun 2020, at 01:10, Bernardo Reino wrote: > > On Fri, 5 Jun 2020, Francis Augusto Medeiros-Logeay wrote: > >> Another related question: if backing up on another location on the same >> computer, using -A doesn't seem to recreate the structure of the original >> Maildir (for example,

Re: Doveadm Backup issues

On Fri, 5 Jun 2020, Francis Augusto Medeiros-Logeay wrote: Another related question: if backing up on another location on the same computer, using -A doesn't seem to recreate the structure of the original Maildir (for example, /var/mail/%d%n). Is there a way to do that? If I understand

Re: Doveadm Backup issues

Hi, As said below, I am trying to use doveadm backup. I made some progress, but I think I misunderstand some of the basic principles behind the command. My main issue is: when using the -A flag, is there a way to create the backup user on the remote server if it doesn't exist

Doveadm Backup issues

Hi, I'm trying to use doveadm backup but I'm having a few issues. When trying locally: `doveadm backup -D -A maildir:/usr/local/backup` It results that no mailbox is separated by user - all seems to sync on the same folder, messing up with the folder structure of the original maildir

Re: doveadm backup : Error: Failed to access mailbox

FYI, found the solution. It seems doveadm can't cope with brackets in mailbox names. I moved the user's mails into non-braketed, deleted the bracketed and doveadm backup worked fine after that. ‐‐‐ Original Message ‐‐‐ On Sunday, 24 May 2020 14:32, Laura Smith wrote: > Hi

doveadm backup : Error: Failed to access mailbox

Hi All, So close and yet so far.  ;-( Have been migrating users from an old Dovecot server to a new one. All of the users have doveadm backup'd perfectly, except for one ! What does the below mean ? $ sudo doveadm -v -o imapc_user=j...@example.org.tld -o imapc_password=secretSquirrel -o

doveadm backup, question

Hello everyone. I am an inexperienced user of dovecot and I faced probably a simple problem, but I still do not understand how to solve it. The issue is related to using doveadm backup - I want to backup mailboxes; make this copy on the same machine (hereinafter, files with backup copies

Issue with doveadm backup

Greetings, Lately I've been seeing this error pop up when running a nightly cron to a backup share with doveadm: Error: stat(/vmail/domain.tld/user/.dovecot-box-sync.lock/tmp) failed: Not a directory: 1 Time(s) This is the command: doveadm backup -u u...@domain.tld maildir:backupshare

Re: [EXT] doveadm backup from gmail with imapc

On Fri, 2020-04-10 at 15:13 +0300, Sami Ketola wrote: > > > > > On 10 Apr 2020, at 14.07, Ben Mulvihill > > wrote: > > > > > last answer from gmail: > > > > > 1586513176.126970 1944 OK Success > > last commands send by dovecot: > > > > > 1586513175.951965 1944 UID FETCH > >

Re: [EXT] doveadm backup from gmail with imapc

> On 11 Apr 2020, at 15.20, Ben Mulvihill wrote: > > I tried setting imapc_cmd_timeout = 10s and that was enough to take the > download process past the ID stage and on to downloading messages. > doveadm still failed the same ASSERT and core dumps, just not so soon. > In four attempts I

Re: [EXT] doveadm backup from gmail with imapc

> On 10 Apr 2020, at 14.07, Ben Mulvihill wrote: > > last answer from gmail: > 1586513176.126970 1944 OK Success last commands send by dovecot: > 1586513175.951965 1944 UID FETCH > 99624,99627,99628,99629,99631,99632,99633,99634,99635,99636,99637,99639 >

Re: doveadm backup from gmail with imapc

On Thu, 2020-04-09 at 13:48 +0300, Sami Ketola wrote: > > > > > On 31 Mar 2020, at 23.18, Ben Mulvihill > > wrote: > > > > Hello again, > > > > I am still stuck I'm afraid. > > > > I now have doveadm backup working perfect

Re: doveadm backup from gmail with imapc

On Thu, 9 Apr 2020, Plutocrat wrote: I could never figure out how to get the dovecot indexes correct, so that when the client connected to the new server via POP, it didn't re-download all the messages. IMAP was OK though. It's been a while since I migrated from the qpopper, but I believe

Re: doveadm backup from gmail with imapc

> On 31 Mar 2020, at 23.18, Ben Mulvihill wrote: > > Hello again, > > I am still stuck I'm afraid. > > I now have doveadm backup working perfectly from > a small gmail mailbox (a few hundred messages), but > when I try the same configuration (apart from username

Re: doveadm backup from gmail with imapc

> On 9 Apr 2020, at 4.45, Plutocrat wrote: > > On 08/04/2020 19.14, Ben Mulvihill wrote: >> Thanks for the suggestion. I think my next step will be to investigate >> imapsync, or maybe isync, which also looks promising. > > I've recently migrated a server with imapsync with 150Gb of email

Re: doveadm backup from gmail with imapc

On 08/04/2020 19.14, Ben Mulvihill wrote: > Thanks for the suggestion. I think my next step will be to investigate > imapsync, or maybe isync, which also looks promising. I've recently migrated a server with imapsync with 150Gb of email and 200+ accounts. I found the trick with this was the run

Re: doveadm backup into IMAP folder

...@domain.new/fromold. i can follow that While I succeeded using doveadm backup / dsync to successfully replicate the old mailbox to the new one, I am unable to store all imported mail under a specific folder. So, I have some questions: this have not being dokumented good for me to understand and i have

doveadm backup into IMAP folder

using doveadm backup / dsync to successfully replicate the old mailbox to the new one, I am unable to store all imported mail under a specific folder. So, I have some questions: - can the above be done? - if yes, can you confirm that email outside the specific destination folder

  1   2   3   >