Re: TLS encryption

Yes, you don't need to do anything else, nor play with the Connector costs.

I feel that I have everything configured correctly but immediately get the
550 5.7.1 Unable to relay when sending a message to the domain space that is
configured on the secure connector.

Did you mean trying to send outbound mail over the new SMTP virtual server?
--
Bharat Suneja
MVP - Exchange
www.zenprise.com
NEW blog location:
www.exchangepedia.com/blog
----------------------------------------------



"John" <John@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D3B37C9C-9056-48B3-BF41-48FA16ED3C4D@xxxxxxxxxxxxxxxx
Ok... so in my case I have a server that has two IP addresses assigned to
one NIC. The default connector and default smtp virtual server are
assigned
to the primary IP address of the server. Let's say 192.168.5.20. The
additional connector and smtp virtual server that we want to use for TLS
is
assigned to the secondary IP address. Let's say 192.168.5.30. The secure
connector is configured in the address space with a specific domain.
Let's
say... fakedomain.com. The default connectors address space is
configured
with an asterick (*). The default connector has a local bridgehead of the
server name itself and the default smtp virtual server. The secure smtp
connector has a local bridgehead server of the server name itself with the
secure smtp virtual server. Is there anything in the configuration that I
should also check for? Do I need to change the cost on any of the address
spaces.

I feel that I have everything configured correctly but immediately get the
550 5.7.1 Unable to relay when sending a message to the domain space that
is
configured on the secure connector.

Thanks for you help.


"Bharat Suneja [MVP]" wrote:

Yes, mail is always routed out using the Connector (and whatever SMTP
virtual server it uses as a Bridgehead) that has the closest address
space
for the recipient. E.g. if you have a Connector for foo.somedomain.net
and
somedomain.net, mail for foo.somedomain.net will always be routed over
the
Connector for foo.somedomain.net.

Even if the Connector is down, and a Connector with more generic
address-space like * is available, messages will be queued till the
Connector with the more specific address-space becomes available.

--
Bharat Suneja
MVP - Exchange
www.zenprise.com
NEW blog location:
www.exchangepedia.com/blog
----------------------------------------------



"John" <John@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:E67FE2BC-3D86-4BFB-9EB8-9D5355AE993D@xxxxxxxxxxxxxxxx
Ok, that's what I thought. I have a connector configured with two
specific
address spaces. The connector is configured to utilize a newly created
smtp
virtual server. So you're saying that the client relies on the routing
from
the server config and the server won't try to utilize the default smtp
virtual server and connector since the address space is defined in a
different connector. Basically the mail server is smart enough to
determine
that the mail should utilize the new TLS connector instead of the
default
one? Any ideas why I would immediately get a smtp;550 5.7.1 Unable to
relay
when sending the E-mail?

Thanks

"Bharat Suneja [MVP]" wrote:

Outlook clients don't do the message routing - they submit messages to
the
Store using MAPI. The server routes the mail based on routing info,
including presence of Connectors for specific address spaces
(domains).
--
Bharat Suneja
MVP - Exchange
www.zenprise.com
NEW blog location:
www.exchangepedia.com/blog
----------------------------------------------



"John" <John@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:426BF2F8-791F-478E-AB1C-6BC2FA01EDFC@xxxxxxxxxxxxxxxx
I'm currently running Exchange 2003 sp2. I'm in the process of
configuring
an smtp virtual server for specific domains for TLS encryption.
I've
configured the virtual server and connector and wasn't sure if there
was
anything else needed (E-mail policy, etc...). How does an Outlook
client
know that it needs to route mail through the new smtp virtual server
instead
of the default. I'm currently getting undeliverable bounceback
messages
to
the specific domain name with the error of smtp;550 5.7.1 Unable to
relay

Any help would be greatly appreciated.








.

Relevant Pages

  • Re: TLS encryption
    ... I would compare your default smtp virtual server settings with your new ... Is the Connector pointed to a smarthost or is it using DNS to resolve the ... the new secure connector which has the new virtual smtp server as the ...
    (microsoft.public.exchange.setup)
  • Re: TLS encryption
    ... configured on the secure connector. ... Did you mean trying to send outbound mail over the new SMTP virtual server? ...
    (microsoft.public.exchange.setup)
  • Re: TLS encryption
    ... The default connector and default smtp virtual server are assigned ... Is there anything in the configuration that I ...
    (microsoft.public.exchange.setup)
  • Re: Can send but not receive email on Exchange 2003
    ... SMTP Virtual Server properties, Access tab, Connection button ... all addresses should be able to telnet to your box. ... > Created a new SMTP Virtual Server and pointed the connector to it. ...
    (microsoft.public.exchange.connectivity)
  • Re: Concept of SMTP-connectors
    ... The use of the SMTP Connector, ... would be to make sure that outbound messages are ... connector instead of going over the virtual server directly? ... But the connector directs OUTBOUND messages. ...
    (microsoft.public.exchange.admin)