two mail servers migration setup
I would appreciate any advice on how to setup the following:
There is an existing Solaris 9 mail server on the network running sendmail with domain name ab.example.com.
I抎 like to setup Java Messaging 6.2 server on the same network that would be able to process mail in parallel with existing mail server during transition period.
The setup should provide a possibility to migrate part of the users from the existing server and eventually be moved to production.
The first question is should I give new server a different domain name for example cd.example.com or test.ab.example.com?
How to setup MX records that would let two servers work together in parallel?
[701 byte] By [
Andre_R] at [2007-11-26 9:30:49]
# 1
> I would appreciate any advice on how to setup the
> following:
>
> There is an existing Solaris 9 mail server on the
> network running sendmail with domain name
> ab.example.com.
>
> I抎 like to setup Java Messaging 6.2 server on the
> same network that would be able to process mail in
> parallel with existing mail server during transition
> period.
Um, maybe.
Messaging Server has several places with "names". The machine name. The "default domain" are two that make sense to talk about.
First, what is the format of your intended mail addresses? "user@example.com"? If so, that's what I'd set your default domain to.
Messaging Server is different from sendmail in that it does NOT use the machine name as part of the address for mail routing. The LDAP entry for each user contains a "mailhost" attribute that Messaging uses for routing.
You can set up your Messaging Server as the MX, and set your old server up as a "domain smarthost" (see doc for how to set this up). What this does, is tell Messaging that any mail addressed to a user that's NOT in ldap is to be sent to your sendmail box. That way, you can migrate users to Messaging Server, and they'll get mail.
>
> The setup should provide a possibility to migrate
> part of the users from the existing server and
> eventually be moved to production.
>
> The first question is should I give new server a
> different domain name for example cd.example.com or
> test.ab.example.com?
I'd suggest "example.com" for the "default domain"
>
> How to setup MX records that would let two servers
> work together in parallel?
Point your MX record to the new Messaging Server.
# 3
Well, we don't actually have a "Provisioning Guide" for Messaging 6.x, but the concept and execution are basically the same as for 5.2. The only real difference is that Schema 2 doesn't have a 'dc tree', all is in the same tree in ldap:
http://docs.sun.com/source/816-6018-10/domains.htm#29147
Please note, we're talking about a "domain smarthost" not a "smarthost" There's a difference.. .
