1 Jul 2010 03:16
Re: Recomendations for a Migration of a Cyrus mailStore with 70K users.
Wesley Craig <wes <at> umich.edu>
2010-07-01 01:16:40 GMT
2010-07-01 01:16:40 GMT
On 30 Jun 2010, at 13:59, Nestor A Diaz wrote:
> another question : what about if a mail is comming from the lmtp
> socket
> to the refering mailbox and the mailbox is currently in the renaming
> process ?
From lmtpengine.c:
case IMAP_MAILBOX_MOVED:
prot_printf(pout, "451 4.2.1 Mailbox Moved\r\n");
break;
i.e., a temp fail error. It's retried.
> what about if the user have a shared folder and other users
> are accessing his mailbox with write privilegies ??
As a general statement, imapd is sensitive to the MOVING condition.
The specific circumstance would dictate precisely what would happen,
but there is no known case that would cause writes to be lost. The
user agent would either be informed or the server would retry on the
user agents's behalf.
It might look weird to the user agent, tho, and the user agent might
pass that weirdness along to the user.
:wes
----
Cyrus Home Page: http://cyrusimap.web.cmu.edu/
(Continue reading)
>
> Some basic questions:
>
> - Is Cyrus on amd64 able to read skiplist files created by Cyrus on
> i386? (If not, I'd probably have to use cvt_cyrusdb(8) to dump and
> restore the relevant files.)
Yes, it is. Heck, it managed to read (and upgrade in-place, I suppose)
skiplist files from Cyrus 2.1 just fine...
> - What about the cyrus.{cache,header,index,squat} files? Can I expect
> Cyrus on amd64 to be able to read them just fine? (This seems not to
> be that important since those files are easily recreated IIUC.)
Yes, if they're skiplist. I wouldn't trust that to work if it is berkeley
DB.
Be careful with the mailbox list, though. Better dump it to the portable
text file format, update any missing ACL rights, and restore it in the new
box.
RSS Feed