similar to: maildir, zlib and mtime/internal date

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

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

I posted to the list about this a while ago but never got a response, I have a bit more information now. Dovecot 2.2.12 and other 2.2 versions are broken when using zlib and maildir. If messages are re-indexed, the INTERNALDATE of all messages is set to the time the re-index is done. The problem seems to be in src/plugins/zlib/zlib-plugin.c in the function zlib_mail_cache_open. During a

Hello again, as stated earlier there is a problem with mtime setting on directories during healing in replication setup. Today I tested 2.0.5 and found out that the handling is more or less generally buggy for directory mtimes. Simply try this: untar some kernel archive on your local disk and look at the mtime of the created top directory. now untar the same archive on an exported gluster fs and

When using the zlib plugin with maildir and copying with hardlinks, if a compressed message is copied, the 'Z' suffix on the file isn't copied, so the new message isn't uncompressed when it's fetched. I wasn't smart enough to figure out a clean way to carry a file suffix through a copy, so I changed how the zlib-plugin detects if a message is compressed. This

It'd be useful for us if the IMAP passdb could be used as a prefetch userdb. The remote IMAP server could respond with something like * OK key=value * OK key=value SEQ OK [CAPABILITY ...] Logged in. Or * OK <some JSON key value pairs> SEQ OK [CAPABILITY ...] Logged in. Would anyone else find this useful?

Hi all. I prepared a mirror (that is intended to be updated by rsync) by doing the initial copy using cpio (for efficiency on 15 million files). Unfortunately, user, group, and mtime of some directories and files was copied incorrectly. Can I use rsync (GIT) to fix this? Greetings Sven -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type:

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

Hello List, How would i rsync all files which are older than X-Days? I am missing some kind of -mtime option. Since this is quite common for backups i am wondering how you are doing this kind of stuff. Thanks, Mario

Hello. As stated in my previous message, we have some old compressed maildir messages with incorrect sizes in the filename. These messages cause dovecot 2.x problems. I'm trying to write a script to crawl all our messages, check the actual message size and if necessary, fix the filename. However, when I do this, dovecot gives the message a new UID on next login. If I change the filename

When a compressed maildir message has a bad S= size in its filename it puts the user in an unrecoverable state, since maildir's do_fix_size function just does a stat() on the maildir file and saves the compressed size in the filename. This (quick, rough, barely tested) patch addresses this issue, it's inefficient, but we're already in a hopefully rare emergency situation. ---

I noticed that rsync is happy to hard-link a device node from a --link-dest dir even if its mtime differs from that of the source device node and --times is given. Is this behavior expected? It seems to break the rule that a difference in preserved attributes disqualifies a hard link. To see the behavior, run the following as root: mkdir src dest basis mknod src/null c 1 3 sleep 1 mknod

https://bugzilla.samba.org/show_bug.cgi?id=5867 Summary: rsync with ACLs resets mtime on targets Product: rsync Version: 3.0.4 Platform: x86 OS/Version: FreeBSD Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: samba@byshenk.net

On 8 September 2015 at 13:57, Kevin Korb <kmk at sanitarium.net> wrote: Hi Kevin. > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > The ctime will always be newer or the same as the mtime. This is > because changing the mtime also changes the ctime as does other things > like changing the permissions. > > Rsync only pays attention to the mtime because rsync can

Hello, I'm using rsync as part of a centralised config management for several servers. I'm trying to monitor the mtime of a particular directory and confirm that the remote copies are approximately as new as the the local master. However, mtime on that directory is not being synced. Here's my rsync command: cd $confdir && rsync -avpzR --checksum -I -e "ssh"

Hi An email with a mal-formed address in a header like: To:(receiver at domain.com (Starting with a comment, with no closing ')' ) causes dovecot 1.1.5 to panic and abort. This is similar to the problem fixed by: http://hg.dovecot.org/ dovecot-1.1/rev/04fdaa2f831e This patch seems to resolve the problem: --- dovecot-1.1.5/src/lib-mail/message-address.c.orig 2008-10-23

Hi Running dovecot 2.1.7 (from debian repo). We have some old compressed maildir messages with the wrong S= size in the filename (our fault). If I delete index files, log in to the mailbox and try to FETCH the bad message, dovecot complains about the incorrect message size, attempts to fix the filename and disconnects the client. However, it changes the filesize to the size of the message on

Hi With dovecot 2.2.5, and dovecot-antispam built from a recent HEAD pull, when copying multiple messages to or from a Spam folder, the plugin sends multiple copies of the first message to the backend. I've tried this with the pipe and spool2dir backends. For example with the spool2dir backend, via IMAP doing A COPY 1:3 Spam yields 3 copies of message id 1 in the dir: dev:imap-8.1 rplatel

If I run this: find /path/to/files/ -type f -mtime -2 -name *.xml.gz I get the expected results, files with modify time less than two days old. But, if I run it like this, with the print0 flag: find /path/to/files/ -print0 -type f -mtime -2 -name *.xml.gz I get older files included as well. Anyone know why?

Is there anyway I can get Dovecot to update mtime on dovecot.index everytime a user successfully checks there email? Or perhaps there is a better way to do what I want here. I am working on a script that I want to check when the last time a user checked there email account. If a user has not checked it in say 6 months I want to automatically suspend the account through the MTA. If they start