Hi there--not sure if this is the right forum, Roughly half of all inbound e-mail gets stuck on the Edge server for an unseemly length of time Here is a typical header dump (all times are UTC): 8/5 9:50:00 p.m. message is sent bounces thru PostIni, etc. 8/5 9:50:05 p.m. message arrives on Edge server 8/6 12:12:02 a.m. message arrives on Hub Any ideas on where I should start? Barnaby Duncan barnaby@naiahedc.org

Hi, Is this issue happening for new created user or for all the user ???, in case of new recipients have a look into this KB : http://support.microsoft.com/kb/936159Ripu Daman Mina | MCSE 2003 & MCSA Messaging

Hello, I agree to what Ripu has said and the article speaks about the issue. However in order to reolve this immediately you could try to force the Edge Sync operation from the Hub server. you could try the options given below: Start-EdgeSynchronization -Server <Hubservername> The synchronization is initiated from the Hub Transport server which you give in for <Hubservername> Only the changes since the last replication will be synced by executing this command. Regards, Yogesh S.

Thank you Ripu & Yogesh, I believe I have found the cause, at least the major symptom anyway. My edge server is named edge, and my hub/client/message server is bigblue. DNS is on the DC, which is a different server, and working fine. From the DC: ping bigblue reply from 192.168.2.7...<1ms so that is fine/as expected. From edge: ping bigblue pinging 205.178.189.129 with 32 bytes... request timed out... also from edge: nslookup bigblue bigblue.domain.com 192.168.2.7 To fix this I hacked the hosts file to point to the correct IP, and now edge transport is taking all of about 1 minute. So any ideas on where this 205 IP came from? I have nerver used any 205 IPs. It's not black-listed, and r-dns pretty much gives me nothing. I'm wide open. Barnaby Barnaby Duncan barnaby@naiahedc.org

Hi Barnaby, Glad to know you solved your problem. Actually, before deploying the Edge server, you should make sure the Edge Transport servers and the Hub Transport servers must be able to use DNS host resolution to locate each other. More information: Configuring DNS Settings for Exchange 2007 Servers http://technet.microsoft.com/en-us/library/bb124896(EXCHG.80).aspx About the IP 205, I guess it is a host computer on the internet since your edge can connect to internet. Frank Wang