similar to: Excluding ALT maildir from showing in main INBOX

Hi all, I had implemented on one of my shares vfs full_audit module. It was working with Samba 3.0.x without any problems. After migration to Samba 3.4.3 this function doesn't work anymore - when it's enabled then share isn't accessible from users (it's visible but getting error when trying to connect to it). Audit and extd_audit vfs's are working fine, but they

I moved some mail into the alt storage: doveadm altmove -u johnd at example.com seen savedbefore 1w and now I want to move it back to the regular INBOX, but I can't see how I can do that with either 'altmove' or 'mailbox move'. thanks! micah -- -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type:

> 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

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

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 all please apologize that I repost this problem again. I tried to get some help several times on the list but did not find/get a solution. I am still struggling to setup different quotas for namespaces. In addition to the default "INBOX" namespace I have created a namespace called "MailArchive" which should have its own quota value of 5G per user. At first I

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

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

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

On 02 Nov 2016, at 22:02, Larry Rosenman <larryrtx at gmail.com> wrote: > > why wouldn't it be able to use the ~/MAILARCHIVE/ filesystem space? > > The other indexes etc seem to get built there. It's not about adding an index there, but about trying to open "MAILARCHIVE" itself as a folder. fts-lucene attempts to use an existing folder's indexes for

FWIW it DOES work on my default NAMESPACE, just not the #ARCHIVE/ NAMESPACE. On Wed, Nov 2, 2016 at 12:32 PM, Larry Rosenman <larryrtx at gmail.com> wrote: > It's ALWAYS failed on the other NAMESPACE. > > Some of the logging looks weird as well for the 2nd namespace: > > Nov 2 12:32:03 thebighonker dovecot: imap-login: Login: user=<mrm>, > method=PLAIN,

I'm getting this error message and I don't really understand what rsync is trying to tell me:- rsync: link_stat "/rdiffBackup/gradwell/Mail/." failed: No such file or directory (2) rsync error: some files could not be transferred (code 23) at main.c(977) [sender=2.6.9] Can anyone explain what it's saying please. /rdiffBackup/gradwell/Mail/ does exist and is

It looks like fts-lucene wants to write some information into INBOX's index files. But your archive namespace doesn't have a working INBOX. Maybe it would work if you create "#ARCHIVE/inbox"? > On 02 Nov 2016, at 20:13, Larry Rosenman <larryrtx at gmail.com> wrote: > > one other thing, fts_autoindex does NOT appear to be working on the > #ARCHIVE/ NAMESPACE.

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, all Based on my gcc plugin port to windows (see http://sourceforge.net/mailarchive/forum.php?thread_name=4E9E5897.8030001%40gmail.com&forum_name=mingw-users <http://sourceforge.net/mailarchive/forum.php?thread_name=4E9E5897.8030001%40gmail.com&forum_name=mingw-users> and

It's ALWAYS failed on the other NAMESPACE. Some of the logging looks weird as well for the 2nd namespace: Nov 2 12:32:03 thebighonker dovecot: imap-login: Login: user=<mrm>, method=PLAIN, rip=207.231.91.36, lip=192.147.25.65, mpid=76712, TLS, session=<HC+00VRAWczP51sk> Nov 2 12:32:03 thebighonker dovecot: imap(mrm): Debug: Loading modules from directory: /usr/local/lib/dovecot

thebighonker.lerctr.org /home/ler $ doveadm -D -v index \#ARCHIVE/2015/01/INBOX doveadm(ler): Debug: Loading modules from directory: /usr/local/lib/dovecot doveadm(ler): Debug: Module loaded: /usr/local/lib/dovecot/lib20_fts_plugin.so doveadm(ler): Debug: Module loaded: /usr/local/lib/dovecot/lib21_fts_lucene_plugin.so doveadm(ler): Debug: Module loaded: