Re: Change to SmartHost Failed
- From: "Ed Crowley [MVP]" <curspice@xxxxxxxxxxxxxx>
- Date: Tue, 27 Nov 2007 20:21:20 -0800
I'm assuming we're talking about Exchange 2003 since you didn't say.
Comments inline below.
--
Ed Crowley
MVP - Exchange
"Protecting the world from PSTs and brick backups!"
"Mr_Huang" <mr.huang.hk@xxxxxxxxx> wrote in message
news:95f37303-0553-4d4c-ba7b-2e319bd25e5a@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Dear guru,
We have configured in the back-end using "DNS to route to each address
space on this connector" and add two front-end in the local bridgehead
under the Routing Groups -> Connectors. Now, we would like to route
our outgoing emails to two the email gateways for anti-virus. Having
configured the two IPs under the SmartHost under Connectors of the
back-end Exchange, the outgoing email to external party would NOT work
at all, then we receive an error,
That is your mistake. Do not configure a smart host in your back-end SMTP
virtual servers. You created an SMTP Connector (correct?) and specified the
two front-end servers as bridgehead servers, so that dictates that all mail
going out of your organization will route through the front-end servers. If
you want to specify your antispam servers as smart hosts, you configue that
in the properties of the SMTP Connector, not on any of the SMTP virtual
servers.
Your message did not reach some or all of the intended recipients.
Subject: RE: testing aage
Sent: 11/27/2007 3:19 PM
The following recipient(s) could not be reached:
xyz@xxxxxxxxx on 11/27/2007 3:19 PM
There was a SMTP communication problem with the
recipient's email server. Please contact your system administrator.
<frontend1.domain.com #5.5.0 smtp;550 Requested action not
taken - Recipient not allowed>
Tried to restart the SMTP and Routing Engine on the back-end and front-
end (not much related) but it could NOT help,
It seems there's some configuration error in the back-end Exchange
Questions:
1. Can we use the Anti-spam email gateway in replacing the Front-end
Exchange?
You can use the front-end as bridgeheads or not, but in either case,
configure the smart hosts in the SMTP Connector, not in any of the SMTP
virtual servers.
2. Should we configure the SmartHost in the Front-end instead?
No. See above.
3. Do we need to create a new connector under the routing group
instead of modifying the old setting?
You need an SMTP Connector, probably with an Address Space of "*" (without
the quotes).
4. Is it related to the bridgehead setting under the connector,
however we could not able to remove so?
No. The local bridgehead specifies which of the Exchange servers will route
the mail to the destination domain or to the smart host as specified in the
SMTP Connector.
Please advise,
Huang
.
- References:
- Change to SmartHost Failed
- From: Mr_Huang
- Change to SmartHost Failed
- Prev by Date: Re: Exchange Management Console slow
- Next by Date: Exchange 2003: Multiple sites via slow link
- Previous by thread: Change to SmartHost Failed
- Next by thread: Exchange 2003: Multiple sites via slow link
- Index(es):