none
How to set-up Shared MailBox where all Catch-All Mail goes to another Mailbox RRS feed

  • Question

  • We are in the process of setting up and configuring a new on-premise Exchange 2016 Server. The internal server name is computername.ad.abc123.com

    We've currently added two domains as 'accepted domains'.

    The first domain abc123.com is currently in use on an old Exchange server (2003), and we aren't ready to move anything until the set-up is complete.  We have another domain 123abc.com which we have pointed the MX record to our new Exchange IP adress, and we are receiving mail fine both internally and externally.

    For the domain 123abc.com we want to set a rule so that we catch any email where the mailbox hasn't been set-up.  I navigated to mail flow -> rules.  I added a rule so that if the recipient is 'Outside the organization' I forward redirect the message to a mailbox under the domain abc123.com in this case sales@ad.abc123.com

    However it doesn't seem to work.   I looked under Exchange Toolbox and found the error was A local loop was detected.  Where am I going wrong ?

    Tuesday, October 30, 2018 5:27 PM

Answers

All replies

  • Try a different condition, such as "recipients's address domain portion belongs to any of these domains: 'abc123.com'"
    Tuesday, October 30, 2018 7:21 PM
  • I tried as you suggested, but still the same.  Here is the rule

    Another point to add, is our send connector is currently a smarthost (3rd party mail filtering company).  Do I need to add another send connector...As I can see in the smarthost logs the message trying to be sent out.

    Wednesday, October 31, 2018 9:12 AM
  • Hi,

    According to your description, you have Exchange 2003 and Exchange 2016 that is still setting up in your organization, and the two Exchange servers share the same name space “ad.abc123.com”. Domain “123abc.com” is an accepted domain and is pointed to the new server. If there is any misunderstanding, feel free let me know.


    In this situation, the emails can infinite loop if the type of accepted domain is autorotative. Please run the following command to check the domain type of “ad.abc123.com”.

    Get-AcceptedDomain “ad.abc123.com” | fl domaintype


    If it is authoritative, please change it to “internal relay”.

    Set-AcceptedDomain “ad.abc123.com” -DomainType InternalRelay


    After changing domain type, you still need to create a send connector in Exchange 2016 which enables emails to be sent to Exchange 2003.

    New-SendConnector -Name "Internal Relay" -Custom -AddressSpaces ad.abc123.com -DNSRoutingEnabled $true -SourceTransportServers computername.ad.abc123.com


    Regards,

    Dawn Zhou


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Wednesday, October 31, 2018 9:23 AM
    Moderator
  • Our old Exchange 2003 server is in separate environment and is no way connected to our new Windows Server 2016 environment.   Sorry for any confusion.  But the problem still remains as I described.
    Wednesday, October 31, 2018 9:28 AM
  • These are the message headers.  Basically for some reason, even though I have the Catch All rule, to deliver the message to a email address on our local exchange server,  it is attempting to send it out via our SmartHost.

    Received: from [EXCHANGE-SERVER-IP] (helo=ADVEXCH01.ad.abc123.com)
    by out4d.XXXXXXX.net with esmtps (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128)
    (Exim 4.90_1)
    (envelope-from <someexternalemail@hotmail.com>)
    id 1gHn23-0007ZH-TN
    for noone@123abc.com; Wed, 31 Oct 2018 02:43:23 -0700
    Received: from ADVEXCH01.ad.abc123.com (192.168.1.3) by
     ADVEXCH01.ad.abc123.com (192.168.1.3) with Microsoft SMTP Server
     (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id
     15.1.1591.10; Wed, 31 Oct 2018 09:43:22 +0000
    Received: from EUR02-HE1-obe.outbound.protection.outlook.com (40.92.68.27) by
     ADVEXCH01.ad.abc123.com (192.168.1.3) with Microsoft SMTP Server
     (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256) id
     15.1.1591.10 via Frontend Transport; Wed, 31 Oct 2018 09:43:22 +0000
    DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hotmail.com;
     s=selector1;
    Received: from HE1EUR02FT004.eop-EUR02.prod.protection.outlook.com
     (10.152.10.59) by HE1EUR02HT041.eop-EUR02.prod.protection.outlook.com
     (10.152.10.200) with Microsoft SMTP Server (version=TLS1_2,
     cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.1294.14; Wed, 31 Oct
     2018 09:43:20 +0000
    Received: from HE1P18901MB0140.EURP189.PROD.OUTLOOK.COM (10.152.10.52) by
     HE1EUR02FT004.mail.protection.outlook.com (10.152.10.83) with Microsoft SMTP
     Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id
     15.20.1294.14 via Frontend Transport; Wed, 31 Oct 2018 09:43:20 +0000
    Received: from HE1P18901MB0140.EURP189.PROD.OUTLOOK.COM
     ([fe80::ca5:2832:a7e0:fb60]) by HE1P18901MB0140.EURP189.PROD.OUTLOOK.COM
     ([fe80::ca5:2832:a7e0:fb60%7]) with mapi id 15.20.1294.021; Wed, 31 Oct 2018
     09:43:20 +0000
    From: NeilDT <someexternalemail@hotmail.com>
    To: "noone@123abc.com" <noone@123abc.com>

    Wednesday, October 31, 2018 9:51 AM
  • Do I need to provide any further information to help resolve this issue.  To confirm, that we have 1 Windows 2016 Server running Active Directory, and 1 Exchange 2016 Standard installation (on-premise).
    Wednesday, October 31, 2018 5:42 PM
  • This is not the condition I suggested to use, try with the exact "recipients's address domain portion belongs to any of these domains: 'abc123.com'".
    Wednesday, October 31, 2018 6:30 PM
  • Sorry, where do I find 'recipients's address domain portion belongs to any of these domains: '  I can only see 'The recipient address includes...'.

    I can't see anything that says 'domain portion belongs to'...


    • Edited by NeilDT Wednesday, October 31, 2018 6:41 PM
    Wednesday, October 31, 2018 6:39 PM
  • Hi,

    So they are two separate mail systems but share a domain name "ad.abc123.com", right? If so, you can try the method proposed in my initial reply.

    Regards,

    Dawn Zhou


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Thursday, November 1, 2018 10:10 AM
    Moderator
  • I can't even get the Catch All to work for the 'other' accepted domain 123abc.com.   Is there any specific documentation I can follow in setting up Catch All for a accepted domain that will forward all mail that doesn't have a valid SMTP address to a mailbox I specify ?
    Thursday, November 1, 2018 10:42 AM
  • I can't even get the Catch All to work for the 'other' accepted domain 123abc.com.   Is there any specific documentation I can follow in setting up Catch All for a accepted domain that will forward all mail that doesn't have a valid SMTP address to a mailbox I specify ?

    You could try something similar like this for on-prem:

    https://social.technet.microsoft.com/wiki/contents/articles/30462.catch-all-mailbox-office365.aspx

    • Marked as answer by NeilDT Friday, November 2, 2018 10:47 AM
    Thursday, November 1, 2018 10:43 AM
    Moderator
  • Thank you Any, that worked perfectly !
    Friday, November 2, 2018 10:47 AM