Hello got a question and not sure "yet" why its not working properly. I setup my dyndns.com account with mailhop relay service since my ISP blocks port 25 inbound.My Edge 2007 Server is able to recieve email inbound from gmail/hotmail etc, send it to my HT via Edge subscription to my CCR node! Works great no issues over port 2525 inbound.Outbound though.. isnt work.. Being first time really setting up Edge with subscription I'm not sure if I'm doing something right. I noticed it created two Send Connectors. Inbound to ADSite1 and ADSite1 to Internet.The inbound to ADSite1 must be working since I am able to get email inbound, but the Outbound isnt work and that is where mail is queuing on my HT serverMy Question is this.. there are only a few settings so it shouldnt be that hard, but I should be using DynDns.org as my smarthost outbound servers I need to modify that connectors network tab to route mail through the following smart host. Do a start-edgesync... and test-edgesync verify everything is successful and at that point mail should flow out right? Tried and that didnt work. I changed it back to Use DNS "MX", but that didnt work either. However when I changed it to that I did receive delay email reports right away for messages that had been queued.Any suggestion please let me know or what else to test. I also emailed DynDns.com because when I telnet into their MX1 from my Edge server and try to send an email as if it was my domain user to gmail.com it tells me access denied.Thanks

Typically when you smarthost to a service like dyndns, you have to authecticate your server to theirs. Is that setup on the send connector to the internet?

When I created the edge subsciption it create the two connectors. The Connect that goes from AD-Site1 to the internet I assumed that I need to change it to use the dyndns.org smarthost under the network tab. I configured them but it doesnt give any options to use a differnet port or username/password.Would it be in the set-sendconnector cmdlet, only thing i see is AuthenticationCredential parameter, but that seems more like credentials for creating the connector.

Yes, use set-connector ( or with EMC)http://technet.microsoft.com/en-us/library/aa998294(EXCHG.80).aspxThere is an example of authenticating in that article:Set-SendConnector "E-Mail to Contoso.com" -AuthenticationCredential $CredentialObject -SmartHostAuthMechanism BasicAuth The second example shows the commands that modify an existing Send connector to use authentication when the Send connector sends an e-mail message to Contoso.com. The Contoso.com e-mail server requires that the local Exchange Server 2007 server authenticate with it to submit e-mail messages. To configure the Send connector to use authentication, you must first run the Get-Credential command and assign the command to a variable. When you run the Get-Credential command, the command asks for the user name and password of the account that will be used during authentication with the Contoso.com e-mail server. In the example, the Get-Credential command is assigned to the $CredentialObject variable. After the authentication credentials are assigned to the $CredentialObject variable, the Send connector can be modified by using the Set-SendConnector cmdlet. The $CredentialObject variable is passed to the AuthenticationCredential parameter. In addition to setting the credentials that will be used, you must set the SmartHostAuthMechanism parameter to BasicAuth to instruct the Send connector to authenticate with the Contoso.com e-mail server by using the supplied credentials.

Yea I messed around today and when I telnet into dyndns.org... their smart hose is.. outbound.mailhop.org so I set it up to on my hub transport. Using the EMC gui it lets you put credentials in there. Now here is something....If I telnet from my HUB to Edge it requires port 2525, SO I changed the connector to use 2525. Once I telnet into my edge when I type rcpt to:me@gmail.com it says "Unable to replay"Why would my edge server say that when I'm Telnet from the hub? shouldnt my edge server accept the msg and even though it cant sent it to outbund.mailhop.org for some reason... I would think it would queue up on the edge and not the HT.. right now all my outbound messages are queuing on the HT.. Test-EdgeSync Passes without any issues.

OK so it must be something with the edge server...keeping it simple in EMC.. under source server.. i removed the edge subscription.. and put the Hub Transport server in there... and the messages sent out with out any issues....So I wonder whats up with my edge server settings.. has to be something since telnet gives me the error unable to relay.. very close to having this all work =) thanks for your replys!

Hi,Since the DynDns.com is using 2525 port to send and receive the email. Thus, the two send connectors for the Edge Subscription need to be set 2525 port for sending the email. One is working from the Hub to Edge, the other one is working from the Edge to the DynDNS.To configure it, you need to run the Set-SendConnector command to do the configuration.http://technet.microsoft.com/en-us/library/aa998294(EXCHG.80).aspxThanksAllen

Ok let me ask this question.. and I think its a small routing issue as well I turned off all the Windows Firewalls, to elimate this issue Here is my network layout.. Cable Modem to Apple Airport Exterme using the 10.x.x.x 255.255.255.0 addressing scheme HyperV server is getting a 10.x.x.2 / 24 address on its External NIC I created a ADSite1 Virtual Swtich 192.168.1.0 /27 I created a DMZ Virtual Switch 192.168.1.226 /27 My HT is in ADSite 1, and is getting 192.168.1.4 DC is 192.168.1.2 Router is 192.168.1.1 (this is the IP on the HyperV Virtual NIC) Edge is 192.168.1.228 for the DMZ NIC Edge is 10.x.x.3 on the external NIC (IP is being issued by Apple Airport... port forwarding for anything 2525 is sent to this IP.. this works since outbound email is being delivered) Router is 192.168.1.227 (this is the IP on my HyperV VIrtual NIC) HyperV is running Routing and Remote Access which has both the DMZ and ADSite1, so they are able to talk. Here is the problem.... The Edge server can not ping the HT server it will time out.. running a -t BUT as soon as I ping from the HT to Edge.. the Edge is able to ping the HT server.. Why would the Edge loose its route to the 192.168.1.0 /27 path? Maybe its my NIC configurations My HyperV is running Routing and Remote Access to connect all the networks.... Also my Edge is Server 2008 SP2...and I have configured both NICs with External Gateways... but reading Server 2008 accepts this configuration. Also both my NIC are using my internal DC for DNS... Can you recommend a better way to configure my NICs? External 10.x.x.2 255.255.255.0 10.x.x.1 DNS 192.168.1.2 WINS 192.168.1.2 DMZ NIC 192.168.1.228 255.255.255.224 192.168.1.227 DNS 192.168.1.2 WINS 192.168.1.2 Sorry so long..but its bugging me that the Edge keeps loosing its router and is unable to ping the HT.. then all of the suggent its able to ping it again.. weirdest thing...

Want to add this.. If I reboot or disabled and enable the nics.. my edge can no longer ping my HT... i have to add a route add 192.168.1.4 MASK 255.255.255.255 192.168.1.225 in order for it to work and be able to ping... not sure why me edge is having all these routing issues, guess its my NIC configuration.. using two default gateways? My Edge server has 1 Receive connector...which is what dyndns.org mail relay is sending to over port 2525 since my ISP blocks port 25.. When I created my Edge subscription it created two send connectors. Exchange Inbound to ADSite1.. which this is obviously working since email is coming in from DynDns to the Edge and then Edge to the HT over port 25 The 2nd send connector is ADSite1 to Internet.. this one I reconfigured to use port 2525.. a smart host of outbound.mailhop.org, and basic authentication using the Edge subscription as the source server, the messages just sits on the HT server destine for the edge.... Now if I try to telnet to the edge server from the HT over port 2525.. it lets me in... but why I type rcpt to:me@gmail.com .. the Edge returns an error 550 5.7.1 unable to relay. Why is the edge unable to relay messages? Also if I go to the Edge subscription and change the Source server tab from the Edge Subscription to the HT server the messages are sent out, but that is from the HT to the dyndns.org.. its not going through the Edge server is it, its going from the HT to outbound.dyndns.org.... I think my issue is the edge server not being able to relay from the error about and also my nic settings of having to add a route add each time for it to be able to ping the 192.168.1.4 for my ht server... Any suggestions would be great!

FIXED IT.. damn took me a bit but narrowed it down!! Now shes working great!! Inbound/Outbound DynDns as my relay host..take that ISP for blocking 25.