locked
Remote Server returned '550 5.7.122 RESOLVER.RST.NotAuthorizedRejectMessagesFromDLMembers; sender is member of rejected group(s)' RRS feed

  • Question

  • All messages sent from a client's domain get this bounce-back when emailing a specific inbox (individual's inbox, not a DL) without our org:

    Remote Server returned '550 5.7.122 RESOLVER.RST.NotAuthorizedRejectMessagesFromDLMembers; sender is member of rejected group(s)'

    I have checked the Get-MailboxJunkEmailConfiguration of the inbox, and removed all "BlockedSendersAndDomains."

    I have ensured no "Message Delivery Restrictions" on the inbox (Accept Messages from = All Senders).

    Have tried moving inbox (New-MoveRequest) per MS Recommendation, no joy. 

    I have even added an explicit entry in "Domain Allow List" for said domain. Still no joy.

    If sending sends to an alias of the inbox, it is delivered no problem. If sender sends to a distribution list that the inbox is a member of, the message is delivered no problem. I do not see the failed messages in a Message Trace.

    I've had a ticket open with MS for about three weeks. They've been little to no help and have lately not been responsive for about a week despite my checking in with them everyday. Both parties are becoming inpatient, as this has been going on for almost a month now. What am I missing?

    Thursday, April 25, 2019 7:59 PM

Answers

  • Delivery has failed to these recipients or groups:
    <REMOVED>
    Your message couldn't be delivered because you're a member of a group that doesn't have permission to send to the recipient.
    Ask the recipient (by phone or instant messaging, for example) to add you or the rejected group to their allow list. Or you can try the following: Remove yourself from the group, wait ten minutes, and then resend your message.
    For more information (including how to find the owner of a group), see DSN 5.7.122 Errors in Exchange Online and Office 365.


    Diagnostic information for administrators:
    Generating server: SN1PR18MB2160.namprd18.prod.outlook.com
    <REMOVED>
    Remote Server returned '550 5.7.122 RESOLVER.RST.NotAuthorizedRejectMessagesFromDLMembers; sender is member of rejected group(s)'
    Original message headers:
    Authentication-Results: spf=none (sender IP is )
     smtp.mailfrom=<REMOVED>; 
    Received: from SN1PR18MB2222.namprd18.prod.outlook.com (52.132.198.33) by
     SN1PR18MB2160.namprd18.prod.outlook.com (52.132.197.28) with Microsoft SMTP
     Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
     15.20.1792.19; Mon, 15 Apr 2019 14:45:47 +0000
    Received: from SN1PR18MB2222.namprd18.prod.outlook.com
     ([fe80::fcc6:2284:dd6c:e342]) by SN1PR18MB2222.namprd18.prod.outlook.com
     ([fe80::fcc6:2284:dd6c:e342%4]) with mapi id 15.20.1792.018; Mon, 15 Apr 2019
     14:45:47 +0000
    Content-Type: application/ms-tnef; name="winmail.dat"
    Content-Transfer-Encoding: binary
    From: <REMOVED>
    To: <REMOVED>
    CC: <REMOVED>
    Subject: <REMOVED>
    Thread-Topic: <REMOVED>
    Thread-Index: AQHU8gmjKyrmmams5E2zY4eBMEDXZ6Y9RoBqgAAHMCA=
    Date: Mon, 15 Apr 2019 14:45:47 +0000
    Message-ID: <SN1PR18MB22225F2F4B061C64C98EB6C3832B0@SN1PR18MB2222.namprd18.prod.outlook.com>
    References: <33.37.14046.A89F1BC5@a.mta1vsmtp.cc.prd.sparkpost>
     <BN8PR15MB2865DCDC5D12A45FF0528399E22B0@BN8PR15MB2865.namprd15.prod.outlook.com>
    In-Reply-To: <BN8PR15MB2865DCDC5D12A45FF0528399E22B0@BN8PR15MB2865.namprd15.prod.outlook.com>
    Accept-Language: en-US
    Content-Language: en-US
    X-MS-Has-Attach: yes
    X-MS-TNEF-Correlator: <SN1PR18MB22225F2F4B061C64C98EB6C3832B0@SN1PR18MB2222.namprd18.prod.outlook.com>
    MIME-Version: 1.0
    X-Originating-IP: <REMOVED>
    X-MS-PublicTrafficType: Email
    Return-Path: <REMOVED>
    X-MS-Office365-Filtering-Correlation-Id: 949a1ca7-84e9-4cac-8686-08d6c1b10c43
    X-Microsoft-Antispam:
    BCL:0;PCL:0;RULEID:(2390118)(7020095)(4652040)(8989299)(5600140)(711020)(4605104)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(49563074)(7193020);SRVR:SN1PR18MB2160;
    X-MS-TrafficTypeDiagnostic: SN1PR18MB2160:
    X-MS-Exchange-PUrlCount: 2
    X-LD-Processed: 64e6d96e-50d7-4a22-ba04-f47cd801b006,ExtAddr
    X-Microsoft-Antispam-PRVS:
    <SN1PR18MB216012ABCC45B768F6C6F2C3832B0@SN1PR18MB2160.namprd18.prod.outlook.com>
    X-Forefront-PRVS: 000800954F
    X-Forefront-Antispam-Report:
    SFV:NSPM;SFS:(10019020)(136003)(346002)(366004)(396003)(39850400004)(376002)(199004)(189003)(14444005)(11346002)(25786009)(486006)(256004)(476003)(86362001)(7736002)(5024004)(316002)(110136005)(446003)(26005)(186003)(2420400007)(236005)(8936002)(6246003)(3846002)(33656002)(2906002)(478600001)(54906003)(4326008)(7696005)(55016002)(53936002)(9686003)(81156014)(81166006)(790700001)(6116002)(68736007)(5660300002)(54896002)(229853002)(8676002)(74316002)(54556002)(6306002)(52536014)(76176011)(80792005)(97736004)(72206003)(99936001)(7110500001)(733005)(6436002)(102836004)(99286004)(6506007)(106356001)(14454004)(53546011)(105586002)(66066001)(71190400001)(15650500001)(71200400001)(76454003);DIR:OUT;SFP:1102;SCL:1;SRVR:SN1PR18MB2160;H:SN1PR18MB2222.namprd18.prod.outlook.com;FPR:;SPF:None;LANG:en;PTR:InfoNoRecords;A:1;MX:1;
    Received-SPF: None (protection.outlook.com: <REMOVED>.com does not designate
     permitted sender hosts)
    X-MS-Exchange-SenderADCheck: 1
    X-Microsoft-Antispam-Message-Info:
    d9+sriUWjFu7Kv9KnbAKIv78LWEmgUcKBPZTWGmEDvxfirwiTqYud4NXhRMQQ9kLYQU9WWYYgXJhG92SbQHzTxskxXWYAhSG2kI+btaIqTbadi9DKxkX4IppxzOyioL03uR8CuF5mTma7jMtSPnuFM6rcf18hGThDjJ6067NVEdNeQ5h7/GzqbWZAzM+hW3qNt1rHxESDiwnZxjiuL57q1TPC9/4kVZNyOYxegLhJIexYECvcFK0SvUxkDiOFeex2WsXz/qcrnQXdh0B3YfY9B2Yc1cBGXnLLLRpFuNAcRmDm2LD1W9CgiLPGfuadAanCA/A0rOZ/b5SbpDzSd9d2oEWX2h+XzXzrbLcsTg/1QLqqZ7RaOhU3dpqogIERmkUbw7Dq2Py/c9shJ9lbeiaepcjd8hw+f+qDttJEtIlC/Q=
    Is the sender on Office 365 as well?  If I had to guess, this is an issue on the sending side if so. Perhaps a misconfigured connector that is attributing the message incorrectly. I say this assuming you havent removed any of the header info and message hops from this
    • Marked as answer by MFiebs Thursday, April 25, 2019 9:27 PM
    Thursday, April 25, 2019 9:16 PM

All replies

  • All messages sent from a client's domain get this bounce-back when emailing a specific inbox (individual's inbox, not a DL) without our org:

    Remote Server returned '550 5.7.122 RESOLVER.RST.NotAuthorizedRejectMessagesFromDLMembers; sender is member of rejected group(s)'

    I have checked the Get-MailboxJunkEmailConfiguration of the inbox, and removed all "BlockedSendersAndDomains."

    I have ensured no "Message Delivery Restrictions" on the inbox (Accept Messages from = All Senders).

    Have tried moving inbox (New-MoveRequest) per MS Recommendation, no joy. 

    I have even added an explicit entry in "Domain Allow List" for said domain. Still no joy.

    If sending sends to an alias of the inbox, it is delivered no problem. If sender sends to a distribution list that the inbox is a member of, the message is delivered no problem. I do not see the failed messages in a Message Trace.

    I've had a ticket open with MS for about three weeks. They've been little to no help and have lately not been responsive for about a week despite my checking in with them everyday. Both parties are becoming inpatient, as this has been going on for almost a month now. What am I missing?

    Please post the entire NDR including the generating server and detailed info scrubbed of the domain and other identifying info
    Thursday, April 25, 2019 8:30 PM
  • Delivery has failed to these recipients or groups:
    <REMOVED>
    Your message couldn't be delivered because you're a member of a group that doesn't have permission to send to the recipient.
    Ask the recipient (by phone or instant messaging, for example) to add you or the rejected group to their allow list. Or you can try the following: Remove yourself from the group, wait ten minutes, and then resend your message.
    For more information (including how to find the owner of a group), see DSN 5.7.122 Errors in Exchange Online and Office 365.


    Diagnostic information for administrators:
    Generating server: SN1PR18MB2160.namprd18.prod.outlook.com
    <REMOVED>
    Remote Server returned '550 5.7.122 RESOLVER.RST.NotAuthorizedRejectMessagesFromDLMembers; sender is member of rejected group(s)'
    Original message headers:
    Authentication-Results: spf=none (sender IP is )
     smtp.mailfrom=<REMOVED>; 
    Received: from SN1PR18MB2222.namprd18.prod.outlook.com (52.132.198.33) by
     SN1PR18MB2160.namprd18.prod.outlook.com (52.132.197.28) with Microsoft SMTP
     Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
     15.20.1792.19; Mon, 15 Apr 2019 14:45:47 +0000
    Received: from SN1PR18MB2222.namprd18.prod.outlook.com
     ([fe80::fcc6:2284:dd6c:e342]) by SN1PR18MB2222.namprd18.prod.outlook.com
     ([fe80::fcc6:2284:dd6c:e342%4]) with mapi id 15.20.1792.018; Mon, 15 Apr 2019
     14:45:47 +0000
    Content-Type: application/ms-tnef; name="winmail.dat"
    Content-Transfer-Encoding: binary
    From: <REMOVED>
    To: <REMOVED>
    CC: <REMOVED>
    Subject: <REMOVED>
    Thread-Topic: <REMOVED>
    Thread-Index: AQHU8gmjKyrmmams5E2zY4eBMEDXZ6Y9RoBqgAAHMCA=
    Date: Mon, 15 Apr 2019 14:45:47 +0000
    Message-ID: <SN1PR18MB22225F2F4B061C64C98EB6C3832B0@SN1PR18MB2222.namprd18.prod.outlook.com>
    References: <33.37.14046.A89F1BC5@a.mta1vsmtp.cc.prd.sparkpost>
     <BN8PR15MB2865DCDC5D12A45FF0528399E22B0@BN8PR15MB2865.namprd15.prod.outlook.com>
    In-Reply-To: <BN8PR15MB2865DCDC5D12A45FF0528399E22B0@BN8PR15MB2865.namprd15.prod.outlook.com>
    Accept-Language: en-US
    Content-Language: en-US
    X-MS-Has-Attach: yes
    X-MS-TNEF-Correlator: <SN1PR18MB22225F2F4B061C64C98EB6C3832B0@SN1PR18MB2222.namprd18.prod.outlook.com>
    MIME-Version: 1.0
    X-Originating-IP: <REMOVED>
    X-MS-PublicTrafficType: Email
    Return-Path: <REMOVED>
    X-MS-Office365-Filtering-Correlation-Id: 949a1ca7-84e9-4cac-8686-08d6c1b10c43
    X-Microsoft-Antispam:
    BCL:0;PCL:0;RULEID:(2390118)(7020095)(4652040)(8989299)(5600140)(711020)(4605104)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(49563074)(7193020);SRVR:SN1PR18MB2160;
    X-MS-TrafficTypeDiagnostic: SN1PR18MB2160:
    X-MS-Exchange-PUrlCount: 2
    X-LD-Processed: 64e6d96e-50d7-4a22-ba04-f47cd801b006,ExtAddr
    X-Microsoft-Antispam-PRVS:
    <SN1PR18MB216012ABCC45B768F6C6F2C3832B0@SN1PR18MB2160.namprd18.prod.outlook.com>
    X-Forefront-PRVS: 000800954F
    X-Forefront-Antispam-Report:
    SFV:NSPM;SFS:(10019020)(136003)(346002)(366004)(396003)(39850400004)(376002)(199004)(189003)(14444005)(11346002)(25786009)(486006)(256004)(476003)(86362001)(7736002)(5024004)(316002)(110136005)(446003)(26005)(186003)(2420400007)(236005)(8936002)(6246003)(3846002)(33656002)(2906002)(478600001)(54906003)(4326008)(7696005)(55016002)(53936002)(9686003)(81156014)(81166006)(790700001)(6116002)(68736007)(5660300002)(54896002)(229853002)(8676002)(74316002)(54556002)(6306002)(52536014)(76176011)(80792005)(97736004)(72206003)(99936001)(7110500001)(733005)(6436002)(102836004)(99286004)(6506007)(106356001)(14454004)(53546011)(105586002)(66066001)(71190400001)(15650500001)(71200400001)(76454003);DIR:OUT;SFP:1102;SCL:1;SRVR:SN1PR18MB2160;H:SN1PR18MB2222.namprd18.prod.outlook.com;FPR:;SPF:None;LANG:en;PTR:InfoNoRecords;A:1;MX:1;
    Received-SPF: None (protection.outlook.com: <REMOVED>.com does not designate
     permitted sender hosts)
    X-MS-Exchange-SenderADCheck: 1
    X-Microsoft-Antispam-Message-Info:
    d9+sriUWjFu7Kv9KnbAKIv78LWEmgUcKBPZTWGmEDvxfirwiTqYud4NXhRMQQ9kLYQU9WWYYgXJhG92SbQHzTxskxXWYAhSG2kI+btaIqTbadi9DKxkX4IppxzOyioL03uR8CuF5mTma7jMtSPnuFM6rcf18hGThDjJ6067NVEdNeQ5h7/GzqbWZAzM+hW3qNt1rHxESDiwnZxjiuL57q1TPC9/4kVZNyOYxegLhJIexYECvcFK0SvUxkDiOFeex2WsXz/qcrnQXdh0B3YfY9B2Yc1cBGXnLLLRpFuNAcRmDm2LD1W9CgiLPGfuadAanCA/A0rOZ/b5SbpDzSd9d2oEWX2h+XzXzrbLcsTg/1QLqqZ7RaOhU3dpqogIERmkUbw7Dq2Py/c9shJ9lbeiaepcjd8hw+f+qDttJEtIlC/Q=
    Thursday, April 25, 2019 8:44 PM
  • Delivery has failed to these recipients or groups:
    <REMOVED>
    Your message couldn't be delivered because you're a member of a group that doesn't have permission to send to the recipient.
    Ask the recipient (by phone or instant messaging, for example) to add you or the rejected group to their allow list. Or you can try the following: Remove yourself from the group, wait ten minutes, and then resend your message.
    For more information (including how to find the owner of a group), see DSN 5.7.122 Errors in Exchange Online and Office 365.


    Diagnostic information for administrators:
    Generating server: SN1PR18MB2160.namprd18.prod.outlook.com
    <REMOVED>
    Remote Server returned '550 5.7.122 RESOLVER.RST.NotAuthorizedRejectMessagesFromDLMembers; sender is member of rejected group(s)'
    Original message headers:
    Authentication-Results: spf=none (sender IP is )
     smtp.mailfrom=<REMOVED>; 
    Received: from SN1PR18MB2222.namprd18.prod.outlook.com (52.132.198.33) by
     SN1PR18MB2160.namprd18.prod.outlook.com (52.132.197.28) with Microsoft SMTP
     Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
     15.20.1792.19; Mon, 15 Apr 2019 14:45:47 +0000
    Received: from SN1PR18MB2222.namprd18.prod.outlook.com
     ([fe80::fcc6:2284:dd6c:e342]) by SN1PR18MB2222.namprd18.prod.outlook.com
     ([fe80::fcc6:2284:dd6c:e342%4]) with mapi id 15.20.1792.018; Mon, 15 Apr 2019
     14:45:47 +0000
    Content-Type: application/ms-tnef; name="winmail.dat"
    Content-Transfer-Encoding: binary
    From: <REMOVED>
    To: <REMOVED>
    CC: <REMOVED>
    Subject: <REMOVED>
    Thread-Topic: <REMOVED>
    Thread-Index: AQHU8gmjKyrmmams5E2zY4eBMEDXZ6Y9RoBqgAAHMCA=
    Date: Mon, 15 Apr 2019 14:45:47 +0000
    Message-ID: <SN1PR18MB22225F2F4B061C64C98EB6C3832B0@SN1PR18MB2222.namprd18.prod.outlook.com>
    References: <33.37.14046.A89F1BC5@a.mta1vsmtp.cc.prd.sparkpost>
     <BN8PR15MB2865DCDC5D12A45FF0528399E22B0@BN8PR15MB2865.namprd15.prod.outlook.com>
    In-Reply-To: <BN8PR15MB2865DCDC5D12A45FF0528399E22B0@BN8PR15MB2865.namprd15.prod.outlook.com>
    Accept-Language: en-US
    Content-Language: en-US
    X-MS-Has-Attach: yes
    X-MS-TNEF-Correlator: <SN1PR18MB22225F2F4B061C64C98EB6C3832B0@SN1PR18MB2222.namprd18.prod.outlook.com>
    MIME-Version: 1.0
    X-Originating-IP: <REMOVED>
    X-MS-PublicTrafficType: Email
    Return-Path: <REMOVED>
    X-MS-Office365-Filtering-Correlation-Id: 949a1ca7-84e9-4cac-8686-08d6c1b10c43
    X-Microsoft-Antispam:
    BCL:0;PCL:0;RULEID:(2390118)(7020095)(4652040)(8989299)(5600140)(711020)(4605104)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(49563074)(7193020);SRVR:SN1PR18MB2160;
    X-MS-TrafficTypeDiagnostic: SN1PR18MB2160:
    X-MS-Exchange-PUrlCount: 2
    X-LD-Processed: 64e6d96e-50d7-4a22-ba04-f47cd801b006,ExtAddr
    X-Microsoft-Antispam-PRVS:
    <SN1PR18MB216012ABCC45B768F6C6F2C3832B0@SN1PR18MB2160.namprd18.prod.outlook.com>
    X-Forefront-PRVS: 000800954F
    X-Forefront-Antispam-Report:
    SFV:NSPM;SFS:(10019020)(136003)(346002)(366004)(396003)(39850400004)(376002)(199004)(189003)(14444005)(11346002)(25786009)(486006)(256004)(476003)(86362001)(7736002)(5024004)(316002)(110136005)(446003)(26005)(186003)(2420400007)(236005)(8936002)(6246003)(3846002)(33656002)(2906002)(478600001)(54906003)(4326008)(7696005)(55016002)(53936002)(9686003)(81156014)(81166006)(790700001)(6116002)(68736007)(5660300002)(54896002)(229853002)(8676002)(74316002)(54556002)(6306002)(52536014)(76176011)(80792005)(97736004)(72206003)(99936001)(7110500001)(733005)(6436002)(102836004)(99286004)(6506007)(106356001)(14454004)(53546011)(105586002)(66066001)(71190400001)(15650500001)(71200400001)(76454003);DIR:OUT;SFP:1102;SCL:1;SRVR:SN1PR18MB2160;H:SN1PR18MB2222.namprd18.prod.outlook.com;FPR:;SPF:None;LANG:en;PTR:InfoNoRecords;A:1;MX:1;
    Received-SPF: None (protection.outlook.com: <REMOVED>.com does not designate
     permitted sender hosts)
    X-MS-Exchange-SenderADCheck: 1
    X-Microsoft-Antispam-Message-Info:
    d9+sriUWjFu7Kv9KnbAKIv78LWEmgUcKBPZTWGmEDvxfirwiTqYud4NXhRMQQ9kLYQU9WWYYgXJhG92SbQHzTxskxXWYAhSG2kI+btaIqTbadi9DKxkX4IppxzOyioL03uR8CuF5mTma7jMtSPnuFM6rcf18hGThDjJ6067NVEdNeQ5h7/GzqbWZAzM+hW3qNt1rHxESDiwnZxjiuL57q1TPC9/4kVZNyOYxegLhJIexYECvcFK0SvUxkDiOFeex2WsXz/qcrnQXdh0B3YfY9B2Yc1cBGXnLLLRpFuNAcRmDm2LD1W9CgiLPGfuadAanCA/A0rOZ/b5SbpDzSd9d2oEWX2h+XzXzrbLcsTg/1QLqqZ7RaOhU3dpqogIERmkUbw7Dq2Py/c9shJ9lbeiaepcjd8hw+f+qDttJEtIlC/Q=
    Is the sender on Office 365 as well?  If I had to guess, this is an issue on the sending side if so. Perhaps a misconfigured connector that is attributing the message incorrectly. I say this assuming you havent removed any of the header info and message hops from this
    • Marked as answer by MFiebs Thursday, April 25, 2019 9:27 PM
    Thursday, April 25, 2019 9:16 PM
  • "I say this assuming you havent removed any of the header info and message hops from this" - Correct, no message hops removed. 

    "Is the sender on Office 365 as well?" - Yes, they are. 

    "Perhaps a misconfigured connector that is attributing the message incorrectly." - Thank you for the suggestion. I will in turn suggest this to my IT Contact from the Sender side (who has assured me they do not block outgoing). 

    Thank you for responding, I agree with you in that there is a lack of objective data pointing to a cause. In which case, maybe we do not have all of the data (sender logs are out of my reach, but may contain the information needed). 
    If you think of anything else, I'd be happy to hear it. Until then, marking your answer. Thanks again!

    Thursday, April 25, 2019 9:27 PM
  • "I say this assuming you havent removed any of the header info and message hops from this" - Correct, no message hops removed. 

    "Is the sender on Office 365 as well?" - Yes, they are. 

    "Perhaps a misconfigured connector that is attributing the message incorrectly." - Thank you for the suggestion. I will in turn suggest this to my IT Contact from the Sender side (who has assured me they do not block outgoing). 

    Thank you for responding, I agree with you in that there is a lack of objective data pointing to a cause. In which case, maybe we do not have all of the data (sender logs are out of my reach, but may contain the information needed). 
    If you think of anything else, I'd be happy to hear it. Until then, marking your answer. Thanks again!

    well, a couple of things:

    1. Its not in your message tracking. That means it was never accepted by your org unless message trace is broken.

    2. It appears that their SPF record is broken or non-existent, but that could be because its getting misrouted.

    3. References: <33.37.14046.A89F1BC5@a.mta1vsmtp.cc.prd.sparkpost> If its going from Office 365 to another Office 365 tenant, then how is this getting added...

    Thursday, April 25, 2019 10:04 PM
  • Presented objective hop data to sender IT Department - they looked into it and found (within minutes) the issue was that our recipient was at one time added as a user on their end with our domain email address. Said account was disabled. 

    So this was indeed a routing issue. Nothing on our end. I spent a lot (too much) time on this, but learned some lessons. Not the least of which is that a little nudge in the right direction from folks here can be very helpful. Thank you Andy! 

    Friday, April 26, 2019 2:17 PM