Timo Sirainen writes:
> On Sat, 2011-01-29 at 12:04 -0600, Rob Browning wrote:
>> OK, so it sounds like if we wanted to be completely safe, we probably
>> need to know that we're in a dovecot Maildir, and then we need to know
>> where to create the appropriate dovecot-
Timo Sirainen writes:
> On 29.1.2011, at 19.05, Rob Browning wrote:
>> I saw that, but I wasn't sure if the fact that a message might "receive
>> a new UID" could be a problem.
>
> It's a theoretical problem mostly, especially in your case. It's
&
gs. Would locking
dovecot-uidlist.lock be sufficient, perhaps via liblockfile?
Also, is there some reliable way to detect a dovecot Maildir? For
example, are any of the dovecot-* files guaranteed to exist all the
time?
Thanks
--
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2002-11-03
