SMTP Smart Host - hiding multiple sub-domains
Mark Sparling
Hello!
A friend is trying to connect his disparate mail systems using an SMTP
backbone, along with a connection to the Internet for all. They are going
to eventually migrate completely to Exchange, but they need
interoperability for a while (many thousands of users). NT Mail, Exchange
Server 5.0, and a product called QuickMail are in use.
They would like to have simple sub-domains for email -
us...@exchange.company.com, us...@ntmail.company.com, etc., and for the
outside world to only see us...@company.com. Easy to configure Exchange
users with multiple addresses, probably the other systems as well.
How would mail be routed to the correct SMTP host? Using a smart host (I
have just begun learning about this), it appears all SMTP mail can be
forwarded to a single SMTP host, which then replaces the FQDN header and
puts in the simple company.com. Great. But how does mail make it back in?
Thanks for your help!
Mark Sparling
mspa...@stepinc.com
Ace
Mark, here is how you can do it.
Create a mail domain by making a DNS entry such as
exchange.company.com. IN MX 10 hostname2.foo.company.com
exchange.company.com. IN MX 10 hostname2.foo.company.com
exchange.company.com. IN MX 10 hostname2.foo.company.com
Mark Sparling <mspa...@stepinc.com> wrote in article
<01bc3184$d1309f40$f7b1...@tarheels.stepconsulting.com>...
Ace
Mark, accidently sent it too soon. Ignor the previous posting of mine on
this.
Here is how you can solve this.
Create a mail domain by making a DNS entry such as
exchange.company.com. IN MX 10 hostname1.foo.company.com
exchange.company.com. IN MX 20 hostname3.foo.company.com
Then in Exchange...
Set up secondary address for each user as us...@exchange.company.com
Then set up a primary for each user as us...@company.com
As far as the sending to a relay host... you can do this but it is better
usually to let DNS resovle the host names directly since it only puts it on
the network once that way.
--- Vince
Vince Egan, MCSE
Harris Corporation
ve...@harris.com
impu
Hi,
I belive I understood you right. I'm going to hold the tail of
your question and try to answer that. "all SMTP mail can be
>forwarded to a single SMTP host, which then replaces the FQDN header and
>puts in the simple company.com. Great. But how does mail make it back in?"
if "impu" is the domain, and if SMTP server for "impu" is
mail.impu.com (out going), then POP Server will be pop.impu.com. In
order to be able to use the Internet, I would recommend "Internet
Mail" (if you don't have it in the "Add" list, just install MSIE and
it wizard will ask you "if you would like to install Internet Mail".
Anyway, hope I didn't make things confusing:-))
"When all else fails, read the manuals"
Impu
im...@mindspring.com
impu
"When all else fail, read the manuals".
Thom.M...@asu.edu
> On Sat, 15 Mar 1997 13:07:00 -0800, "Mark Sparling"
> <mspa...@stepinc.com> wrote:
>
> >Hello!
> > A friend is trying to connect his disparate mail systems using an SMTP
> >backbone, along with a connection to the Internet for all. They are going
> >to eventually migrate completely to Exchange, but they need
> >interoperability for a while (many thousands of users). NT Mail, Exchange
> >Server 5.0, and a product called QuickMail are in use.
> > They would like to have simple sub-domains for email -
> >us...@exchange.company.com, us...@ntmail.company.com, etc., and for the
> >outside world to only see us...@company.com. Easy to configure Exchange
> >users with multiple addresses, probably the other systems as well.
> > How would mail be routed to the correct SMTP host? Using a smart host (I
> >have just begun learning about this), it appears all SMTP mail can be
> >forwarded to a single SMTP host, which then replaces the FQDN header and
> >puts in the simple company.com. Great. But how does mail make it back in?
> >
> >Thanks for your help!
> >Mark Sparling
> >mspa...@stepinc.com
The key here is that you want all of your disparate systems to
"masquerade" as company.com. A "smart host" is a mailer that can
authoritatively reject mail (e.g., some mailers are not "smart", meaning
they try to deliver mail but if they can't figure it out, they hand off
the message to a "smart host" instead of sending out an error).
For Exchange, outgoing mail can masquerade as us...@company.com
(Configuration\Site Addressing\Site Addressing). Incoming mail would
easily work also (create MX record in DNS to direct company.com to
exchange.company.com), except that in this case you want several
machines to masquerade as the same host, company.com.
I can imagine several ways to make this work, and it comes down to
having a good mailer acting as company.com. Outside of commercial
products, Unix sendmail (ftp://ftp.sendmail.org) has the ability to
create "user tables," so that us...@company.com is forwarded to
us...@exchange.company.com, us...@company.com is forwarded to
us...@ntmail.company.com, etc. At ASU, we are using Innosoft PMDF
(http://www.innosoft.com).
Before pursuing this, remember that this is not trivial. The database
for directing us...@company.com mail to where.ever must be maintained.
--
Thom McCarty
Arizona State University
impu
Hi,
I belive I understood you right. I'm going to hold the tail of
>forwarded to a single SMTP host, which then replaces the FQDN header and
>puts in the simple company.com. Great. But how does mail make it back in?"
if "impu" is the domain, and if SMTP server for "impu" is
mail.impu.com (out going), then POP Server will be pop.impu.com. In
order to be able to use the Internet, I would recommend "Internet
Mail" (if you don't have it in the "Add" list, just install MSIE and
it wizard will ask you "if you would like to install Internet Mail".
Anyway, hope I didn't make things confusing:-))
"When all else fails, read the manuals"
Impu
im...@mindspring.com
On Sat, 15 Mar 1997 13:07:00 -0800, "Mark Sparling"