Project Detail

Description

Hello,

We are a company with about 25 user accounts and about 36 GB of mail data (including cyrus squatter indexes).

Our mail is currently served by a Centos4 mail server with postfix as MTA and cyrus as backend. Our users access their mail via secured IMAP (TLS) or via squirrelmail (https). Our users and theirpasswords are stored in an openldap server. Postfix, cyrus imap and openldap used are the from latest version from Centos 4. We use a combination of spamassassin, clamav and sagator to reject spam and viruses. We also have a mailman service for about 30 mailing-lists. We have a 4Mb/s SDLS connexion to Internet.


Our server is reaching its limits (both storagewise and CPUwise) and instead of upgrading it, we would like to move to google apps (Premier Edition). We are looking for someone to manage this move. Here are some of our most important requirements:

Probably easy:
a) our users should keep all their existing mails
b) our users should be able to access their mails through IMAP (SSL or TLS) with their thunderbird clients
c) some users have special aliases (like johnny _at_ ourdomain.com -> john _at_ ourdomain.com)

Harder ?
d) our users should be able to use both firstname _at_ ourdomain.com and lastname _at_ ourdomain.com to get their mails (in our current setup, lastname is the account name, and we create the firstname alias based on ldap data)
e) hyphen-addressing should continue to work (ie one user 'john _at_ ourdomain.com' should be able to give any address of the form 'john-anything _at_ ourdomain.com' and get their mail automatically in their mailbox
f) our users should continue to get mail for different domains (john _at_ ourdomain1.com and john _at_ ourdomain2.com should both work)
g) We might want to introduce a third domain (john _at_ ourdomain1.com and john _at_ ourdomain2.com and john _at_ ourdomain3.com should all work)
h) the transition should take place during a weekend (Paris time) and no mails should be lost

Even harder ?
i) I would like the passwords for the mail accounts to be fetched from our ldap server live
j) Creation of a user in ldap should also create the associated mailbox and configuration on google apps
k) We want to be able to continue to use our mailing-lists (either self-hosted or via google apps)
l) a special alias 'everybody _at_ ourdomain.com' should send mail to everybody (with a valid ldap account)
m) some special aliases should be created/updated based on ldap group membership. Eg as long as a user is in the ldap group 'accounting' they should receive mails sent to 'accounting _at_ ourdomain.com'


A tgz file with our current configuration files is available upon request.


What I expect:
1) understanding of our situation and critical analysis of our requirements (maybe I forgot something important !). Feaseability analysis of our requirements a) to m). If some requirements are not (or do not seem) possible, discussion with me to find the best workaround
2) detailed technical documentation on HOW to do the move. Should we have a problem, the 'rollback' procedure should be clear too.
3) Help with the actual move

Each step should be validated by me prior to taking the next step.


Best regards,
Antoine

NOTE1: if g) is easy, we could start with the setup of ourdomain3.com on google apps, get things working, and only once everything is OK change the MXs for our other domains and switch the users to use google apps.

NOTE2: c) d) e) f) and g) mean that a user "john doze" with special alias johnny should be able to read their mails sent the following addresses from the same account:
john _at_ domain1.com
doze _at_ domain1.com
johnny _at_ domain1.com
john _at_ domain2.com
doze _at_ domain2.com
johnny _at_ domain2.com
john _at_ domain3.com
doze _at_ domain3.com
johnny _at_ domain3.com
john-anything _at_ domain1.com
doze-anything _at_ domain1.com
john-anything _at_ domain2.com
doze-anything _at_ domain2.com
john-anything _at_ domain3.com
doze-anything _at_ domain3.com