Hello,

Does every message sent to these domains (@bt.com, @rbs.com, @gmail.com, @googlemail etc) have the same problem?

Generally, the error message "550 4.4.7 QUEUE.Expired; message expired" occurs because the email message in the queue expired. In this situation, the sending server tries to relay or deliver the email message. However, the action is not completed before the message expiration time occurs. Please try the troubleshooting methods that are described in following articles to resolve this problem.

550 4.4.7 QUEUE.Expired; message expired" NDR message when you send an email message through FOPE to an external domain
http://support.microsoft.com/kb/2625264/en-us

Troubleshooting Non-Delivery Report Messages
http://technet.microsoft.com/en-us/library/bb123980(EXCHG.65).aspx

Understanding Non-Delivery Reports
http://technet.microsoft.com/en-us/library/bb232118(EXCHG.80).aspx

Thank you.

Jack Sun

Hi Jack, thankyou for your reply.

No, it is only some messages - for example one email address we have sent to 42 times in the past 5 days, but it has generated 2 NDRs this moring - this is pretty typicaly - most of the NDRs messsages have come from email addresses which are known to be good and users have been sending to happily for the past week, and/or ahve sent to againt after receiving an NDR - this inrease started around 3pm UK time yesterday, still going on today - some users are getting probably 1/3 of their outbound emails NDR'd - obviously quite an issue for us as we only transitioned the customer on to 365 a week ago....

We've been on phone direct to the MS support team and this has been the update on our ticket:

"Everytime when it worked the from ip address presented was 157.55.224.141. When it doesn’t work and gives the 550 error the ip address presented is a private one 169.254.2.235 which does not look up by DNS. And the mail expires, times out and is returned. 169.254.2.235 is a private IP address. Private IP addresses cannot be reversed publicly. It may need the ip 157.55.224.141 put in to office 365 as the outbound mail server ip address. "

we're rather stuck and looking a little silly....

thanks for your time jack

regards

Mark

I have a customer with exactly the same issue, it problem started this week. He tries to email to a lot of different email addresses on all different domains that had worked before. Some emails work fine to an email address and some to the same address fail with the same error:

I just changed the original domain name to  DOMAIN,

I see that al the errors are that failed show the private APIPA address, is this the problem????

#550 4.4.7 QUEUE.Expired; message expired ##

Original message headers:

Received: from DB3PRD0502MB114.eurprd05.prod.outlook.com ([169.254.7.201]) by

DB3PRD0502HT011.eurprd05.prod.outlook.com ([10.3.48.120]) with mapi id

14.01.0225.071; Thu, 6 Oct 2011 13:10:22 +0000

From: USERNAME <wsk@DOMAIN.nl>

To: Jet Manrho <jm@DOMAIN.nl>

Subject: RE: Antal --> knipsels

Thread-Topic: Antal --> knipsels

Thread-Index: AcyEAjJLNJnLq8HzTPOxrJL1InFv2wABSC6AAAh5dGA=

Date: Thu, 6 Oct 2011 13:10:22 +0000

Message-ID: <46E077D8EA00064493A770000B0EB2ED1DB14E@DB3PRD0502MB114.eurprd05.prod.outlook.com>

References: <03021C46D59C46F3B837B4A1DE55DBD0@Autoped.local>

<7CB986703662DA44948280EEF7ABAED6046079@AUTOPED-SRVR2.Autoped.local>

In-Reply-To: <7CB986703662DA44948280EEF7ABAED6046079@AUTOPED-SRVR2.Autoped.local>

Accept-Language: en-US

Content-Language: nl-NL

X-MS-Has-Attach:

X-MS-TNEF-Correlator:

x-originating-ip: [10.3.4.10]

Content-Type: multipart/alternative;

boundary="_000_46E077D8EA00064493A770000B0EB2ED1DB14EDB3PRD0502MB114eu_"

MIME-Version: 1.0

X-OriginatorOrg: DOMAIN.nl

Yes, this looks like the problem we're having. We started getting the NDRs around 3pm, Friday UK time - so I imagine the problem started on Thursday around that time.

Its becoming rather an issue now, no indication of a resolution yet.....

Hi SupportAdminHawk,

I am having the exact same problem with a client in Germany.  All bounced emails have a 169.x.x.x address for the sending mail server.

I wonder if Microsoft is working on a fix because this might be relevant for many accounts.

Do you know the default time it takes to get the NDR when the email can not be sent?

Best Regards.

I would guess it is 24 hours to generate the NDR - so for us this issue probably started Thursday UK time.

I haven't seen any this morning from users, but we've not had any update since we spoke to MS support yesterday afternoon which is not that good.

I would raise a support ticket with the error message and see if we can get a response out of the 365 team.

Cheers.

Hi,

The problem may also caused by the temporary network connectivity issues. If not all the emails receive NDR when sending to the same external domains, you may also check the message size, or the attachment size to see if something exceed the limitation of the recipients as the More Information in the article in Jack's reply.

Thanks,
Reken Liu

HI Reken,

yes obviously it could be connectivity at the receving end but I think it is unlikley in this case - within 20 minutes for one user we recevied NDRs from email addresses at bt.com (the main telco here in the UK), rbs.com (one of the largest banks here in UK), gmail.com, kpmg.com (major business) as well as 5 other small businesses that were receving emails from other users without problems - I think the issue is to do with an internal configuration problem on the 365 infrastructure as the notes from our conversation with MS hint:

"When it doesn’t work and gives the 550 error the ip address presented is a private one 169.254.2.235 which does not look up by DNS"

I believe that if it was to do with message size a different NDR would be generated

MIght you be able to raise this up the chain at all Reken? Our support ticket doesnt seem to be getting anywhere

Many thanks

Mark

We are experiencing similar problems. Here are the bounce headers of two failed messages for reference:

TONAME@TARGETDOMAIN.fi

#550 4.4.7 QUEUE.Expired; message expired ##

Original message headers:

Received: from DB3PRD0502MB099.eurprd05.prod.outlook.com ([169.254.2.235]) by

DB3PRD0502HT011.eurprd05.prod.outlook.com ([10.3.48.120]) with mapi id

14.01.0225.071; Thu, 6 Oct 2011 11:29:16 +0000

From: FROMNAME <FROMNAME@OURDOMAIN.fi>

To: TONAME <TONAME@TARGETDOMAIN.fi>

Subject: subject

Thread-Topic: subject

Thread-Index: AcyEGUSsJf3LVvQOTbS3D2EtdXzwvQ==

Importance: high

X-Priority: 1

Date: Thu, 6 Oct 2011 11:29:14 +0000

Message-ID: <9CC0D05C243DF34EAD2B9256EC871DBC4291F2@DB3PRD0502MB099.eurprd05.prod.outlook.com>

Accept-Language: fi-FI, en-US

Content-Language: fi-FI

X-MS-Has-Attach: yes

X-MS-TNEF-Correlator:

x-originating-ip: [10.3.4.7]

Content-Type: multipart/mixed;

boundary="_004_9CC0D05C243DF34EAD2B9256EC871DBC4291F2DB3PRD0502MB099eu_"

MIME-Version: 1.0

X-OriginatorOrg: OURDOMAIN.fi

-------------

TONAME2@saunalahti.fi

#550 4.4.7 QUEUE.Expired; message expired ##

Original message headers:

Received: from DB3PRD0502MB100.eurprd05.prod.outlook.com ([169.254.4.182]) by

DB3PRD0502HT012.eurprd05.prod.outlook.com ([10.3.48.169]) with mapi id

14.01.0225.071; Thu, 6 Oct 2011 15:45:10 +0000

From: FROMNAME2 <FROMNAME2@OURDOMAIN2.fi>

To: TONAME2 <TONAME2@saunalahti.fi>

Subject: VS: telkkari

Thread-Topic: telkkari

Thread-Index: AcyEPZDxMBgFJKlBQ/q5/k3ElxjqXAAAL3Nw

Date: Thu, 6 Oct 2011 15:45:09 +0000

Message-ID: <99E50A98F2E72E47AEF4AC9847D8B95231AEEA@DB3PRD0502MB100.eurprd05.prod.outlook.com>

References: <000301cc843d$92309270$b691b750$@NAME@saunalahti.fi>

In-Reply-To: <000301cc843d$92309270$b691b750$@NAME@saunalahti.fi>

Accept-Language: fi-FI, en-US

Content-Language: fi-FI

X-MS-Has-Attach:

X-MS-TNEF-Correlator:

x-originating-ip: [10.3.4.10]

Content-Type: multipart/alternative;

boundary="_000_99E50A98F2E72E47AEF4AC9847D8B95231AEEADB3PRD0502MB100eu_"

MIME-Version: 1.0

X-OriginatorOrg: OURDOMAIN2.fi

we're getting significant numbers of these NDRs from all users (on our domain) on the 365 platform - this is getting serious for us.....

Exactly the same here problem here. We got 2 NDRs on Thursday, 4 on Friday, 6 on Saturday and more than 10 today Sunday.

Microsoft: update please, this is really getting serious!

I'd just like to also comment that this is happening to us also, same NDR message, same random emails, same some emails getting through, same IP address range on the failed ones.  It started Wednesday at about 11am, and have been receiving NDR's since Thursday.  It's making me look a little silly as my office is complaining about emails not getting through, and there is nothing I can do about it!

I have a support ticket set up, but it needs to be sorted soon.

Hi All,

Appreciate all the feedbacks. Regarding this issue, I have sent private messages to some of you, and will continue to follow and monitor this issue. Any solutions or information will be updated in the forum as soon as possible. Apologize for the inconvenience, thanks for your understanding.

Best Regards,
Reken Liu

Please PM me re this issue as we are also affected