Share via

Some Senders from domain nevadajustice.org gets a 550 4.4.7 error bounce back when sending to b***d@mo***lv.com

Anonymous
2025-04-02T18:08:41+00:00

Other senders have been able to send messages from sender domain to recipient domain.

Original Message Details
Created Date: 3/10/2025 10:57:38 PM <br> --- --- <br> Sender Address: r****n@ne****ce.org <br> Recipient Address: B***d@m****lv.com <br> Subject: Re: Test
Error Details
Error: 550 4.4.7 QUEUE.Expired; message expired <br> --- --- <br> Retry count: 9 <br> Message rejected by: SN7PR12MB6839.namprd12.prod.outlook.com
Notification Details
Sent by: SN7PR12MB6839.namprd12.prod.outlook.com <br> --- ---

Message Hops
HOP TIME (UTC) FROM TO WITH RELAY TIME
1 3/10/2025 <br>10:57:38 PM PH7PR12MB5757.namprd12.prod.outlook.com PH7PR12MB5757.namprd12.prod.outlook.com mapi *
2 3/10/2025 <br>10:57:38 PM PH7PR12MB5757.namprd12.prod.outlook.com LV2PR12MB5775.namprd12.prod.outlook.com Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
3 3/11/2025 <br>10:00:00 AM LV2PR12MB5775.namprd12.prod.outlook.com MW3PR12MB4460.namprd12.prod.outlook.com Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 11 hr, 2 min, 22 sec
4 3/11/2025 <br>9:07:11 PM MW3PR12MB4460.namprd12.prod.outlook.com SN7PR12MB6839.namprd12.prod.outlook.com Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 11 hr, 7 min, 11 sec

Original Message Headers

Received: from MW3PR12MB4460.namprd12.prod.outlook.com (2603:10b6:303:2f::7)

 by SN7PR12MB6839.namprd12.prod.outlook.com (2603:10b6:806:265::21) with

 Microsoft SMTP Server (version=TLS1_2,

 cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.8511.27; Tue, 11 Mar

 2025 21:07:11 +0000

Received: from LV2PR12MB5775.namprd12.prod.outlook.com (2603:10b6:408:179::12)

 by MW3PR12MB4460.namprd12.prod.outlook.com (2603:10b6:303:2f::7) with

 Microsoft SMTP Server (version=TLS1_2,

 cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.8511.27; Tue, 11 Mar

 2025 10:00:00 +0000

Authentication-Results: dkim=none (message not signed)

 header.d=none;dmarc=none action=none header.from=nevadajustice.org;

Received: from PH7PR12MB5757.namprd12.prod.outlook.com (2603:10b6:510:1d0::13)

 by LV2PR12MB5775.namprd12.prod.outlook.com (2603:10b6:408:179::12) with

 Microsoft SMTP Server (version=TLS1_2,

 cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.8511.27; Mon, 10 Mar

 2025 22:57:38 +0000

Received: from PH7PR12MB5757.namprd12.prod.outlook.com

 ([fe80::345f:c813:86c5:26b0]) by PH7PR12MB5757.namprd12.prod.outlook.com

 ([fe80::345f:c813:86c5:26b0%4]) with mapi id 15.20.8511.026; Mon, 10 Mar 2025

 22:57:38 +0000

Content-Type: application/ms-tnef; name="winmail.dat"

Content-Transfer-Encoding: binary

From: Rebecca Johnston 

To: Boyd Moss 

Subject: Re: Test

Thread-Topic: Test

Thread-Index: AQHbkg9AGzgoeN3u70yBAM/vjofDR7Ns+vCK

Date: Mon, 10 Mar 2025 22:57:38 +0000

Message-ID: 

References: 

In-Reply-To: 

Accept-Language: en-US

Content-Language: en-US

X-MS-Has-Attach: yes

X-MS-TNEF-Correlator: 

msip_labels:

MIME-Version: 1.0

X-MS-PublicTrafficType: Email

X-MS-TrafficTypeDiagnostic: PH7PR12MB5757:EE_|LV2PR12MB5775:EE_|MW3PR12MB4460:EE_|SN7PR12MB6839:EE_

Return-Path: r***on@ne****ce.org

X-MS-Office365-Filtering-Correlation-Id: e01ce4d7-4037-4078-17c2-08dd6026f45b
Outlook | Windows | New Outlook for Windows | For home

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2025-04-02T22:40:06+00:00

    Hello De Paul,

    Thank you for your response. I work with a MSP and Mossberg is one of our clients that we administer their IT services

    To answer some of the questions

    1st section on the sending domain: We don't have access to their domain records so they are basically a 3rd party in this issue.

    Receiving domain is the one that we have access to all pieces

    1. They use Microsoft 365/Exchange Online for email services entirely cloud based no hybrid.
    2. Proofpoint is the Email filtering service, other users at mossberglv domain have received emails from the sender's domain. The emails to this user Boyd never even reach proofpoint.
    3. this mailbox in question is at about 55% storage.

    It seems to be an internal relay issue with Microsoft server's since hop 3 and 4 are like 11 hours each

    Was this answer helpful?

    0 comments
  2. Anonymous
    2025-04-02T21:57:24+00:00

    Dear Brian Tousley,

    Good day! Thank you for posting in the Microsoft Community. We are happy to help you.

    I understand that some senders from the nev***ce.org domain are receiving a 550 4.4.7 error when emailing b***d@mo***lv.com, while other senders from the same domain are successful. This is definitely a frustrating issue when some emails are getting through and others aren't. Let's try to figure out what might be causing this.

    Based on the error message "550 4.4.7 QUEUE.Expired; message expired" and the information you've provided, it looks like the receiving server (SN7PR12MB6839.namprd12.prod.outlook.com) held onto the message for a period of time and then rejected it because it couldn't be delivered within that timeframe. The retry count of 9 also indicates that the sending server attempted to deliver the message multiple times before it expired.

    To help me understand the situation better and guide you towards a solution, could you please help me gather a bit more information, keeping in mind the troubleshooting steps outlined in Fix NDR error 550 4.4.7 in Exchange Online - Exchange | Microsoft Learn?

    Regarding the Sending Domain (ne***ce.org):

    • Have you recently made any changes to the DNS records for nevadajustice.org, specifically the MX records, SPF record, DKIM, or DMARC records? These records help receiving mail servers verify the legitimacy of your domain.
    • Could you confirm if the senders who are experiencing the bounce-back are using the same email infrastructure or sending platform as the senders who are successfully delivering emails? For example, are they all using the same email server or service?
    • Are there any specific characteristics of the emails that are bouncing back compared to those that are being delivered successfully? For example, are the failing emails larger in size, do they have attachments, or are they being sent in bulk?
    • Have the senders who are experiencing issues tried sending emails to other external recipients to see if they encounter the same problem, or is it isolated to b***d@mo***lv.com?

    Regarding the Recipient Domain (mo***lv.com):

    • Are you aware if the recipient (b***d@mo***lv.com) has reported any issues receiving emails from other senders at nevadajustice.org or from other domains in general?
    • Could you check if the recipient's mailbox (b***d@mo***lv.com) is close to its storage quota limit? A full mailbox can sometimes cause delivery issues.
    • Is there any possibility that emails from ne***ce.org are being caught by a spam filter or other security measures on the receiving end (mo***lv.com) for the affected senders?

    Regarding the Error Details:

    • The error message indicates the message expired in the queue of SN7PR12MB6839.namprd12.prod.outlook.com. Do you know if mo***lv.com uses Microsoft 365 or Exchange Online as their email provider, given the server name?

    By answering these questions, we can start to narrow down the potential causes, such as issues with sender reputation, recipient server problems, or email content triggering filters. The Microsoft article you provided offers several areas to investigate, and your answers will help us focus on the most relevant ones.

    Please understand that our initial response does not always resolve the issue immediately. However, with your help and more detailed information, we can work together to find a solution.

    Thank you for your precious time and your kind understanding.

    Was this answer helpful?

    0 comments