similar to: dovecot vs. mutt: no full index sync on Maildir new/ mtime change

Hello! I run Debian jessie and have an issue with the interaction between Dovecot (2.2.13), Mutt (1.5.23) and the Android Gmail (5.8.105868218) IMAP client, when using Maildir: I use Dovecot LMTP for local delivery into Maildir and access these files both through Dovecot IMAP from the Android Gmail IMAP client and also directly through the filesystem by running Mutt locally on the mail server.

We have been running Dovecot 2.2.10 with a pair of CentOS 7 boxes with replications for the past year. We have been quite happy with the performance and reliability. Recently we received a report from an Android IMAP user that emails that he deleted without reading would often reappear in his INBOX. At first I thought it might be some quirky incompatibility with his email client, but I

On Fri 04 Mar 2016 at 08:37 -0600, Ron Cleven wrote: > Recently we received a report from an Android IMAP user that emails that > he deleted without reading would often reappear in his INBOX. I have encountered this problem too. Did you ever solve it? Cheers // Fredrik Roubert -- Forsterstrasse 64 | +41 78 8170377 CH-8044 Z?rich | https://roubert.name/fredrik/

The dovecot version (2.2.10) we were running had a timing window problem in the context of replication (we use maildir on CentOS 7). After doing elaborate tests to isolate the problem, we wound up upgrading to 2.2.23. That fixed it, and that version has been very reliable. >> Recently we received a report from an Android IMAP user that emails that >> he deleted without reading

Version 2.1.10 For some reason Mutt doesn't list any info about IMAP folders and seems to ignore folder_format. My questions is does anyone have any workarounds for this?

Hi *, can crypted logical volumes be used as vbds for Xen? by Töns -- There is no safe distance. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Hi, I''m writing my requirements in rspec, however, I can not figure out a way to execute all specs according to alphabetical order, not by last modified time. According to the documentation, it seems like the default is by alphabetical order, I just can not get that to work. In the unit tests with the rspec package, seems like only mtime was tested. Can anyone tell me how to run specs

Hi, I''m writing my requirements in rspec, however, I can not figure out a way to execute all specs according to alphabetical order, not by last modified time. According to the documentation, it seems like the default is by alphabetical order, I just can not get that to work. In the unit tests with the rspec package, seems like only mtime was tested. Can anyone tell me how to run specs

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?

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'm trying to write a script that runs rsync to pull files and then detect which ones of them have changed. The problem is when I run rsync without the -t flag the mtime gets updated every run, not only when the file changes. It this a bug, by design, or un-avoidable? My plan was to use the -N bash file test operator to check to see if the file had been accessed since it have been

Hello, I just observed something strange: rsync -av --exclude /USER/NoBackup --exclude '*.NTX' --compare-dest=/backup/novell/vollbackup /mnt/novellserver/SYS/ /backup/novell/ziel rsync -av --exclude /USER/NoBackup --exclude '*.NTX' --compare-dest=/backup/novell/vollbackup/PUBLIC /mnt/novellserver/SYS/PUBLIC/ /backup/novell/ziel For debugging purposes (saving time) I used

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

I'm really excited about the recent work on extended attributes. I've compiled 2.6.9 with xattr support, and run a few tests. It seems that if I have a file with an extended attribute ( a resource fork in this case), and I run rsync -aX , the mtime is not preserved. Example: stat xattrsrc/a 234881026 2894399 -rw------- 1 admin staff 0 1048576 "Nov 10 10:03:01 2006" "Nov

Hi, I try to rsync files only X days old. This is my setup. The backup server needs to store all servers' backup and only has space for 7 days backup. But each individual server has backup for 21 days. On the backup server, i remove files older than 7 days. When backup server pulls files, I want rsync only pull files with mtime last 7 days. Searching through the archive, someone suggested

Hello I am making backup of a Plesk Debian server to /backup using Rsync. My questioin is how can I preserve the ctime, mtime, and atime of original files? Thanks

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"

-----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 set a specific mtime (--times) but setting a specific ctime is impossible as it would violate the basic *nix security model.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I would need to see both your existing rsync command line and the output of --itemize-changes when such an occurrence happens before I can really understand what is happening. In the end, if you have any output at all the bare minimum should be - --itemize-changes. --verbose is utterly useless without it. On 09/07/2015 11:10 PM, Andrej wrote: >

samba on Raspberry pi 4b - Linux 6.1.41-v8+ aarch64 GNU/Linux if I do a mtime on the file that gets shared I see this Modify: 2020-10-22 09:02:16.991364753 -0400 when I do a mtime on the same file on the client (Linux) I see this Modify: 2020-10-22 09:02:16.991364700 -0400 Is not a big deal it just caused some rsync confusion that was addressed by using --modify-window=1 Is this by design