Sign up for Office 365
Learn more about Office 365
I am a Microsoft Partner and administrator for an O365 account for a customer. Emails sent to this customer's domain are bouncing with an NDR - 550 - mailbox unavailable. Same results from several different servers. DNS hosted by O365. No changes have been made. Suspect this is a forefront issue. This issue has resulted in customer having no email service currently as they cannot recieve emails.
We have checked the portal. Everything seems to be in order.
Need resolution quickly.
Thanks for the feedback.
I've got the same problem with my domain.
Started yesterday. I still get a lot of emails but have had a number of people report to me that they are getting this bounce back message
Thank you for your post.
Does this problem happen to all users in your domain, or just one user? Can the user who encountered this problem send emails out properly?
I have checked the healthy status of Exchange Online and noticed that the service is always running. And I can send/receive emails properly with my test Office 365 mailbox. In our case here, to narrow down the issue, would you please send a test emails to/from your Office 365 account to reproduce the issue? And then, post back the full content of NDR message to allow us to understand the problem in more details.
Thank you for your cooperation.
Sorry to hi-jack but I think my issue is the same.
We are having multiple failures for different users.
Delivery has failed to these recipients or groups:
A problem occurred during the delivery of this message to this e-mail address. Try sending this message again. If the problem continues, please contact your helpdesk.
The following organisation rejected your message: BAY0-PAMC2-F9.Bay0.hotmail.com.
Diagnostic information for administrators:
Generating server: bigfish.com
BAY0-PAMC2-F9.Bay0.hotmail.com #<BAY0-PAMC2-F9.Bay0.hotmail.com #5.0.0 smtp;550 Requested action not taken: mailbox unavailable> #SMTP#
Original message headers:
Received: from mail94-am1-R.bigfish.com (10.3.201.244) by
AM1EHSOBE005.bigfish.com (10.3.204.25) with Microsoft SMTP Server id
220.127.116.11; Mon, 30 Apr 2012 10:47:28 +0000
Received: from mail94-am1 (localhost [127.0.0.1]) by mail94-am1-R.bigfish.com
(Postfix) with ESMTP id D221C460478 for
<email@example.com.FOPE.CONNECTOR.OVERRIDE>; Mon, 30 Apr 2012 10:47:27
Received-SPF: pass (mail94-am1: domain of associatesoftware.com designates 18.104.22.168 as permitted sender) client-ip=22.214.171.124; firstname.lastname@example.org; helo=DB3PRD0610HT001.eurprd06.prod.outlook.com ;.outlook.com ;
Received: from mail94-am1 (localhost.localdomain [127.0.0.1]) by mail94-am1
(MessageSwitch) id 1335782846174211_13993; Mon, 30 Apr 2012 10:47:26 +0000
Received: from AM1EHSMHS013.bigfish.com (unknown [10.3.201.235]) by
mail94-am1.bigfish.com (Postfix) with ESMTP id 25CCA340045 for
<email@example.com>; Mon, 30 Apr 2012 10:47:26 +0000 (UTC)
Received: from DB3PRD0610HT001.eurprd06.prod.outlook.com (126.96.36.199) by
AM1EHSMHS013.bigfish.com (10.3.207.151) with Microsoft SMTP Server (TLS) id
188.8.131.52; Mon, 30 Apr 2012 10:47:22 +0000
Received: from DB3PRD0610MB369.eurprd06.prod.outlook.com ([169.254.12.32]) by
DB3PRD0610HT001.eurprd06.prod.outlook.com ([10.255.47.36]) with mapi id
14.16.0143.004; Mon, 30 Apr 2012 10:47:16 +0000
From: Darren Baines <firstname.lastname@example.org>
To: "email@example.com" <firstname.lastname@example.org>
Disposition-Notification-To: Darren Baines
Date: Mon, 30 Apr 2012 10:47:16 +0000
Accept-Language: en-GB, en-US
Same issue, started on Saturday. I haven't heard anything from Microsoft on this. Need resolution.
Are any of you still experiencing this problems? If so, does the NDR contain a line similar to this:
The following organisation rejected your message: BAY0-PAMC2-F9.Bay0.hotmail.com?
I haven't received any new indications of this since April 30th and I want to know if this is still happening before I escalate this to the engineers.
The problem seems to be resolved and only lasted th. I did not have an NDR line like the one you posted. The oddest part was that the bouncebacks were not consistent, they happened to different people at different times from different external servers.