Your message to [Royal Shakespeare Company request email] couldn't be delivered.
liz.thompson wasn't found at rsc.org.uk.
request-657062-f77fc. . . Office 365 liz.thompson
Action Required Recipient
Unknown To address
How to Fix It
The address may be misspelled or may not exist. Try one or more of the
following:
* Send the message again following these steps: In Outlook, open this
non-delivery report (NDR) and choose Send Again from the Report
ribbon. In Outlook on the web, select this NDR, then select the link
"To send this message again, click here." Then delete and retype the
entire recipient address. If prompted with an Auto-Complete List
suggestion don't select it. After typing the complete address, click
Send.
* Contact the recipient (by phone, for example) to check that the
address exists and is correct.
* The recipient may have set up email forwarding to an incorrect
address. Ask them to check that any forwarding they've set up is
working correctly.
* Clear the recipient Auto-Complete List in Outlook or Outlook on the
web by following the steps in this article: [1]Fix email delivery
issues for error code 5.1.10 in Office 365, and then send the message
again. Retype the entire recipient address before selecting Send.
If the problem continues, forward this message to your email admin. If
you're an email admin, refer to the More Info for Email Admins section
below.
Was this helpful? [2]Send feedback to Microsoft.
--------------------------------------------------------------------------
More Info for Email Admins
Status code: 550 5.1.10

This error occurs because the sender sent a message to an email address
hosted by Office 365 but the address is incorrect or doesn't exist at the
destination domain. The error is reported by the recipient domain's email
server, but most often it must be fixed by the person who sent the
message. If the steps in the How to Fix It section above don't fix the
problem, and you're the email admin for the recipient, try one or more of
the following:

The email address exists and is correct - Confirm that the recipient
address exists, is correct, and is accepting messages.

Synchronize your directories - If you have a hybrid environment and are
using directory synchronization make sure the recipient's email address is
synced correctly in both Office 365 and in your on-premises directory.

Errant forwarding rule - Check for forwarding rules that aren't behaving
as expected. Forwarding can be set up by an admin via mail flow rules or
mailbox forwarding address settings, or by the recipient via the Inbox
Rules feature.

Recipient has a valid license - Make sure the recipient has an Office 365
license assigned to them. The recipient's email admin can use the Office
365 admin center to assign a license (Users > Active Users > select the
recipient > Assigned License > Edit).

Mail flow settings and MX records are not correct - Misconfigured mail
flow or MX record settings can cause this error. Check your Office 365
mail flow settings to make sure your domain and any mail flow connectors
are set up correctly. Also, work with your domain registrar to make sure
the MX records for your domain are configured correctly.

For more information and additional tips to fix this issue, see [3]Fix
email delivery issues for error code 5.1.10 in Office 365.
Original Message Details
Created Date: 3/30/2020 6:26:06 AM
Sender Address: [FOI #657062 email]
Recipient Address: [Royal Shakespeare Company request email]
Subject: Freedom of Information request - FM - Hard Services
Error Details
Reported error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient
[Royal Shakespeare Company request email] not found by SMTP address lookup
DSN generated by: HE1P190MB0090.EURP190.PROD.OUTLOOK.COM

Message Hops
HOP TIME FROM TO WITH RELAY
(UTC) TIME
3/30/2020 local (Exim 4.89) (envelope-from
1 6:26:06 foi owl.ukcod.org.uk <[FOI #657062 email]>) *
AM
3/30/2020 esmtps
2 6:26:06 owl.ukcod.org.uk starling.ukcod.org.uk (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) *
AM (Exim 4.89) (envelope-from
<[FOI #657062 email]>)
3/30/2020 Microsoft SMTP Server (version=TLS1_2,
3 6:26:07 mailer102.ukcod.org.uk VE1EUR01FT040.mail.protection.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec
AM
3/30/2020 Microsoft SMTP Server (version=TLS1_2,
4 6:26:07 VE1EUR01FT040.eop-EUR01.prod.protection.outlook.com AM6P195CA0064.outlook.office365.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
AM
3/30/2020 Microsoft SMTP Server (version=TLS1_2,
5 6:26:07 AM6P195CA0064.EURP195.PROD.OUTLOOK.COM HE1P190MB0090.EURP190.PROD.OUTLOOK.COM cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
AM

Original Message Headers

Received: from AM6P195CA0064.EURP195.PROD.OUTLOOK.COM (2603:10a6:209:87::41)
by HE1P190MB0090.EURP190.PROD.OUTLOOK.COM (2603:10a6:3:ca::11) with Microsoft
SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
15.20.2856.20; Mon, 30 Mar 2020 06:26:07 +0000
Received: from VE1EUR01FT040.eop-EUR01.prod.protection.outlook.com
(2603:10a6:209:87:cafe::b2) by AM6P195CA0064.outlook.office365.com
(2603:10a6:209:87::41) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2856.20 via Frontend
Transport; Mon, 30 Mar 2020 06:26:07 +0000
Authentication-Results: spf=pass (sender IP is 46.43.39.102)
smtp.mailfrom=whatdotheyknow.com; rsc.org.uk; dkim=pass (signature was
verified) header.d=whatdotheyknow.com;rsc.org.uk; dmarc=pass action=none
header.from=whatdotheyknow.com;
Received-SPF: Pass (protection.outlook.com: domain of whatdotheyknow.com
designates 46.43.39.102 as permitted sender) receiver=protection.outlook.com;
client-ip=46.43.39.102; helo=mailer102.ukcod.org.uk;
Received: from mailer102.ukcod.org.uk (46.43.39.102) by
VE1EUR01FT040.mail.protection.outlook.com (10.152.3.46) with Microsoft SMTP
Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
15.20.2856.17 via Frontend Transport; Mon, 30 Mar 2020 06:26:07 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;
d=whatdotheyknow.com; s=2014a.mysociety; h=Content-Transfer-Encoding:
Content-Type:Mime-Version:Subject:Message-ID:To:From:Date:Sender:Reply-To:Cc:
Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender:
Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id:
List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive;
bh=H6DiHcFSOhoCW9Q6obNSC3Vn7VjeaM4Logbm9ed1+cc=; b=Hv5Opc521vPYEgMeTiDzpiUeo
CXbSyg8W/2D1ncfMFtvLM2Hfg8YPxqz+AWeJ7xlKe43ian7qT36U1tkRqqlLwp+iipp9/FqG9I3RQ
H9Mp+rHM89LPJ+GYvsDTjmdCG1+Dw3YrqKe/G1In9kErDZ0hjcdFMqxUBMKbnj4D1K8OHap/hE0AD
73R+094MaFio6i7IMAIcs9ay85u8JVUy5Sb9PWwGMRBh1B12YzP2ZuQbtftcVVyPcCf3ydU6jpqGQ
8wuP+x5Wy3wIGyznVmouDXRUEbyZocXC1f779rStcZY31elhQg+VcjMq0Vals1vvlSdr9z7yiMZGq
pRoteIWlA==;
Received: from owl.ukcod.org.uk ([46.43.39.108]:35511)
by starling.ukcod.org.uk with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
(Exim 4.89)
(envelope-from <[FOI #657062 email]>)
id 1jIns6-0001dr-Sd
for [Royal Shakespeare Company request email]; Mon, 30 Mar 2020 07:26:06 +0100
Received: from foi by owl.ukcod.org.uk with local (Exim 4.89)
(envelope-from <[FOI #657062 email]>)
id 1jIns6-0005CA-JK
for [Royal Shakespeare Company request email]; Mon, 30 Mar 2020 07:26:06 +0100
Date: Mon, 30 Mar 2020 07:26:06 +0100
From: Craig Wilkinson <[FOI #657062 email]>
To: FOI requests at Royal Shakespeare Company <[Royal Shakespeare Company request email]>
Message-ID: <[email address]>
Subject: Freedom of Information request - FM - Hard Services
MIME-Version: 1.0
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: 7bit
Return-Path: [FOI #657062 email]
X-EOPAttributedMessage: 0
X-EOPTenantAttributedMessage: 8a38a804-02cd-456a-9217-1296ed8c79c8:0
X-Forefront-Antispam-Report: CIP:46.43.39.102;IPV:;CTRY:GB;EFV:NLI;
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 84e68d54-d858-4b17-e67d-08d7d4733b21
X-MS-TrafficTypeDiagnostic: HE1P190MB0090:

References

Visible links
1. https://go.microsoft.com/fwlink/?LinkId=...
2. https://go.microsoft.com/fwlink/?LinkId=...
3. https://go.microsoft.com/fwlink/?LinkId=...

Thank you for your email (a copy of which can be found at the bottom of
this email).

Your message has been logged. The RSC welcomes and encourages all feedback
from its visitors and audiences. All complaints will be listened to and
taken seriously.

What happens next.
We aim to respond with an answer to all concerns raised by the visitor
within 3 weeks, or explain why this is not possible within this time,
however the more detailed your complaint is the longer this will take.

Our team is currently in the process of contacting all ticket buyers who
are affected by the current cancelled performances owing to the Covid-19
outbreak. If you have tickets for a cancelled performance, please be
assured that a member of the team will be in touch with you over the
coming weeks with your refund options.

Whenever possible the staff most knowledgeable about the issue you raise
will be tasked with investigating and replying direct. This will ensure a
more accurate response, but may take longer.

Frequently asked questions.
Our Contact Us pages (www.rsc.org.uk/contact-us) contain lists of FAQs
which are regularly updated and should provide audience members and
visitors with immediate answers to a great many of their queries. Audience
members and visitors can also use the drop down list of categories of
enquiry to give us feedback on a range of issues. Emails sent through this
route will be re-directed to the most relevant department who can help.

This is an automatically generated acknowledgement. Please do not reply to
this email.