Sync a voice

russell@rocklandbakery.com · all

Undeliverable: Scheduled ping 3:14

Sat Aug 22, 2026 · 03:14 AM EDT

From
Microsoft Outlook <MicrosoftExchange329e71ec88ae4615bbc36ab6ce41109e@RBakery.onmicrosoft.com>
To
russ@signalint.net <russ@signalint.net>

Your message to russ@signalint.net couldn't be delivered.

Russell is not authorized to relay messages through the server that reported this error.

Russell
Office 365
russ

Sender

Action Required

Sender not authorized for relay

How to Fix It

When Office 365 tried to send your message to the next server outside Office 365, that server reported an error that it couldn't relay your message. It's likely that the email server isn't correctly set up to receive and relay messages from your organization.

To fix this issue, forward this non-delivery report (NDR) to your email admin.

Was this helpful? Send feedback to Microsoft.

More Info for Email Admins

Status code: 550 5.7.367

The sender's message was routed to an email server outside Office 365 that returned an error that it can't relay the message. It's likely that the server isn't set up correctly to receive and relay messages sent from rocklandbakery.com or from Russell.

The receiving server is not an Office 365 server - it's likely one of your on-premises servers in a hybrid environment, a server at a smart host email service that you're trying to route messages through, or possibly a server at an email hosting service you used in the past (for example, when your MX record still points to your previous email service provider). To fix this issue, try one or more of the following:

Check the error shown in the "Error Details" section below - Check the error to determine what domain, service, or server is reporting the error. The email server needs to be configured to either accept messages from anonymous users or to include the sending domain or sending IP address in its list of authenticated senders. On an on-premises Exchange server, you can set this up in the server's receive connector. If it's a smart host managed by another service or partner, contact the service or partner and ask them to configure their servers to accept and relay messages from your domain or from your senders.

Make sure your MX/DNS records are correct - Work with your DNS hosting provider (your domain registrar, Web hosting provider, or ISP) to make sure your MX records are correctly set up to direct messages to the correct location.

Unfortunately, Office 365 support can't help fix this problem because it's likely due to misconfigured settings on an email server outside Office 365.

Original Message Details

Created Date:
8/22/2026 7:14:02 AM

Sender Address:
Russell@rocklandbakery.com

Recipient Address:
russ@signalint.net

Subject:
Scheduled ping 3:14

Error Details

Error:
550 5.7.367 Remote server returned not permitted to relay -> 554 5.7.1 <russ@signalint.net>: Relay access denied

Message rejected by:
asp-relay.et.namecheap.tech

Notification Details

Sent by:
PH6P221MB996880.NAMP221.PROD.OUTLOOK.COM

Message Hops

HOP
TIME (UTC)
FROM
TO
WITH
RELAY TIME

1
8/22/2026

7:14:02 AM
LV0P221MB996834.NAMP221.PROD.OUTLOOK.COM
LV0P221MB996834.NAMP221.PROD.OUTLOOK.COM
mapi
*

2
8/22/2026

7:14:02 AM
LV0P221MB996834.NAMP221.PROD.OUTLOOK.COM
PH6P221MB996880.NAMP221.PROD.OUTLOOK.COM
Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384)
*

Original Message Headers

ARC-Seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none;
b=i+GwfOMrLpmwIbu0BHAnaBTrSlqvv0EXWezSTIAnFK7TNfHxlkSkoqrkJ8L/Chu9UyNhMcBLNYLg99dTktx+EzRf83QOkvD8OQUAeqtZ63FxgVyxXVHjvlDZyYoO6vbe2GbxC9mCpbAgK/kdkzglvaoXze+V/TYkJbGVAJVENwt6pz8wWeINft3mbgnUIPjsAl/HDEKxocMKQOYbhnyQJ2s5SdvJOa+oFyzG9LFcbVz2d22sYgh5ny4YRer6NB+EdaYZClXpUkEylvipqCC3nHypV5mJTV3YUftWiOzhH9A/x9Fc0AIgsUwr/EdHLDKsEUgN4afwCS1tejHognUzbA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;
s=arcselector10001;
h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1;
bh=41WVbnAIA8ySd5rVahc05EytYQHwTu4VM1gyH5PFp9o=;
b=D2YfqgIydTXl8aAywhuEsgw9yGA9k8yu/Hh/2nMnZNFA4rAipLL2NfeGk18ZHxUUdvYMK4w+8HQD8Idchfwjm6povYnW+/pQbaOX+Y+iBya892aOEV3xfQfC3q9Yt+X7uUiwnDd/UvhDbIh2OLGuGZveqJDjo612kylM8L+Jcl5bp1gmLGLRtLZJi+1F04IdC1OFjOCnEAjcibz0axX+zOiXgFkVtcWUjrktU9usqKtYorzP+o0378UTsbRZnrW0uMNmG+FsKEzs8pWpq9X/UmVgeqkg2KZ9mnoL8rwL0C6RmZR8RXSLpDB7GonD2mgZ+6EDzbx3gr3Tz9JrQzdG4g==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass
smtp.mailfrom=rocklandbakery.com; dmarc=pass action=none
header.from=rocklandbakery.com; dkim=pass header.d=rocklandbakery.com;
arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rocklandbakery.com;
s=selector1;
h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck;
bh=41WVbnAIA8ySd5rVahc05EytYQHwTu4VM1gyH5PFp9o=;
b=VWMgCQpNJbPHUWflXcYdRjYHQXvMeJjufUIl6berVGTIGb1rg1RIVv1Wat8i/OGCYdijMHBiMrswDwyrqhmKx6p5PDxku3CwsMZmQufWp2h9xoHUsAnFbxo+kELluC0DZRvWzun63r4uiAidOFqcRZ3dfFcK5LA63DRl+2HwQZk=
Received: from LV0P221MB996834.NAMP221.PROD.OUTLOOK.COM (2603:10b6:408:33f::7)
by PH6P221MB996880.NAMP221.PROD.OUTLOOK.COM (2603:10b6:510:3c9::5) with
Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.21.339.11; Sat, 22 Aug
2026 07:14:02 +0000
Received: from LV0P221MB996834.NAMP221.PROD.OUTLOOK.COM
([fe80::c92b:2439:7cf4:51f6]) by LV0P221MB996834.NAMP221.PROD.OUTLOOK.COM
([fe80::c92b:2439:7cf4:51f6%6]) with mapi id 15.21.0339.010; Sat, 22 Aug 2026
07:14:02 +0000

Message id ms:AAMkADc0MWQ3OWM2LTkyOTctNDczZS05OGY4LTIxYjE2ZWEwNzdjNgBGAAAAAAAPZ_rjH0NURr6N3vZG1-vYBwBMGgR5t04vQ6qaA-Ps5SQzAAAAAAEMAABMGgR5t04vQ6qaA-Ps5SQzAABG61RaAAA=