RE: [cobalt-users] Secondary MX

["SteelHead" <bill@xxxxxxxxxxxxxxx>]

! -----Original Message-----
! From: cobalt-users-admin@xxxxxxxxxxxxxxx
! [mailto:cobalt-users-admin@xxxxxxxxxxxxxxx]On Behalf Of Paulick, Jim
! Sent: Friday, November 01, 2002 12:57 PM
! To: 'cobalt-users@xxxxxxxxxxxxxxx'
! Subject: RE: [cobalt-users] Secondary MX
!
!
! secondary mx records are used for the same reason as secondary
! dns servers.
!
! they are only used when the first one fails, they are not an option.
!
! if you have two entries for mx records, the first one (or the one
! with higher priority, will always be used, unless it is down)
!
! you can have the new accounts go to a different domain and then
! they can be sent to your place instead of the HQ of the company.
!
! but if you want to keep the current domain, you will only have
! one mx record for that domain, so it either has to go to one
! place, or another.
!
! i may be full of it...
!
! i'm sure someone will correct me if I am.
!
!
! -----Original Message-----
! From: Oger [mailto:oger@xxxxxxxxx]
! Sent: Thursday, October 31, 2002 4:45 PM
! To: cobalt-users@xxxxxxxxxxxxxxx
! Subject: [cobalt-users] Secondary MX
!
!
! Greetings list...
!
! Background:  I have a customer with a worldwide presence.  They use their
! corporate network to host everything EXCEPT www, which I provide for them.
! Now their local office would like to have some authority over their e-mail
! as well.  They want to have the home office handle all the existing mail,
! and have us handle new e-mail accounts they set up.  They do NOT want to
! migrate all their accounts to us, but for setting up new accounts we are
! much more responsive than their IT department.
!
! Here's my question:  If I have their IT dept. set up an MX record with the
! name of our host (I guess we'll need an A record, too) and then
! if an e-mail
! is sent to an address that is not sent to the mailserver at Headquarters,
! will it fall to ours?
!
! Thanks!
!
! --Chris
!
!
Changing the MX by itself will not work, but you could create a subdomain
such as 1.userdomain.com and mx those, get a vairation of the domain such as
usersdomain.com instead of userdomain.com.  Another option could be to
prefix all email and have it bounce to your server.  You could also get a
list of current userids and have all mail routed to your server, bouncing
the list to their server.

MX is just as Jim suggested.  You have very limited choices, these are a
couple that jump to mind.

bill