Framework

Dominic Smith made this Freedom of Information request to ESEP Limited
This authority is not subject to FOI law, so is not legally obliged to respond (details).
This request has been closed to new correspondence. Contact us if you think it should be reopened.

Response to this request is long overdue. Although not legally required to do so, we would have expected ESEP Limited to have responded by now (details). You can complain by requesting an internal review.

Dear FOI Team,

I would be most grateful if you would provide me, under the Freedom of Information Act, details in respect to the contract below.

2664_18 Property, Building and Infrastructure Advice and Management Services

The details we require are:

• Suppliers who applied for inclusion on each framework/contract and were successful & not successful at the PQQ & ITT stages*
• Contract values of each framework/contract (& any sub lots), year to date
• Start date & duration of framework
• Is there an extension clause in the framework(s)/contract(s) and, if so, the duration of the extension?
• Has a decision been made yet on whether the framework(s)/contract(s) are being either extended or renewed?
• Who is the senior officer (outside of procurement) responsible for this contract?

For clarity, the details of the successful and unsuccessful suppliers are kept in the strictest confidence. These details are used only to contact and support suppliers regarding their bidding activity for the relevant contracts.

Yours sincerely,

ESEP Limited

2 Attachments

Your message to [ESEP Limited request email] couldn't be delivered.
glasgow wasn't found at esep.co.uk.
request-584750-4f498. . . Office 365 glasgow
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: 6/24/2019 8:54:21 AM
Sender Address: [FOI #584750 email]
Recipient Address: [ESEP Limited request email]
Subject: Freedom of Information request - Framework
Error Details
Reported error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient
[ESEP Limited request email] not found by SMTP address lookup
DSN generated by: DB7PR03MB3596.eurprd03.prod.outlook.com

Message Hops
HOP TIME FROM TO WITH RELAY
(UTC) TIME
6/24/2019 local (Exim 4.89) (envelope-from
1 8:54:21 foi owl.ukcod.org.uk <[FOI #584750 email]>) *
AM
6/24/2019 esmtps
2 8:54:21 owl.ukcod.org.uk starling.ukcod.org.uk (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) *
AM (Exim 4.89) (envelope-from
<[FOI #584750 email]>)
6/24/2019 Microsoft SMTP Server (version=TLS1_2,
3 8:54:21 mailer102.ukcod.org.uk VE1EUR01FT008.mail.protection.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA) *
AM
6/24/2019 Microsoft SMTP Server (version=TLS1_2,
4 8:54:22 VE1EUR01FT008.eop-EUR01.prod.protection.outlook.com DB6PR0301CA0033.outlook.office365.com cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) 1 sec
AM
6/24/2019 Microsoft SMTP Server (version=TLS1_2,
5 8:54:22 DB6PR0301CA0033.eurprd03.prod.outlook.com DB7PR03MB3596.eurprd03.prod.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
AM

Original Message Headers

Received: from DB6PR0301CA0033.eurprd03.prod.outlook.com (2603:10a6:4:3e::43)
by DB7PR03MB3596.eurprd03.prod.outlook.com (2603:10a6:5:4::16) with Microsoft
SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
15.20.2008.16; Mon, 24 Jun 2019 08:54:22 +0000
Received: from VE1EUR01FT008.eop-EUR01.prod.protection.outlook.com
(2a01:111:f400:7e01::204) by DB6PR0301CA0033.outlook.office365.com
(2603:10a6:4:3e::43) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.2008.13 via Frontend
Transport; Mon, 24 Jun 2019 08:54:22 +0000
Authentication-Results: spf=pass (sender IP is 46.43.39.102)
smtp.mailfrom=whatdotheyknow.com; esep.co.uk; dkim=pass (signature was
verified) header.d=whatdotheyknow.com;esep.co.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
VE1EUR01FT008.mail.protection.outlook.com (10.152.2.67) with Microsoft SMTP
Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA) id
15.20.2008.13 via Frontend Transport; Mon, 24 Jun 2019 08:54:21 +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=HmDK5pEso+FGGrJJj6zB68ew4KJHnq8Zk/Mw2kPGaC4=; b=F5963rEBlp0rOfX0jNW4H52yx
oFCI2rene4FJIGXePYqtrUbwc9wec76LQ+9OSg/GlMIqaaO+Sl8zhFAQQvEx7vAunrECTloKTx3q4
iAtVcDXV/itDpNyJGx8f1/jnmeT1P5v4yqg67D7E9yi0JjF+0pHlGVHf99+d/CfRBCdQpXegoPumV
tknThprpLYtMF+s0vA3aJ/WbMm6V8/xLgvU9b3T/mrfiLLiJKlZJMJLoP8T4cPNxzYqv8wnNtukcx
tZHqNeGla6QiJB2QmxgzmlX8M6AMjhls6AsCDczhranc74fRbkuTQ1SOjrklgkH4GHFaqN6LjrRo6
PbKM54adQ==;
Received: from owl.ukcod.org.uk ([46.43.39.108]:59041)
by starling.ukcod.org.uk with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
(Exim 4.89)
(envelope-from <[FOI #584750 email]>)
id 1hfKk1-00054z-HQ
for [ESEP Limited request email]; Mon, 24 Jun 2019 09:54:21 +0100
Received: from foi by owl.ukcod.org.uk with local (Exim 4.89)
(envelope-from <[FOI #584750 email]>)
id 1hfKk1-0008GI-EI
for [ESEP Limited request email]; Mon, 24 Jun 2019 09:54:21 +0100
Date: Mon, 24 Jun 2019 09:54:21 +0100
From: Dominic Smith <[FOI #584750 email]>
To: FOI requests at ESEP Limited <[ESEP Limited request email]>
Message-ID: <[email address]>
Subject: Freedom of Information request - Framework
MIME-Version: 1.0
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Return-Path: [FOI #584750 email]
X-EOPAttributedMessage: 0
X-EOPTenantAttributedMessage: 512e1c61-e9be-41c2-a87e-f4e16d7c1144:0
X-Forefront-Antispam-Report: CIP:46.43.39.102;IPV:NLI;CTRY:GB;EFV:NLI;
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 62402d28-c154-4973-944c-08d6f8818d13
X-Microsoft-Antispam:
BCL:3;PCL:0;RULEID:(2390118)(7020095)(4652040)(5600148)(711020)(4605104)(4709080)(8001031)(1402095)(71702078);SRVR:DB7PR03MB3596;
X-MS-TrafficTypeDiagnostic: DB7PR03MB3596:
X-MS-Exchange-PUrlCount: 3

References

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

Sent request to ESEP Limited again, using a new contact address.