Re: imapsync's --maxage flag

[John Fulton <fultonj@lafayette.edu>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Tom Golson wrote:
> 	This is pretty much the technique we used to migrate 66,000 accounts
> and about 5 TB of mail.  It seemed to work pretty well.  For the first
> iteration, we actually used only the --minage flag.  Then during
> subsequent iterations, until the final migration which was with --maxage
> only, we migrated sliding windows of mail using both the --minage and
> --maxage flags. ... I seem to recall our first synch took about a week or a
> week and a half, and our minage was 30.

Tom,

Was there any concern over missed operations on the old mail system?

If a message older than t days is modified in some way (moved, deleted,
etc) when imapsync is run with maxage less than t, then that operation
is not migrated. E.g. I delete a message from January after that portion
has been synced so post migration I have to delete it again.

I see this as a reasonable trade off so that the migration can happen in
a reasonable amount of time but I'm trying to work out how to plainly
explain this to users. You mentioned "sliding windows of mail" did this
involve a hiatus on email archiving or requesting that users do any
cleanup of old mail prior to a certain date to ensure that it's not
imapsync'd?

I was glad to see your reply. Thank you!

  John
- --
John Fulton, Linux Administrator, Lafayette College ITS
610-330-5650, Pardee Hall Room 11, Easton PA 18042-1775
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFI45/kNZmEpbCkXmERAmDlAKDCuI7g36Rw9zHcNb3n370mYdPdtgCgw37W
MNWVwHBY4aGfUvrlFho6ARo=
=Y+A0
-----END PGP SIGNATURE-----