Зрада
Доброго дня!
На підставі статей 1, 13, 19, 20 Закону України «Про доступ до публічної інформації» від 13 січня 2011 року, які надають право звертатись із запитами до розпорядників інформації щодо надання публічної інформації, прошу надати наступну інформацію (наступні документи):
Як стало вiдомо з телеграм каналу:
Кабмин рассматривает решение о принудительном изъятии судов под флагом РФ, которые находятся на судоремонтном заводе Измаила. Об этом рассказал глава Одесской областной военной администрации Максим Марченко.
Как отметил председатель Общественного Совета Комитета ВРУ по вопросам соцполитики и защите прав ветеранов Вадим Латыш, речь идет о девяти судах: Rondo (IMO № 8858013), Svir (IMO № 8866694), Avangard (IMO № 8889438), VOLGO-BALT 225 (IMO № 8230431), VOLGO-BALT 193 (IMO № 8230302), VOLGO-BALT 244 (IMO № 8230584), Omskiy-6 (IMO № 8937687), Naviger-2 (IMO № 8230845), Omskiy-132 (IMO № 8873025).
Эксперт аналитического центра «Левиафан» Николай Мельник рассказал, что направил соответствующее обращение во все правоохранительные органы с требованием уволить из занимаемой должности, а также срочно возбудить уголовное дело в отношении заместителя министра инфраструктуры Юрия Васькова и первого заместителя департамента защиты госсобственности СБУ Ростислава Рашука, которые во время войны действуют в интересах агрессора, пытаясь вывести перечисленные суда в нейтральные воды. Когда гибнут мирные люди, разрушаются города, по меньшей мере странно, что откровенные предатели украинского народа до сих пор занимаю ответственные посты в жизненно важных министерствах и ведомствах.
Прошу поiнформувати про
дату та номер урядового рiшення про нацiоналiзацiю 9 росiйських суден
дату та номер кримiнальних проваджень щодо мiнicтра iнфраструктури та його заступника Васькова по статті 111 за зраду
дату та номер кримiнальних проваджень щодо керiвництва СБУ та першого заступника Рашука по статті 111 за зраду
З повагою,
Олена Семенiвна Мережко
Your message to [gpu request email] couldn't be delivered.
public wasn't found at gp.gov.ua.
foi+request-101277-f. . . Office 365 public
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: 4/8/2022 4:54:12 PM
Sender Address: [FOI #101277 email]
Recipient Address: [gpu request email]
Subject: æ -
Error Details
Reported error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient
[gpu request email] not found by SMTP address lookup
DSN generated by: PR3P195MB0522.EURP195.PROD.OUTLOOK.COM
Message Hops
HOP TIME FROM TO WITH RELAY
(UTC) TIME
4/8/2022 local (Exim 4.89) (envelope-from
1 4:54:12 alaveteli dostup.pravda.com.ua <[FOI #101277 email]>) *
PM
4/8/2022 Microsoft SMTP Server (version=TLS1_2, 5 min,
2 4:59:57 dostup.pravda.com.ua AM7EUR06FT010.mail.protection.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 45 sec
PM
4/8/2022 Microsoft SMTP Server (version=TLS1_2,
3 4:59:57 AM7EUR06FT010.eop-eur06.prod.protection.outlook.com AS8PR07CA0036.outlook.office365.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
PM
4/8/2022 Microsoft SMTP Server (version=TLS1_2,
4 4:59:57 AS8PR07CA0036.eurprd07.prod.outlook.com PR3P195MB0522.EURP195.PROD.OUTLOOK.COM cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
PM
Original Message Headers
Received: from AS8PR07CA0036.eurprd07.prod.outlook.com (2603:10a6:20b:459::14)
by PR3P195MB0522.EURP195.PROD.OUTLOOK.COM (2603:10a6:102:3e::15) with
Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5144.22; Fri, 8 Apr
2022 16:59:57 +0000
Received: from AM7EUR06FT010.eop-eur06.prod.protection.outlook.com
(2603:10a6:20b:459:cafe::b0) by AS8PR07CA0036.outlook.office365.com
(2603:10a6:20b:459::14) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5164.8 via Frontend
Transport; Fri, 8 Apr 2022 16:59:57 +0000
Authentication-Results: spf=pass (sender IP is 144.76.92.108)
smtp.mailfrom=dostup.pravda.com.ua; dkim=test (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 144.76.92.108 as permitted sender)
receiver=protection.outlook.com; client-ip=144.76.92.108;
helo=dostup.pravda.com.ua;
Received: from dostup.pravda.com.ua (144.76.92.108) by
AM7EUR06FT010.mail.protection.outlook.com (10.233.255.222) with Microsoft
SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
15.20.5144.20 via Frontend Transport; Fri, 8 Apr 2022 16:59:57 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;
d=dostup.pravda.com.ua; s=mail; 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=o0aCJPIumxXE2FO5LkrwNxsl6v/APyc1dxKS0vReva8=; b=xNpRdvAb1R8BWcFMpPNAuYIVZq
wFCaeUuCRiszLNFVXD0XHHO5PKT9gihIcV1ZHfztsCZNZTuygkF6zS8vfkx6t6XcsqALBsAaiVXKr
Wkrk6TIj4+sGkwOWJmxTici/SSdxFv7LElZ/2b2CThi/n34NV4O/y3l9BImvBlhd4/IQ=;
Received: from alaveteli by dostup.pravda.com.ua with local (Exim 4.89)
(envelope-from <[FOI #101277 email]>)
id 1ncrsC-0000Dc-6z
for [gpu request email]; Fri, 08 Apr 2022 19:54:12 +0300
Date: Fri, 08 Apr 2022 19:54:12 +0300
From: =?UTF-8?B?0J7Qu9C10L3QsCDQodC10LzQtdC9adCy0L3QsCDQnNC10YDQtdC20LrQvg==?= <[FOI #101277 email]>
To: FOI requests at gpu <[gpu request email]>
Message-ID: <[email address]>
Subject: =?UTF-8?Q?=D0=86=D0=BD=D1=84=D0=BE=D1=80=D0=BC=D0=B0=D1=86=D1=96=D0=B9=D0=BD=D0=B8=D0=B9?=
=?UTF-8?Q?_=D0=B7=D0=B0=D0=BF=D0=B8=D1=82_-_=D0=97=D1=80=D0=B0=D0=B4=D0=B0?=
MIME-Version: 1.0
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: base64
Return-Path: [FOI #101277 email]
X-EOPAttributedMessage: 0
X-EOPTenantAttributedMessage: 3a5e2e39-0633-4775-8a2f-4b767cf8b4cc:0
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: fb26dee6-ba93-4717-3092-08da198135de
X-MS-TrafficTypeDiagnostic: PR3P195MB0522:EE_
References
Visible links
1. https://go.microsoft.com/fwlink/?LinkId=...
2. https://go.microsoft.com/fwlink/?LinkId=...
3. https://go.microsoft.com/fwlink/?LinkId=...
[ Повідомлення сайту: вищенаведений текст неправильний закодований, тож невідомі символи було вилучено.]
