Very Computer

I've created my own testing environment for testing e-mail encryption
and such, where I have two Exchange servers simulating two different
companies. They have their own DNS that does not look to the root
hints, so I can pretty much enter any MX record I want.

Now, our Development people would like a similar setup so they can
test applications that send out Internet mail, without the mail
actually going out.

Not a problem. I can set up the same scenario for them and fake out
any MX record they'd like, and make a mailbox for it on the receiving
test Exchange server.

EXCEPT, we could be talking hundreds of domains and mailboxes here. So
what I'd really like to do is have some sort of router process or
server that sees all mail for companyA.com and routes it to a single
mailbox, all mail for companyB and routes it... and so on.

Or conversely, some sort of test server that will create a mailbox for
any unique incoming e-mail address.

I'm open to suggestions!!!

You can use host file entries to route mail for particular domains to
wherever you want.  Another thing you could do is populate the routing table
of the IMS to relay for your test domains, to the receiving SMTP box,

--

regards,
Michael Abbaticchio
Microsoft Exchange Server MVP
http://www.exchangemvp.com

Quote:> I've created my own testing environment for testing e-mail encryption
> and such, where I have two Exchange servers simulating two different
> companies. They have their own DNS that does not look to the root
> hints, so I can pretty much enter any MX record I want.

> Now, our Development people would like a similar setup so they can
> test applications that send out Internet mail, without the mail
> actually going out.

> Not a problem. I can set up the same scenario for them and fake out
> any MX record they'd like, and make a mailbox for it on the receiving
> test Exchange server.

> EXCEPT, we could be talking hundreds of domains and mailboxes here. So
> what I'd really like to do is have some sort of router process or
> server that sees all mail for companyA.com and routes it to a single
> mailbox, all mail for companyB and routes it... and so on.

> Or conversely, some sort of test server that will create a mailbox for
> any unique incoming e-mail address.

> I'm open to suggestions!!!

That's not really my problem. That's the easy part, and I can do that
with a test environment DNS. My problem is that the developers will be
testing with literally hundreds of different (outside) e-mail
addresses. I need to have those messages received in a mailbox so they
can see them.

What I want to get away from is manually creating mailboxes for all
those addresses (or manually entering hundreds of SMTP addresses for a
mailbox).

One thought that occurs to me is using the directory import to create
an incoming mailbox with ALL the test e-mail addresses associated with
it.

It would be easier to create individual custom recipients, and then populate
them into a dl that has a single SMTP address.

--

regards,
Michael Abbaticchio
Microsoft Exchange Server MVP
Do not attempt to email me direct from
here.  Visit my web site,
and click on my email link..
http://www.exchangemvp.com

Quote:> > You can use host file entries to route mail for particular domains to
> > wherever you want.  Another thing you could do is populate the routing
table
> > of the IMS to relay for your test domains, to the receiving SMTP box,

> That's not really my problem. That's the easy part, and I can do that
> with a test environment DNS. My problem is that the developers will be
> testing with literally hundreds of different (outside) e-mail
> addresses. I need to have those messages received in a mailbox so they
> can see them.

> What I want to get away from is manually creating mailboxes for all
> those addresses (or manually entering hundreds of SMTP addresses for a
> mailbox).

> One thought that occurs to me is using the directory import to create
> an incoming mailbox with ALL the test e-mail addresses associated with
> it.

If you were going to do this, you would also need to set the IMS routing
table to receive all those domains as inbound.  Anyway you look at it, you
are looking at a bit of data import work.

--

regards,
Michael Abbaticchio
Microsoft Exchange Server MVP
Do not attempt to email me direct from
here.  Visit my web site,
and click on my email link..
http://www.exchangemvp.com

Quote:> > You can use host file entries to route mail for particular domains to
> > wherever you want.  Another thing you could do is populate the routing
table
> > of the IMS to relay for your test domains, to the receiving SMTP box,

> That's not really my problem. That's the easy part, and I can do that
> with a test environment DNS. My problem is that the developers will be
> testing with literally hundreds of different (outside) e-mail
> addresses. I need to have those messages received in a mailbox so they
> can see them.

> What I want to get away from is manually creating mailboxes for all
> those addresses (or manually entering hundreds of SMTP addresses for a
> mailbox).

> One thought that occurs to me is using the directory import to create
> an incoming mailbox with ALL the test e-mail addresses associated with
> it.