similar to: doveadm altmove -r

Hallo there. I'm new to this list and also to NUT. Our previous ups-system was APC based and apcupsd was serving the ordered shutdowns in our network. Our new ups is made by MGE and that's why we can't use apcupsd anymore. This led us into trouble. Our network system is quite complex and we need shutdown sequence levels. The servers depend on each other because of NFS and SQL

Well that option set still doesn?t look correct? Here is the doveadm option set from my 2.2.2 server which is several weeks\months before 2.2.36? [Jul-27 @ 15:25:09 ] > dovecot --version 2.2.2 [Jul-27 @ 15:26:53 ] > ls -l /usr/local/bin/doveadm -rwxr-xr-x 1 root root 1379203 May 22 2013 /usr/local/bin/doveadm [Jul-27 @ 15:25:12 ] > doveadm usage: doveadm [-Dv] [-f

I seem to recall a post a while back where, due to the age of the remote end, the remote side command had to be entered in the command executed on the local side. Do you have dsync on the 2.0.9 machine? > On Jul 27, 2020, at 4:16 PM, Kishore Potnuru <kishore.reachme at gmail.com> wrote: > > This is what my understanding. May be I am also wrong here. > > Backup option

Hi, But there is no "doveadm backup" option in dovecot 2.0.9 version. [root at production ~]# doveadm -backup doveadm: invalid option -- 'b' [root at production ~]# dovecot --version 2.0.9 Copy the contents by using "scp", will that work? Thanks, Kishore Potnuru On Mon, Jul 27, 2020 at 10:00 AM Aki Tuomi <aki.tuomi at open-xchange.com> wrote: > > >

Hi! Kishore, you got the command wrong.. `doveadm backup -R -u username-goes-here imapc:` for this to work, you need to configure following things: imapc_host = old-host-name imapc_password = master-password imapc_master_user = master-user-name and on the old host you need passdb { args = /etc/dovecot/passwd.masterusers driver = passwd-file master = yes pass = yes } This should

Hi I am in the process/planning of moving from my existing dovecot imap/pop3 server to 2 new servers (for HA/Resilience). I will be implementing dovecot replication on new servers. Please find my current and new servers versions. My Current Production Server details: ======================== Linux OS - Red Hat Enterprise Linux Server release 6.5 (Santiago) Dovecot version - 2.0.9

Fair enough but the command snippet I posted was taken directly from your earlier post dated Mon Jul 27 23:11:06 EEST 2020 and it does say ?production1??I just double-checked as well... FWIW?the server order in the command you just pasted is the exact reverse from the Jul 27th post I mentioned above? Here you appear to be exec?ing the command on prod2 and trying to pull from the remote of prod

I tried this command also. It didn't work. It shows syntax again. Please see the supported commands in dovecot 2.0.9 version. This doesn't support replication also as per syntax, if i am not wrong. Please suggest me. [root at production ~]# doveadm backup -u kishore at test.org.com remote:vmail at production2.test.org.com usage: doveadm [-Dv] [-f <formatter>] <command>

Hi there! It seems that # doveadm backup -v backup -fu $MUSER mdbox:"$BKPDIR/$MUSER/mdbox" doesn't backup all messages stored in alternate storage. mail_location = mdbox:~/mdbox:ALT=/srv/mail/slow/vmail/%n/mdbox I don't know how to debug this. The sizes of the mailboxes in the filesystems of user C are strange: ~/mdbox: # du -sm 2169 ALT: # du -sm 25252 backup: # du -sm

> On 21/03/2023 00:26 EET Benoit Branciard <benoit.branciard at univ-paris1.fr> wrote: > > > Hello, > > I have some trouble using "doveadm altmove -r". > > Regular "doveadm altmove" is OK, selected mails were moved to alternate > storage as expected. But I can't manage to get them back to original > location, "doveadm altmove

Hello, I have some trouble using "doveadm altmove -r". Regular "doveadm altmove" is OK, selected mails were moved to alternate storage as expected. But I can't manage to get them back to original location, "doveadm altmove -r" has no effect. We are using Dovecot 2.3.4 (Debian Buster package). mail_location =

Hi, Your problem might be similar to mine a long time ago. IMO behavior of "doveadm altmove -r" command with mdbox format is different to sdbox format: - With sdbox format, when you move back a message to primary storage (aka default storage), only the message and the file containing it are affected. There is nothing impacted. - With mdbox format, a file in storage contains

Hello everyone! I would like to report a bug here. We are using dovecot's sdbox with alternate storage here. From time to time my SSD partition gets full and I always find users with lots of e-mails stuck there, and altmove just won't move them. It moves most of the e-mails correctly, but a few was getting stuck everyday. So, I think I have found the problem! When a user moves the

Not sure if this matters but the prompt when attempting the ?doveadm backup? command shows it to be a ?production" server? [root at production1 <https://dovecot.org/mailman/listinfo/dovecot> test.org.com]# doveadm backup -R -u kishore at test.org.com <https://dovecot.org/mailman/listinfo/dovecot> remote:vmail at production2.baplc.com

Hello again. When I use doveadm altmove, I notice that it may result in some very small storage files in either the primary or the alternate storage location. I'm not quite sure, but it almost seems like every storage file that contains messages to be moved is simply split into two parts, even if a part might only contain a single message. This seems quite curious, since the idea of

Hello We are using Dovecot 2.0.17 with mdbox+zlib and we are evaluating alternative storage. These are the relevant settings mdbox_rotate_interval = 1d mdbox_rotate_size=60m [...] zlib_save_level = 9 # 1..9 zlib_save = gz # or bz2 [...] zlib plugin enabled in dovecot-lda These are my questions: 1? General mdbox question. We are happy usings zlib_save, but we would like to try bzip2

Hi, im wondering if it's possible to store old messages in a compressed mdbox on alternate storage. The main storage is uncompressed mdbox. I tried something like: doveadm -Dv -o "plugin/zlib_save=gz" altmove -u testuser sentbefore 8d Could someone tell me if it's possible and give me a hint how this can be done? I tried this with dovecot-2.2 Claus

This is what my understanding. May be I am also wrong here. Backup option is there in my new server, production2. When I use the command with -R option from new server, it is connecting to old server, Production1 and giving the output of the doveadm backup command in old server to get the data. If you see the command and error I posted, it shows the same. Sorry just incase if I am wrong.

dovecot 2.2.33.2 Ubuntu 18.04 I got strange file .temp.1592374672.P11164Q21M692534.hostname after doveadm altmove command in INBOX on alternate storage server What can I do with this file? Remove? I am using dbox regards

Hey Kishore? I believe this is the thread I mentioned earlier. It is quite long and spans a monthly barrier (Feb\Mar 2012) so if you use the ?Next\Previous message? links, you need to be sure to pick up the thread in each monthly archive. I have provided links to the first post of the thread in each archive here: https://dovecot.org/list/dovecot/2012-February/133718.html