Tags: allowthat, deliver, exchange, external, force, internal, mail, microsoft, msdn, route, server, smtp, software
Route all Exchange mail (internal and external) to an SMTP server
On Microsoft » Microsoft Exchange server
6,022 words with 2 Comments; publish: Tue, 20 May 2008 10:15:00 GMT; (300125.00, « »)
I need to force all Exchange mail to be sent to an SMTP server to allow
that SMTP server to deliver the mail. The reason for this is simple.
I'm supporting users that have several mailboxes on different mail
systems. A typical user will have an Exchange mailbox, a procmail
mailbox, and a Cyrus mailbox. The SMTP server will deliver mail to
all these mail systems. Exchange cannot be configured to do this (as
far as I know).
I have set up an SMTP connector so all externally bound mail will be
delivered to the SMTP server, but mail being sent from one mailbox to
another mailbox within the same Exchange server does NOT go through the
SMTP server.
Here is where it gets tricky. Mail being delivered within the same
Exchange server needs to be routed to the SMTP server BEFORE it is
delivered to the mailbox. If mail was delivered to the mailbox as well
as sent to the SMTP server for delivery, the destination Exchange
mailbox would end up with a double delivery.
I've also thought about creating a unique SMTP address for Exchange
users, something like .ms-exchange.itags.org.exchange.widget.com. I then figured that I
could create contact objects for all users that only contains
.ms-exchange.itags.org.widget.com addresses, then set up a GAL that only contains those
contact objects so all mail would be externally bound (and thus go
through the SMTP server). The problem with this is that it breaks the
calendar functionality, free/busy in particular. This is because you
would be attempting to view the calendar for a contact object rather
than an Exchange user.
I've also thought about Journaling, but I can't journal to the SMTP
server, only to an e-mail address.
All Exchange servers are Exchange 2003 with SP1.
I'm at a loss. If anyone has any suggestions or has dealt with this
issue before, please reply. I would be eternally grateful.
http://ms-exchange.itags.org/q_exchange-server_166306.html
All Comments
Leave a comment...
- 2 Comments

- Hi G12,
It can be done but we do not recommend doing it. Exchange should be allowed
to deliver its own email internally at least. You can configure a user
account in AD to forward all email received by the mailbox to another email
address as defined in a contact. I am not sure if you can define multiple
contact or multiple email addresses on a contact. But you could define a
given email address for all users affected say like smarthost.domain.com and
then configure an SMTP connector to route that domain to the smarthost ...
at which point the smarthost can fan it out how ever you define.
To have Exchange route all email that goes thru it to a Smart Host all you
need to do is define the IP of the smart host on the properties of the SMTP
virtual server. Again I would not recommend this as it is know to cause
problems with mail routing especially if you have more than one Exchange
server per site.
Hope this Helps,
--
Matthew Byrd
Microsoft PSS
Run Microsoft Exchange Server Best Practices Analyzer Today
http://www.microsoft.com/exchange/exbpa
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
This posting is provided "AS IS" with no warranties, and confers no rights.
"G12" <gideon12.ms-exchange.itags.org.gmail.com> wrote in message
news:1133368947.325082.195190.ms-exchange.itags.org.g49g2000cwa.googlegroups.com...
>I need to force all Exchange mail to be sent to an SMTP server to allow
> that SMTP server to deliver the mail. The reason for this is simple.
> I'm supporting users that have several mailboxes on different mail
> systems. A typical user will have an Exchange mailbox, a procmail
> mailbox, and a Cyrus mailbox. The SMTP server will deliver mail to
> all these mail systems. Exchange cannot be configured to do this (as
> far as I know).
> I have set up an SMTP connector so all externally bound mail will be
> delivered to the SMTP server, but mail being sent from one mailbox to
> another mailbox within the same Exchange server does NOT go through the
> SMTP server.
> Here is where it gets tricky. Mail being delivered within the same
> Exchange server needs to be routed to the SMTP server BEFORE it is
> delivered to the mailbox. If mail was delivered to the mailbox as well
> as sent to the SMTP server for delivery, the destination Exchange
> mailbox would end up with a double delivery.
> I've also thought about creating a unique SMTP address for Exchange
> users, something like .ms-exchange.itags.org.exchange.widget.com. I then figured that I
> could create contact objects for all users that only contains
> .ms-exchange.itags.org.widget.com addresses, then set up a GAL that only contains those
> contact objects so all mail would be externally bound (and thus go
> through the SMTP server). The problem with this is that it breaks the
> calendar functionality, free/busy in particular. This is because you
> would be attempting to view the calendar for a contact object rather
> than an Exchange user.
> I've also thought about Journaling, but I can't journal to the SMTP
> server, only to an e-mail address.
> All Exchange servers are Exchange 2003 with SP1.
> I'm at a loss. If anyone has any suggestions or has dealt with this
> issue before, please reply. I would be eternally grateful.
>
#1; Tue, 20 May 2008 10:16:00 GMT

- Thanks for replying, Matthew!
So are you saying that by setting up a smarthost in the SMTP virtual
server, all e-mail, even e-mail destined within the same Exchange
server will be sent to the smarthost? This would be exactly what I'm
looking for if it is true. I'm not worried about mail routing because
the non-Exchange SMTP server will handle the mail routing.
Thanks again for your help!
#2; Tue, 20 May 2008 10:17:00 GMT