none
Recieve Connector question (EDGE 2013) - unable to relay 550 5.7.1

    Question

  • Hi guys.
    In EX2010-EDGE we had default RECIEVE connector which worked fine after we had added AnonymousUsers.
    Now in EX2013-EDGE default RECIEVE connector is not working ok after we had added AnonymousUsers permission.

    Are there any differences in default recieve connectors on EDGE2010 and EDGE2013?
    We recieve error unable to relay 550 5.7.1).

    Do you need to create "another" recieve connector on EDGE2013, and you didn't need to do this step on EDGE2010?

    With best regards


    bostjanc


    Tuesday, December 29, 2015 8:14 AM

Answers

  • Hi guys.

    At the end we found out that FIREWALL was blockin it :(

    One more question if I may.

    How do you configure spam filter on exchange edge 2013?

    We have ran this command:

    Add-IPBlockListProvider-Name zen.spamhaus.org -LookupDomainzen.spamhaus.org -AnyMatch$true-Enabled$true

    Do you do anything else, or you leave default?


    bostjanc

    Wednesday, December 30, 2015 9:15 AM

All replies

  • Have a look at this KB.

    https://technet.microsoft.com/en-us/library/bb232082(v=exchg.150).aspx


    OM (MCITP) | Blog

    Tuesday, December 29, 2015 11:36 AM
  • Hi,

    Are you trying to relay email through your edge server to a domain that is not within your organization? You'll need an additional receive connector on your CAS server if you want to allow a particular internal IP to relay to all domains.

    Thanks.


    Please mark as an answer if this answers your question

    Mark Gossa

    MCSE 2003, MCITP Enterprise Administrator 2008 R2, MCSA 2012 R2, MCTS Exchange 2010, MCTS SQL 2012, MCTS SharePoint 2007, VCP4, VCP5, CCNA

    Blog: http://markgossa.blogspot.com   LinkedIn:

    Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

    Tuesday, December 29, 2015 1:13 PM
  • Hi,

    According to your description, I notice that configure open relay in Edge server. Do you deploy EdgeSync or not?
    If so, you need configure connector on CAS server or multi-role server, then use EdgeSync to sync configuration with Edge server. If not, we need configure connector as Om Prakash Nath mentioned above.

    Moreover, we can configure connector for internal relay or external relay. Although the default Frontend Transport receive connector allows internal SMTP relay it will not allow external SMTP relay, we need to configure a new receive connector for external relay.

    More details about it, for your reference: http://exchangeserverpro.com/exchange-2013-configure-smtp-relay-connector/
    Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.

    If this issue persists, please use Telnet to test SMTP communication: https://technet.microsoft.com/en-us/library/aa995718(v=exchg.65).aspx


    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.

    Allen Wang
    TechNet Community Support

    Wednesday, December 30, 2015 7:37 AM
    Moderator
  • Hi,

    As per the NDR "unable to relay 550 5.7.1" there are multiple reason.

    Please find the NDR's listed below:

    http://www.techrid.com/exchange-server-2010/mailflow/exchange-server-mail-flow-troubleshooting-with-list-of-exchange-2010-ndr-codes-2/

    Regards,

    Praveen

    ----------------------------------------------------------------------

    Remember to 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 Check out my latest blog posts on Exchange 2016 @ Techrid.com

    Wednesday, December 30, 2015 9:12 AM
  • Hi guys.

    At the end we found out that FIREWALL was blockin it :(

    One more question if I may.

    How do you configure spam filter on exchange edge 2013?

    We have ran this command:

    Add-IPBlockListProvider-Name zen.spamhaus.org -LookupDomainzen.spamhaus.org -AnyMatch$true-Enabled$true

    Do you do anything else, or you leave default?


    bostjanc

    Wednesday, December 30, 2015 9:15 AM
  • Glad to know that you finally figured it out. Well, review these articles on configuring SPAM filtering on EDGE 2013.

    http://www.msexchange.org/articles-tutorials/exchange-server-2013/security-message-hygiene/anti-spam-and-anti-malware-protection-exchange-2013-part1.html


    OM (MCITP) | Blog

    Wednesday, December 30, 2015 12:44 PM