similar to: strange file .temp.1592374672.P11164Q21M692534.hostname - doveadm altmove

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

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

>>>>> "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, 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

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 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

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

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

> 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 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

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 =

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

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, 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

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

I was optimizing a 650MB using ferret (0.11.3) and I received the following error. I''ve seen some people have similar issues but I haven''t seen any resolutions. The contents of the index directory follow the error. Has anyone seen anything like this and found a resolution? Many thanks. /mnt/apps/search/releases/20070622175637/script/../config/../vendor/

After fresh installation of CentOS 6.2 on my server, I get following errors in my dmesg output: ------- MTRR default type: uncachable MTRR fixed ranges enabled: 00000-9FFFF write-back A0000-BFFFF uncachable C0000-D7FFF write-protect D8000-E7FFF uncachable E8000-FFFFF write-protect MTRR variable ranges enabled: 0 base 000000000 mask C00000000 write-back 1 base 400000000 mask

Dear all, I would appreciate please a piece of help regarding the use of acast/dcast functions in reshape2 package. Specifically, I'm working with a data frame, that has information about SAMPLE, GENE, and TYPE of MUTATION (as shown below): Sample Gene Type 22M AEBP1 SNV 17M AEBP1 SNV 22M ATR INDEL 22M ATR SNV 11M BTK SNV 11M BTK

Hi Do you want something like dcast(test, Sample~Gene, fun=function(x) paste(x, collapse=",")) or dcast(test, Sample~Gene, fun=function(x) sum(as.numeric(x))) 1 means INDEL, 2 means SNV and three means both Cheers Petr > -----Original Message----- > From: R-help [mailto:r-help-bounces at r-project.org] On Behalf Of Bogdan > Tanasa > Sent: Monday, July 3, 2017 9:22 AM