ЗПІ про використання бюджетних коштів

Ваш документ зареєстрований №3-Г-ЗПІ-1182-001 від 17.07.2023

Your message to [email address] couldn't be delivered.
mail wasn't found at office.lvivcity.gov.ua.
foi+request-115058-3. . . Office 365 mail
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: 7/25/2023 10:06:43 AM
Sender Address: [FOI #115058 email]
Recipient Address: [email address]
Subject: Re: 3---1182-001 17.07.2023
Error Details
Error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient
[email address] not found by SMTP address
lookup
Message rejected DU0P189MB2371.EURP189.PROD.OUTLOOK.COM
by:
Notification Details
Sent by: DU0P189MB2371.EURP189.PROD.OUTLOOK.COM

Message Hops
HOP TIME FROM TO WITH RELAY
(UTC) TIME
7/25/2023
1 10:06:43 dostup.pravda.com.ua *
AM
7/25/2023 Microsoft SMTP Server (version=TLS1_2,
2 10:06:45 dostup.pravda.com.ua AM7EUR06FT037.mail.protection.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 2 sec
AM
7/25/2023 Microsoft SMTP Server (version=TLS1_2,
3 10:06:45 AM7EUR06FT037.eop-eur06.prod.protection.outlook.com AS9PR06CA0433.outlook.office365.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
AM
7/25/2023 Microsoft SMTP Server (version=TLS1_2,
4 10:06:47 AS9PR06CA0433.eurprd06.prod.outlook.com DU0P189MB2371.EURP189.PROD.OUTLOOK.COM cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 2 sec
AM

Original Message Headers

Received: from AS9PR06CA0433.eurprd06.prod.outlook.com (2603:10a6:20b:49e::11)
by DU0P189MB2371.EURP189.PROD.OUTLOOK.COM (2603:10a6:10:47b::15) with
Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6609.32; Tue, 25 Jul
2023 10:06:47 +0000
Received: from AM7EUR06FT037.eop-eur06.prod.protection.outlook.com
(2603:10a6:20b:49e:cafe::f3) by AS9PR06CA0433.outlook.office365.com
(2603:10a6:20b:49e::11) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6609.33 via Frontend
Transport; Tue, 25 Jul 2023 10:06:45 +0000
Authentication-Results: spf=pass (sender IP is 178.20.154.234)
smtp.mailfrom=dostup.pravda.com.ua; dkim=pass (signature was verified)
header.d=dostup.pravda.com.ua;dmarc=pass action=none
header.from=dostup.pravda.com.ua;
Received-SPF: Pass (protection.outlook.com: domain of dostup.pravda.com.ua
designates 178.20.154.234 as permitted sender)
receiver=protection.outlook.com; client-ip=178.20.154.234;
helo=dostup.pravda.com.ua; pr=C
Received: from dostup.pravda.com.ua (178.20.154.234) by
AM7EUR06FT037.mail.protection.outlook.com (10.233.255.131) with Microsoft
SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
15.20.6631.25 via Frontend Transport; Tue, 25 Jul 2023 10:06:45 +0000
Received: by dostup.pravda.com.ua (Postfix, from userid 1000)
id 65A403C0AF8; Tue, 25 Jul 2023 13:06:43 +0300 (EEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dostup.pravda.com.ua;
s=202206; t=1690279603;
bh=zO2R68cGEhirZ/5d0CnXdB4U2FelJVeqNza3aWQH7c0=;
h=Date:From:To:Subject:From;
b=Fsvtftr/IGBz+QxNvd1a3kKSsYhYkw1GXzhZdPpFRXbRenqQ97lbfWjzd+oiZ2e9r
DNxvfe9ZBHm8itCIRBZ5OZYALKBBrH+NPXsze8Z/MIz8ATEeYovluVQZVpPehtlTFh
R/bQpZqjcAj/bwirdCg3svHpVc1b5VPg2uYl26n6beyoPW0sd9K7Hl9nDP1Tj+yzEr
TpBHlK3qyHdu6V7r4Hl/bM4mo6rHcKFqIRdk/AWtQeb4eRnVNuoYUrNQD7OM8KCMYX
n4j4+QHqPLeYrZaAolYtGYLPF5bjfiLrQnEc/ANGxUCGGFAx5jlcSptUiNX5No6XHW
HBgZgoU7siN9w==
Date: Tue, 25 Jul 2023 13:06:43 +0300
From: =?UTF-8?B?0JzQuNC60L7Qu9CwINCT0L7QvdGH0LDRgNC10L3QutC+?= <[FOI #115058 email]>
To: "office.mail" <[email address]>
Message-ID: <[email address]>
Subject: =?UTF-8?Q?Re:_=D0=92=D0=B0=D1=88?=
=?UTF-8?Q?_=D0=B4=D0=BE=D0=BA=D1=83=D0=BC=D0=B5=D0=BD=D1=82?=
=?UTF-8?Q?_=D0=B7=D0=B0=D1=80=D0=B5=D1=94=D1=81=D1=82=D1=80=D0=BE=D0=B2=D0=B0=D0=BD=D0=B8=D0=B9?=
=?UTF-8?Q?_=E2=84=963-=D0=93-=D0=97=D0=9F=D0=86-1182-001_=D0=B2=D1=96=D0=B4?=
=?UTF-8?Q?_17.07.2023?=
MIME-Version: 1.0
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: base64
Return-Path: [FOI #115058 email]
X-EOPAttributedMessage: 0
X-EOPTenantAttributedMessage: 165b5718-8f3a-4f7e-9fac-33ac5e255d25:0
X-MS-PublicTrafficType: Email
X-MS-TrafficTypeDiagnostic: AM7EUR06FT037:EE_|DU0P189MB2371:EE_
X-MS-Office365-Filtering-Correlation-Id: 3e721214-9c4b-48a7-c6e6-08db8cf6da6d

References

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

[ Повідомлення сайту: вищенаведений текст неправильний закодований, тож невідомі символи було вилучено.]

[Subject only] Fwd: Відповідь на запит

показати цитоване

[Subject only] Fwd: Відповідь на запит - плани використання коштів

показати цитоване