dovecot - Apr 2006 - hard link between courierimapuiddb and dovecot-uidlist?

Hi, guys.

I'm attempting to transition between Courier IMAP and Dovecot. I may not
be able to transition all the courierimapuiddb files instantly or even
transition all my servers at the same time. Ideally, it wouldn't matter.
Users can login and get to a Courier IMAP machine or a Dovecot machine
and read their email (all mounted via NFS).

My question is: is there any reason I can't just do a hard link between
courierimapuiddb and dovecot-uidlist? That way, I can transition users
over to Dovecot at my leisure. And, if I need to, I can move back to
Courier. The hard link is essentially free and lets me make sure these
files stay synced.

Thanks
Jeff

On Sun, 2006-04-16 at 20:06 -0400, Jeff Tucker wrote:
> Hi, guys.
> 
> I'm attempting to transition between Courier IMAP and Dovecot. I may
not
> be able to transition all the courierimapuiddb files instantly or even
> transition all my servers at the same time. Ideally, it wouldn't
matter.
> Users can login and get to a Courier IMAP machine or a Dovecot machine
> and read their email (all mounted via NFS).
> 
> My question is: is there any reason I can't just do a hard link between
> courierimapuiddb and dovecot-uidlist? That way, I can transition users
> over to Dovecot at my leisure. And, if I need to, I can move back to
> Courier. The hard link is essentially free and lets me make sure these
> files stay synced.
They don't stay synced, because the first time a new mail arrives in the
maildir the uidlist file gets rename()d over and the other uidlist file
doesn't get updated. Both Courier and Dovecot does this.

Also I'm not sure if Courier can properly read Dovecot-generated uidlist
file because I also write the filename's ":2,flags" part in there.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL:
<http://dovecot.org/pipermail/dovecot/attachments/20060421/b0e36a4d/attachment.bin>