First of all thanks to all for previous post http://social.technet.microsoft.com/Forums/en/exchangesvrgeneral/thread/3418551b-aa10-40cd-8f9b-21a38fe38416. Basically I installed a 2nd Exchange 2003 server and moved users mailbox over. The users could send email fine, but cannot receive email at first. I thought the same If you have installed the new server in the same organization and routing group, then you shouldn't have to do anything We have 2 external MX domains, with 2 SMTP Gateways - one for domain1.com and one for domain2.com. Mailsrv1 has 2 SMTP Connectors - SMTP1 forwards all mail to Smarthost1 for domain1.com, SMTP2 forwards all mail to Smarthost2 for domain2.com. Mailsrv2 has 1 SMTP Connector - SMTP forwards all mail to Smarthost1 for * domains. Connector scope = Entire organization. All mailboxes with domain2.com address are on MailSrv1. I added the First Routing Group, added a SMTP connector with address space * on 2nd server and users can send and receive fine. However we are still having issues with mail delivery between server, Public folders don’t replicate, users on MailSrv2 can’t send message to Public folders on Mailsrv1 server. They simply disappear. Any thoughts ? thanks

Ensure there is no smart host on the SMTP virtual server. Check that nothing is scanning/blocking SMTP traffic. AV is notorious for doing this. Check that you can telnet to port 25 of the other server using IP address, name and FQDN. Public Folder replication goes over SMTP as well, so if something is stopping email flowing between the servers, the public folder replication will fail as well. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

Thanks Simon Yes I can telnet to the other server. Question - if both servers are in the same Default Routing Group do I need to create a SMTP connector for 2nd server? Shouldn’t it just use the Default SMTP Virtual Server? Lynden . I also found this - http://searchexchange.techtarget.com/answer/Smoothly-adding-a-second-Exchange-server-to-your-organization To fix this, you need to remove the smarthost settings from the SMTP virtual server on Server A, and create a SMTP Connector for address space *. You can make Server A a bridgehead, or make both servers bridgeheads should you wish, and configure the smarthost on the Connector's settings. Once you do this, Server A will be able to send mail to recipients on Server B directly, and only direct mail for recipients not in your org to the smarthost will let you know Lynden

Thanks OK I now have sending/receiving emails internally/externally working on both servers. However still no Public Folder replication or sending email to a public folder on 2nd Exchange server. Lynden

Ensure there is no smart host on the SMTP virtual server. Check that nothing is scanning/blocking SMTP traffic. AV is notorious for doing this. Check that you can telnet to port 25 of the other server using IP address, name and FQDN. Public Folder replication goes over SMTP as well, so if something is stopping email flowing between the servers, the public folder replication will fail as well. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

Public Folder replication can take some time, therefore if you have added the second server to the list of replicas, you will just need to be patient. Message Tracking will show the replication traffic, and you can confirm it is being delivered to the second server. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

Weekend is finished and Public folders are still not appearing on the 2nd Server. PF Replication set to every 2 hours. Replication tab says replicate to both servers. PF all have an email address. Exchange Admins have full control. 1st Server - In Sync, 2nd Server - Local Modified. If I go into Message Tracking and search for messages from Public Folder Store (2nd server) I get Subject=Hierarchy Message submitted from Store, Message submitted to Categorizer, Started outbound Transfer of Message, Message transferred to 1^st Server through SMTP. But if I do Message Tracking and search for messages from Public Folder Store (1st server) I get nothing? Currently looking at – http://blogs.technet.com/b/exchange/archive/2006/01/17/417611.aspx & http://mostlyexchange.blogspot.com/2006/10/public-folder-hierarchy-replication.html Lynden

Why is replication set to every two hours instead of "Always Run"? I would check that the replication priority is set to Normal and then use the tools in ESM to propagate the replication schedule and priority to all folders. When checking message tracking I never put in recipient or sender. Just track all messages that the server has received. You will see the public folder content as it sticks out somewhat. You have checked the queues to ensure that they are clear and the messages aren't hanging around? Simon.Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

Why is replication set to every two hours instead of "Always Run"? I would check that the replication priority is set to Normal and then use the tools in ESM to propagate the replication schedule and priority to all folders. When checking message tracking I never put in recipient or sender. Just track all messages that the server has received. You will see the public folder content as it sticks out somewhat. You have checked the queues to ensure that they are clear and the messages aren't hanging around? Simon.Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

Thank you Simon – appears to be working now. Seems the previous administrator had added Exchange admin and Exchange service account to Domain Admins. I set Replication to Always and Normal and I removed the Deny Send As Receive As for Domain Admins from the top of Public Folders Heirarcy. Restarted the Exchange services and Replication started. User on 2nd server can email Public Folder on 1st server now. A combination of smarthost, permissions, replication issues. Now I can work on upgrading to Exchange 2010 Next question - how do you deal with managers 9Gb mailboxes ! J