none
Mail Flow in CoExistence routed through old Exchange server

    Question

  • We are at the tail end of our co-existence migration from exchange 2007 to 2013 and have noticed recently that all external mail is flowing through our old 2007 server.  Is there a way to test and see which receive/send connectors are in use when external email comes in?  We can see that the mail hits our SPAM firewall, and is routed to our edge servers, then sent from the edge to our old 2007 mail server which then transfers the item to our 2013 mail server.

    Another question would be do we even need to forward the mail from the SPAM firewall to the Edge or should it go directly to the mail servers?

    Also, could there be some kind of edge subscription on the old server that is affecting the mail flow?

    Any suggestions/help would be greatly appreciated.

    Tuesday, April 26, 2016 5:31 PM

Answers

  • If your Edge is routing to internal Exchange 2007, then you need to change those connectors, but the best method is probably to reconfigure your Edge Subscription.

    Get-ReceiveConnector and Get-SendConnector tell you all about the routing.

    If the Edge servers don't provide you with any useful functions, then there's no reason the antispam appliance, server or cloud service can't send mail straight to an Exchange 2013 server.


    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Celebrating 20 years of providing Exchange peer support!


    Tuesday, April 26, 2016 6:00 PM
    Moderator
  • Please have a look at below resources:

    Check this article to see is the proper configuration of URLs for Proxy and Redirection - Exchange 2007/2013 CoExistence URLs and also see this to configure Internet mail flow through an Edge Transport server.

    Create a Send connector for email sent to the Internet:
    https://technet.microsoft.com/en-us/library/jj657457%28v=exchg.150%29.aspx

    For information about how to configure mail flow in a new Exchange 2013 organization, see Configure mail flow and client access. Here's a guide to Migrate from Exchange Server 2007 to Exchange Server 2013.

    Hope this helps!
    Wednesday, April 27, 2016 5:43 AM

All replies

  • If your Edge is routing to internal Exchange 2007, then you need to change those connectors, but the best method is probably to reconfigure your Edge Subscription.

    Get-ReceiveConnector and Get-SendConnector tell you all about the routing.

    If the Edge servers don't provide you with any useful functions, then there's no reason the antispam appliance, server or cloud service can't send mail straight to an Exchange 2013 server.


    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Celebrating 20 years of providing Exchange peer support!


    Tuesday, April 26, 2016 6:00 PM
    Moderator
  • Hi Michael, 

    Welcome to our forum.

    I agree with Ed.

    We should create a receive connector on Exchange 2013 to receive inbound message for Edge server, and exclude Edge server IP address for receive connector on Exchange 2007, then reconfigure Edge subscription to check if the issue persist.

    Best Regard,

    Jim Xu

    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Jim Xu
    TechNet Community Support

    Wednesday, April 27, 2016 2:41 AM
    Moderator
  • Please have a look at below resources:

    Check this article to see is the proper configuration of URLs for Proxy and Redirection - Exchange 2007/2013 CoExistence URLs and also see this to configure Internet mail flow through an Edge Transport server.

    Create a Send connector for email sent to the Internet:
    https://technet.microsoft.com/en-us/library/jj657457%28v=exchg.150%29.aspx

    For information about how to configure mail flow in a new Exchange 2013 organization, see Configure mail flow and client access. Here's a guide to Migrate from Exchange Server 2007 to Exchange Server 2013.

    Hope this helps!
    Wednesday, April 27, 2016 5:43 AM
  • Hi Michael, 

    Is there any update for this thread?

    If the above suggestions are helpful to you, please mark it as answer so that someone who has similar issue could find this thread as soon as possible.

    Best Regard,

    Jim Xu

    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Jim Xu
    TechNet Community Support

    Tuesday, May 3, 2016 6:06 AM
    Moderator