I find that behavior to be normal -- non-desirable, but normal. -----Original Message----- From: William Holmes [mailto:wtholmes@xxxxxxxxxxxxxx] Sent: Monday, July 18, 2005 11:50 AM To: [ExchangeList] Subject: [exchangelist] Connector Question http://www.MSExchange.org/ Hello, I have an SMTP connector question. I have setup a connector to handle an SMTP address called: otherdomain.com. This connector sends mail through a smart host. I have configured two local bridgeheads and have selected their default SMTP Virtual Servers. When I send a message the routing goes correctly except for one thing: Instead of the outbound connection from my bridgehead using the Default SMTP Virtual Server, its using one of the other Virtual Servers on the Bridgehead. When I look at the message headers after it has been received by otherdomain.com they indicate that source IP address is for one of the other SMTP virtual servers. Is this normal behavior. I would have thought that after specifying a specific virutal server that the mail would have gone out through that one and not one of the others. Thanks Bill ------------------------------------------------------ List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp Exchange FAQ: http://www.msexchange.org/pages/larticle.asp?type=FAQ ------------------------------------------------------ Other Internet Software Marketing Sites: World of Windows Networking: http://www.windowsnetworking.com Leading Network Software Directory: http://www.serverfiles.com No.1 ISA Server Resource Site: http://www.isaserver.org Windows Security Resource Site: http://www.windowsecurity.com/ Network Security Library: http://www.secinf.net/ Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com ------------------------------------------------------ You are currently subscribed to this MSEXchange.org Discussion List as: michael@xxxxxxxxxx To unsubscribe visit http://www.webelists.com/cgi/lyris.pl?enter=exchangelist Report abuse to listadmin@xxxxxxxxxxxxxx