If it's less than 64 bits number and Dovecot is compiled as 64bit
binary, I guess it should work. Otherwise it gets more or less random:
http://hg.dovecot.org/dovecot-2.2/file/17aac21b303d/src/lib-storage/index/maildir/maildir-filename.c#l117
That explains it. Thanks.
> On 17 Oct 2015, at 11:44, Akash wrote:
>
>> Dovecot doesn't look at the new files' mtimes or ctimes, because that
>> would require stat()ing the file, which slows it down. So it's using
>> the timestamp in the Maildir filename itself.
>
> Thanks Timo for the clarification. Whats Dovecot's str
Dovecot doesn't look at the new files' mtimes or ctimes, because that
would require stat()ing the file, which slows it down. So it's using
the timestamp in the Maildir filename itself.
Thanks Timo for the clarification. Whats Dovecot's strategy when the
file-name does not contain a time-stamp a
On 17 Oct 2015, at 10:24, Akash wrote:
>
> 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
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.
