Master Slave config

[kanderson]

I currently run Samsung Contact, but I'm looking to switch to this because they no longer wish to support small clients. We're about 100 users.

I currently have a main server, in our head office, where all email bound to or from the internet passes through. This email is then passed over smintfc relay to a slave server, where the employees at that end would then access it. If they then send email back out, it returns to the main server (via smintfc) which passes the message out to the internet.

I need to build a new remote office server, and that will happen before we convert the head office over to Scalix. Will there be any problem with setting up a connection like this between a SC box, and a Scalix box?

This will also affect the other remote sites. Can I move the other remote sites onto Scalix, and then finally do the Head Office last? Or will everything need to move at the same time?

I understand that some things, like webmail, and even the web admin stuff probably won't work very well during the transition, but will it work for the employees to send/recieve email through their Outlook MAPI connections? I'm comfortable enough with the omwhatever commands that I could administrate the servers without the web admin tools temporarily. But I'm wondering if there will be any other problems I should be aware of.

Any suggestions or advice for this situation would be most appreciated.

Thanks
Kev.

[florian]

While Contact and Scalix both have the same roots, Scalix has done some changes to the OpenMail foundation that improve the user experience with the system. These changes necessarily have an impact on the interoperability with other OM-based systems.

Specifically, Scalix has disabled direct SMINTFC communication to OpenMail or Contact systems, so integrating a Contact system directly with Scalix will not work.

You can setup a valid co-existence scenario though where email routing works through Internet messages (i.e. via UNIX queue and Internet Mail Gateway), probably using a "pseudo" domain for the "remote" users.

Directory syncronisation can be archieved using omldapsync and a LDAP-based synchronisation approach.

Therefore, a smooth coexistence and transistion is well possible.

However, given the size of the organization you are working for, maybe a "flash" replacement of all systems would be possible. We have processes and expertise to help you with this.

Maybe you want to contact us or one of our partners directly to find the best possible migration strategy for you.