similar to: Maildir synchronization

Hi, I'm wondering: Is it a problem to move and delete files inside a dovecot-managed maildir? For example: I have a folder ~/.maildir/.Sub1.Start/cur and a folder ~/.maildir/.Sub1.Start.old/cur and like to regularly move old mails from the first to the second one. Can you create a cron job saying something like: find ~/.maildir/.Sub1.Start/cur -mtime +5 -exec mv {}

I'm using Dovecot (+postfix) to host some personal imap accounts on a private server (Maildir format). I've got one account that receives mostly automated mails, and I want to be able to purge messages beyond a given date (say 30 days). I know that since maildir uses flat files, I can literally just delete messages doing something similar to the following with bash: for i in $(find

Hi, We are repeatedly getting these below warnings for some of our users, al though we have no complaints from them yet, ?we need to know why these warning occurs. So it would be help full if some one explain these warning msg in detail. ----------------------------------------------------------------------------------------------------------------------------------------------------- Aug? 2

Hi, everyone! This is a follow-up to "Looks like a bug to me: Dovecot ignores Maildir/new timestamp" from Fredrik Roubert on 01.12.2015: https://www.dovecot.org/list/dovecot/2015-December/102585.html I've run into the same problem as Fredrik: When manipulating my Maildir locally with mutt, deleting a message from new/ doesn't cause a full update of the index. Therefore, IMAP

Dovecoters, is it safe to manipulate files in Maildir/xxx directly or will Dovecot become unstable if I don't make these changes by talking to Dovecot and having it make the changes? (I'm running 2.1.7 under Wheezy, IMAP only) My specific application: I am running spamassassin and would like users to be able to submit spam (and ham) directly by moving it into special folders. A cron

Hi! I want to automatically delete old messages from one user's Maildir, and I was thinking on running something like this: find /home/user/Maildir/cur/ /home/user/Maildir/new/ -daystart -mtime +15 -delete but I'm not sure if by deleting messages "manually" I will break the dovecot.index* files. What do you think? Thanks! Ildefonso.

Hello- I have set up Dovecot before and feel fairly comfortable with it but am having some issues with a new setup and have not been able to find a solution via Google or the list archives. I use offlineiimap to sync an IMAP account with an email provider. After the sync is complete, my ~/Maildir is set up with a folder called INBOX (with cur,new,tmp inside) and all my other folders set up at

Hi. It seems that dovecot is using the current time, not a maildir file's mtime for INTERNALDATE when a message is re-indexed: $ cd Index $ rm -rf .INBOX $ cd ../Maildir/cur $ stat * File: `1392914632.P54451Q0M08633.smtpin01,S=2215,W=2249:2,' Size: 960 Blocks: 8 IO Block: 1048576 regular file Device: 36h/54d Inode: 11132959 Links: 1 Access: (0600/-rw-------)

While running dovecot on debian etch using version 1.0.rc15-2etch3, i wonder the following: If i read the config files correctly, dovecot seems to have no equivalent of courier's IMAP_EMPTYTRASH=Trash:7 setting. Therefore, i wrote a script that dives into the user's directories and their maildirs. It looks like this: ============================================= #!/bin/bash for pad1

On 12 Feb 2019, at 03:45, Ralf Hildebrandt via dovecot <dovecot at dovecot.org> wrote: > 201629 of 301900 (66.7%) files are modified (mtime) more than 5 days ago, although I just purged everything older than 4 days? I had problems with this a few years ago, and resorted to simply using find to remove the files from the file system /usr/bin/find /usr/local/virtual/*/.Junk*/{cur,new}

Hi ALL... I want to know if the files in /Maildir/cur & /Maildir/.Sent are modified by dovecot. I have a script which calculates the age of the mail files. I think that if they are continuously modified by dovecot I won't be able to calculate the age of the files. Can Anyone plz advise on this.... Thanks CoolAtt

On the wiki: http://wiki.dovecot.org/Plugins/Zlib I think there should be a step 5.0. along the lines of "get and remember the original message file's mtime" And a step 5.4 like "Using the touch command or some other method, set the now compressed message's mtime back to the mtime of the original message file." To preserve the message's internal time in case

I haven't been able to find what is responsible for altering the time on APPENDed mail, but was able to come up with a temporary workaround ... simply calling utime() later on in the process resolves it. Below is my patch. Steve --- dovecot-1.0.beta7-orig/src/lib-storage/index/maildir/maildir-save.c 2006-03-25 05:53:43.000000000 -0500 +++

Hi, I just want some clarification on how Dovecot's IMAP assigns UIDs when it picks files from the "new" directory of a Maildir. What I am observing is that only ctime has a role to play in it. For example if there are two files in "new", a.msg & z.msg. Even when a.msg has lower mtime than z.msg and "a" comes before "z" alphabetically, dovecot

https://bugzilla.samba.org/show_bug.cgi?id=13735 --- Comment #3 from Sébastien Béhuret <sbehuret at gmail.com> --- Thank you for suggesting the patches repo. An improved checksum/maybe-checksum algorithm would be great but there appears to be a lot of work to achieve this. Checksums are very handy for special cases (e.g. to detect and fix data corruption) but are still relatively slow and

If Maildir storage is used, the mtime of a given Maildir file is set to the message's INTERNALDATE. Now, when a client APPENDs a message to an IMAP mailbox, the client may optionally specify the INTERNALDATE: | If a date-time is specified, the internal date SHOULD be set in the | resulting message; otherwise, the internal date of the resulting | message is set to the current date and time by

https://bugzilla.samba.org/show_bug.cgi?id=13735 Bug ID: 13735 Summary: Synchronize files when the sending side has newer change times while modification times and sizes are identical on both sides Product: rsync Version: 3.1.3 Hardware: All OS: All Status: NEW

Hello, I would like to know what is the proper way to restore a Maildir : Assuming someone has got a foobar/[cur|new|tmp] maildir, loses for some reason its content and that some new mail (seen and/or unseen) comes into that mailbox inbetween (that is before the restore procedure takes place, thus creating the need to merge restored messages and new ones). I'd like to check the following (I

Bump. Any advice would be most appreciated. Thanks. From: Terence Lau Sent: Wednesday, 24 January 2018 9:59 AM To: 'dovecot at dovecot.org' <dovecot at dovecot.org> Subject: Out of memory on lmtp vsz_limit Hi, We've been getting these types or errors for quite a while now ... Fatal: master: service(lmtp): child 63477 returned error 83 (Out of memory (service lmtp {

Hello Adam, and the dovecot list Just a question, I hate to pollute the thread, so feel free to push these questions into a new thread if deemed necessary. So as you can guess I'm a bit of a newb here, so rather obvious questions are about to arrive.... As you are using GIT for your archive (which is a cool idea by the way) I'm sure you are well aware that not all files types play nicely