Exchange 2013 user cannot mail 2010 user RRS feed

  • Question

  • Hello All, I am migrating from 2010 to 2013. The Exchange Server Deployment Assistant is proving very helpful thus far. I created a mailbox in 2013 and attempted to email a 2010 user. No luck - the email gets stuck in the queue "Last Error: 400 4.4.7 Message delayed". I can see that it is attempting to send the email to the correct database in 2010 but that is the extent of my troubleshooting knowledge.

    I have yet to complete the step "Enable and Configure Outlook Anywhere" which states: "To allow your Exchange 2013 Client Access server to proxy connections to your Exchange 2010 servers, you must enable and configure Outlook Anywhere on all of the Exchange 2010 servers in your organization." - I haven't yet done this because I didn't want anything destructive to happen to the current 2010 server, but perhaps to enable a 2013 user to send to a 2010 user this step needs to be completed - thoughts? Btw, 2010 can successfully email a 2013 user. Is it a particular receive connector that I need to modify?

    Cheers, db.

    Thursday, September 4, 2014 12:17 PM


All replies

  • Hi Dennis,

    if you go to your Ex 2010 Server, please install Telnet-Client ; you can do this from Powershell using "install-windows-Feature telnet-client".

    1. run a Powershell or CMD
    2. telnet exchange2013server 25
    Does it connect using the Exchange 2013 CAS / Transport Server Name?
    If no, please check
    1. is there any anti Virus / Firewall Software blocking the Connection?
    2. is there any Firewall on the Network blocking the SMTP Connection?
    3. does your receive connector include the subnet of your Exchange 2013 CAS server?

    If you cannot connect verify please the remote IP range includes your new servers ,  check it running
    Get-ReceiveConnector  | fl name,binding,remoteipranges

    from Powershell. If required, use set-receiveconnector to Change it. http://technet.microsoft.com/de-de/library/bb125140(v=exchg.150).aspx


    Thursday, September 4, 2014 12:40 PM
  • Does the Receive Connector allow for "Exchange server" authentication. I noticed that was the cause in another discussion. I thought that Exchange servers could send/receive internally without additional configuration or adjustments but that may have changed with Exchange 2013.


    Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

    Thursday, September 4, 2014 1:08 PM
  • For some reason I completely missed the other discussion re. this issue.

    Enabling "Exchange Authentication" for the receive connector solved the problem.

    Many thanks.

    Cheers, db.

    Thursday, September 4, 2014 10:42 PM