Instead of perdition you might want to look at nginx:

http://wiki.nginx.org/Main

Alexei


On Tue, Aug 18, 2009 at 12:41 PM, Phil
Pennock<[email protected]> wrote:
> On 2009-08-18 at 11:32 -0700, Ski Kacoroski wrote:
>> At $work we purchased a new mail server (Scalix) and need to migrate
>> from our old mail server (CommunigatePro).  We have 2500 accounts with
>> the largest account about 4.2GB/53000 messages.  Our problem is that in
>> testing several of the imap migration programs available (mailutil,
>> imapsync, MoveIMAPMail) we are looking at roughly 30 days to complete
>> the migration which just is not going to work.  One idea we have for
>> doing this in a weekend is to have 30 processes running in parallel, but
>> I am wondering what other people do to migrate to a new mail server in a
>> large organization.
>
> It's been a while, and when doing migrations I engineered things to have
> common storage so did things differently (ISP mail-systems) but if doing
> this in-house then I'd:
>
>  (1) Configure the gateway inbound MTA to be able to deliver to either
>     of the two systems, or to queue mail pending delivery while an
>     account is locked and kick off a flush when unlocked.
>
>  (2) Use Perdition as an IMAP & POP3 proxy in front of the real servers;
>     make Perdition the name in DNS which all users use.
>
>  (3) Have a migrate script, which for a given user locks the account,
>     migrates the content, updates config for delivery & perdition and
>     then unlocks, so that the MTA will deliver once more.  "Locking" is
>     defined however you care to define it, but using LDAP with common
>     access by both Perdition and your MTA is possibly a decent
>     approach.
>
>  (4) Figure out how many of (3) can be run in parallel and not worry if
>     it takes 3 days or 6 weeks.
>
>  (5) Never Worry (hah!) about future migrations, the implementation is
>     abstracted away behind your proxy and MTA gateway and you can even
>     split users, moving some users to fancier and more expensive
>     systems if needed, or letting sysadmin play with having their
>     account on an experimental system (but plan on putting
>     dual-delivery into the inbound gateway in that case).
>
> http://www.vergenet.net/linux/perdition/
>
> -Phil
> _______________________________________________
> Discuss mailing list
> [email protected]
> http://lopsa.org/cgi-bin/mailman/listinfo/discuss
> This list provided by the League of Professional System Administrators
>  http://lopsa.org/
>

_______________________________________________
Discuss mailing list
[email protected]
http://lopsa.org/cgi-bin/mailman/listinfo/discuss
This list provided by the League of Professional System Administrators
 http://lopsa.org/

Reply via email to