similar to: "doveadm altmove -r" not working ?

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

> 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

Accessing or listing "mdbox_deleted" contents seems to destroy MDBOX indexes. Examples of commands which triggers this problem ($home being the home directory of $user, and mail_location being mdbox:~/mdbox): doveadm -o mail="mdbox_deleted:$home/mdbox" -f table mailbox status -u "$user" 'messages vsize' INBOX doveadm -v import -s -u "$user"

It appears that doveadm output format changes every now and then, without particular notice. For example, the following command: doveadm -f pager mailbox status 'messages recent' '*' did output something like this until v2.2.24 : mailbox: Mailbox1 messages: 58 recent: 12 ^L mailbox: Mailbox2 messages: 128 recent: 0 but switched to that in v2.2.26 : Mailbox1 messages: 58

in Dovecot 2.0, is it possible to have kind of "cumulative" multiple userdb ? that is, for all users: - extract some attributes (let's say: uid, gid, home) from a first userdb (Passwd for example), - an extract some other attributes (mail for example, but overwriting those from the first userdb in case of redundancy) from a second userdb (LDAP for example) ? This is *different*

Hi there, there is the ubuntu version 2.0.13 ov dovecot installed on our server. But in contrast to http://wiki2.dovecot.org/Tools/Doveadm/Altmove the option -r isn't supported in this version. altmove: invalid option -- 'r' doveadm altmove [-u <user>|-A] [-S <socket_path>] <search query> In which version of dovecot is this option supported? Thanks Lars

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

Hi, we just upgraded our mailserver from Dovecot 1.0.15 to Dovecot 2.1.7. We use MBOX format (due to legacy compatibility), system users, PAM+GSSAPI auth, filesystem quotas, and indexes located on a separate filesystem: mail_location = mbox:~/mail:INBOX=~/mail/INBOX:INDEX=/var/cache/dovecot/indexes/%16Hu/%u The 2.1.7 configuration files have been rewritten based on default templates

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

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

I was thinking about documentation for alternate storage. We have a few mentions at: http://wiki2.dovecot.org/MailboxFormat/dbox http://wiki2.dovecot.org/Tools/Doveadm http://wiki2.dovecot.org/Tools/Doveadm/Altmove But I was thinking it would be helpful if there could be a page about alternate storage. I could write the page, but I currently have so many unknowns that I think it would be

Hi list, I've just set up a 2.1.7 server, and have migrated a couple of accounts across from a 2.0.15 server, keeping the old configs. I have a strange problem on the new box in that altmove just doesn't work. I have my main storage under /home/email, indexes under /home/indexes and ALT under /home/email_archive. When I run the altmove command, the following broken symlink is created

Il 2020-11-01 13:23 John Stoffel ha scritto: > How is your "mail_location" defined in your configuration? And what > is your search term? > > John Hi, I just discovered having such strange .temp files on an old server of mine. In some folders I have hundred of such files, but they really are hardlinks to the same .temp file (for each folder), so they do not consume

On 15 May 2015, at 02:50, Daniel van Ham Colchete <daniel.colchete at gmail.com> wrote: > > 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

>>>>> "Maciek" == Maciek Jackowski <niksfirefly at gmail.com> writes: Maciek> dovecot 2.2.33.2 Ubuntu 18.04 Maciek> I got strange file Maciek> .temp.1592374672.P11164Q21M692534.hostname Maciek> after doveadm altmove command Maciek> in INBOX on alternate storage server Maciek> What can I do with this file? Remove? Maciek> I am using dbox You

Hi, Here is the problem that occured: #sudo doveadm -D altmove -u vv at vito.pp.ua all works properly and moves all storage to alt dir. However, to move it back to default storage I add '-r' by manual: #sudo doveadm -D altmove -u vv at vito.pp.ua -r all That seems behave like the original command ignoring '-r'. my dovecot conf: # 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf

dovecot 2.2.33.2 on Ubuntu 18.04 I am using dbox with altmove to save storage space on mail server I got strange behaviour with one email box where folder content Archives/2018 is not moving but other folders Archives/2017 and Archives/2019 are moved to the alternate storage server Well I dont know howto start to resolve this regards

Hello, i tried to move mails to an alt storage with the following command: doveadm altmove -u user at domain.de mailbox Inbox After that, the imap process produces a core dump (files has not been moved): Maillog: dovecot: imap-login: Login: user=<user at domain.de>, method=PLAIN, rip=X.X.X.X, lip=X.X.X.X, mpid=5393, TLS, session=<83JiHqNdTwCsEAIf> dovecot: imap(user at