Hi, I've problem to receive email from edge server. I've follow article best practice article : http://technet.microsoft.com/en-us/library/bb310755%28EXCHG.80%29.aspx When i telnet from edge server to hub transport email successful in. when using gmail or yahoo to send email i failed to receive. On my edge server have many queue. Below are result i did a test-edge synchronization from hub transport server: Name : KKLWES01 LeaseHolder : CASHT02 LeaseType : Option ConnectionResult : Succeeded FailureDetail : LeaseExpiry : 4/25/2010 12:46:23 PM LastSynchronized : 4/25/2010 11:46:23 AM CredentialStatus : Synchronized TransportServerStatus : Synchronized TransportConfigStatus : Synchronized AcceptedDomainStatus : Synchronized SendConnectorStatus : Synchronized MessageClassificationStatus : Synchronized RecipientStatus : Synchronized CredentialRecords : Number of credentials 6 Name : KKLWES02 LeaseHolder : CASHT02 LeaseType : Option ConnectionResult : Succeeded FailureDetail : LeaseExpiry : 4/25/2010 12:46:24 PM LastSynchronized : 4/25/2010 11:46:24 AM CredentialStatus : Synchronized TransportServerStatus : Synchronized TransportConfigStatus : Synchronized AcceptedDomainStatus : Synchronized SendConnectorStatus : Synchronized MessageClassificationStatus : Synchronized RecipientStatus : Synchronized CredentialRecords : Number of credentials 6 Please Advise, ThanksEzzy

Hello. Did you get any NDR ? Per your post i assume you have only a problem to send email for yahoo or Gmail. Do you use Public IP to send email? Some Email ISPS don't trust dynamic ips. So please verify that information. Regards Chinthaka Shameera | MCITP: EA | MCSE: M | http://howtoexchange.wordpress.com/

Hello Ezzy, Please try one more time all this step :-- Checked few thing :-- 1) Ping the HUB & EDGE server from each other 2) Checked whether all the proper Port (25, 50306 & 50389 )are open For mail flow between the HUB & EDGE server 3) If above things are perfect then --- Re subscribe the HUB & EDGE server Create XML file on the EDGE server with cmd. --> New-Edgesubscription -filename c:\edge.xml Removed the Edge subscription from the HUB server and Restart the Transport & ADAM service Then Ran Start & Test-EdgeSynchronization cmdlet on the Exchange Management Shell on Hub Again Restart the Transport server on the HUB & ADAM service on the EDGE It will fix the problem. For More information please go through this article :-- White Paper: Edge Subscription and Synchronization http://technet.microsoft.com/en-us/library/bb310755(EXCHG.80).aspx#EdgeSyncsynchronization MicroSoft Exchange Admin. & Connector EXCHANGE2010, MCSE, MCTS, MCSA MESSAGING, CCNA & GNIIT

Hello PKT & Chinthaka, Thank for reply, Email can send to internet and no issues . Main issue is receive email from internet to internal. On the edge server I got this 2 error. the error as below; 1. 451 4.4.0 Primary Target IP Address responded with:"451 5.7.3 Cannot achieve Exchange Server authentication."Attempted failover to alternate host,but that did not succeed. Either there are no alternate hosts,or delivery failed to alternate all hosts. 2. 451 4.4.0 Primary Target IP Address responded with:"421 4.2.1 unable to connect" "Attempted failover to alternate host,but that did not succeed. Either there are no alternate hosts,or delivery failed to alternate all hosts. but if I telnet from edge server to Hub Transport - email successful in. I'm not sure why email stuck in queue edger server. Please Advise, Thanks. Ezzy

Hello Mohd Ezzy, Perfect -- Email can send to internet and no issues . Main issue is receive email from internet to internal. On the edge server I got this 2 error. the error as below; 1. 451 4.4.0 Primary Target IP Address responded with:"451 5.7.3 Cannot achieve Exchange Server authentication."Attempted failover to alternate host,but that did not succeed. Either there are no alternate hosts,or delivery failed to alternate all hosts. Ans. It is because you modified the Permission on the Default receive Connector on HUB Or EDGE server. 2. 451 4.4.0 Primary Target IP Address responded with:"421 4.2.1 unable to connect" "Attempted failover to alternate host,but that did not succeed. Either there are no alternate hosts,or delivery failed to alternate all hosts. Yes, You telnet from edge server to Hub Transport - email successful in. Please check the Receive connector on Both the server and configure it properly as default Or try to delete the Connector's and resubscribe the HUB & Edge. MicroSoft Exchange Admin. & Connector EXCHANGE2010, MCSE, MCTS, MCSA MESSAGING, CCNA & GNIIT

Hello PKI, What you mean resubscribe the HUB and Edge? how to configure default receive connector? If I delete a receive connector on Edge server how about email in queue? it will deleted together? Thanks Ezzy

Hi, Whether you changed Default Receive Connector setting before? If not, I think the default receive connector setting allows Edge to authenticate to Hub Server to deliver message. Please check following two conditions: When you telnet to Hub Server from Edge, after typeing Ehlo, which SMTP commands are received? When you telnet to Hub Server from Hub server locally, after type Ehlo, which SMTP commands are received? Please compare the SMTP commands you got for above two conditions. In case, some firewall between edge server or hub server filter smtp verbs, you may encounter the problem. Please also enable protocol logging on the Hub Server receive connector and check whether you can find any clues. Mike

Hi Mike, This i s answer: When you telnet to Hub Server from Edge, after typeing Ehlo, which SMTP commands are received? 220 KKLWES01.rurallink.gov.my ESMTP Service ready ehlo kklwes01 250-Requested mail action okay, completed 250-SIZE 10485760 250-AUTH NTLM LOGIN 250-8BITMIME 250 OK 451 Requested action aborted: local error in processing When you telnet to Hub Server from Hub server locally, after type Ehlo, which SMTP commands are received? 220 CASHT01.rurallink.gov.my Microsoft ESMTP MAIL Service ready at Mon, 26 Apr 2 010 12:40:56 +0800 ehlo casht01 250-CASHT01.rurallink.gov.my Hello [127.0.0.1] 250-SIZE 250-PIPELINING 250-DSN 250-ENHANCEDSTATUSCODES 250-STARTTLS 250-X-ANONYMOUSTLS 250-AUTH NTLM LOGIN 250-X-EXPS GSSAPI NTLM 250-8BITMIME 250-BINARYMIME 250-CHUNKING 250-XEXCH50 250 XRDST I also already enable logging on hub. but can't see any log files. Thanks,Ezzy

Hey, From the test above, I think there are some firewalls/devices between Hub and Edge server filter some SMTP verbs. So you get different response when telnet to Hub from Edge or Hub locally. I think it is the cause of the issue. I recommned that you configure the Edge to bypass the firewall/device if possible and check the result again. Thanks, Mike

Hi Ezzy, Agree with Mike, some firewall devices or third party scan software would cause the issue. Especially those are not warranty by MS. Regards! gavin