Arrêtés préfectoraux autorisant les emplacements de caméras de surveillance

Quelqu'un a fait cette demande de droit d'accès à l'information à Mairie - Igny dans le cadre d'un lot envoyé à 49 autorités Des dispositifs automatiques anti-spam sont en place pour cette requête plus ancienne. Merci de nous faire savoir si une réponse complémentaire est attendue ou si vous rencontrez des difficultés à répondre.

La réponse à cette demande est très en retard. Selon la loi, l'administration aurait déjà dû répondre Si vous avez envoyé la demande initiale, et si les délais le permettent encore, vous pouvez saisir la CADA.

Madame, Monsieur,

En application des dispositions des articles L. 311-1 et suivants du code des relations entre le public et l’administration, je sollicite, au nom de l'association La Quadrature Du Net (LQDN), la communication (de préférence par voie électronique) de l'ensemble des arrêtés préfectoraux autorisant l'installation de caméras de surveillance sur votre territoire.

Je souhaite recevoir ces documents dans un format numérique, ouvert et réutilisable. Pour ce faire, veuillez m’indiquer leur adresse de téléchargement ou me les envoyer en pièce jointe.

À défaut de réponse dans un délai d’un mois, ou dans l’hypothèse d’une réponse incomplète, je serais contrainte de saisir la Commission d’accès aux documents administratifs (CADA).

Veuillez agréer, Madame, Monsieur, l'expression de mes sentiments distingués.

[information personnelle cachée],
Pour La Quadrature du Net

Mairie - Igny

2 pièces jointes

  • Attachment

    attachment.delivery status

    0K Download

  • Attachment

    Demande au titre du droit d acc s aux documents administratifs Arr t s pr fectoraux autorisant les emplacements de cam ras de surveillance.txt

    2K Download View as HTML

Your message to [adresse email] couldn't be delivered.
direction.generale wasn't found at igny.fr.
dada+request-646-d79. . . Office 365 direction.generale
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/1/2021 7:10:11 PM
Sender Address: [FOI #646 email]
Recipient Address: [adresse email]
Demande au titre du droit d’accès aux documents
Subject: administratifs - Arrêtés préfectoraux autorisant les
emplacements de caméras de surveillance
Error Details
Reported error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient
[adresse email] not found by SMTP address
lookup
DSN generated by: AM0P195MB0515.EURP195.PROD.OUTLOOK.COM

Message Hops
HOP TIME FROM TO WITH RELAY
(UTC) TIME
3/1/2021
1 7:10:11 dadaprod1.madada.fr *
PM
3/1/2021
2 7:10:12 dadaprod1.madada.fr AM5EUR02FT057.mail.protection.outlook.com Microsoft SMTP Server 1 sec
PM
3/1/2021 Microsoft SMTP Server (version=TLS1_2,
3 7:10:12 AM5EUR02FT057.eop-EUR02.prod.protection.outlook.com AM6PR10CA0108.outlook.office365.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
PM
3/1/2021 Microsoft SMTP Server (version=TLS1_2,
4 7:10:12 AM6PR10CA0108.EURPRD10.PROD.OUTLOOK.COM AM0P195MB0515.EURP195.PROD.OUTLOOK.COM cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
PM

Original Message Headers

Received: from AM6PR10CA0108.EURPRD10.PROD.OUTLOOK.COM (2603:10a6:209:8c::49)
by AM0P195MB0515.EURP195.PROD.OUTLOOK.COM (2603:10a6:20b:16a::18) with
Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3890.20; Mon, 1 Mar
2021 19:10:12 +0000
Received: from AM5EUR02FT057.eop-EUR02.prod.protection.outlook.com
(2603:10a6:209:8c:cafe::62) by AM6PR10CA0108.outlook.office365.com
(2603:10a6:209:8c::49) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3890.19 via Frontend
Transport; Mon, 1 Mar 2021 19:10:12 +0000
Authentication-Results: spf=pass (sender IP is 92.243.18.104)
smtp.mailfrom=madada.fr; igny.fr; dkim=test (signature was verified)
header.d=madada.fr;igny.fr; dmarc=bestguesspass action=none
header.from=madada.fr;
Received-SPF: Pass (protection.outlook.com: domain of madada.fr designates
92.243.18.104 as permitted sender) receiver=protection.outlook.com;
client-ip=92.243.18.104; helo=dadaprod1.madada.fr;
Received: from dadaprod1.madada.fr (92.243.18.104) by
AM5EUR02FT057.mail.protection.outlook.com (10.152.9.242) with Microsoft SMTP
Server id 15.20.3890.19 via Frontend Transport; Mon, 1 Mar 2021 19:10:12
+0000
Received: by dadaprod1.madada.fr (Postfix, from userid 1001)
id 001D340DF9; Mon, 1 Mar 2021 20:10:11 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=madada.fr; s=mail;
t=1614625812; bh=ZGIFqmwESYzDWq4ekvSmTjFplQqwZeFaJGI7qtviCPs=;
h=Date:From:To:Subject:From;
b=YN1BqnZ+bNa3f3jyjCBWH68xGB3BBH2HZbt4gLfQy/KS64QG7jCcl20Y1BFY9+HE5
Ddl5LYchofL36qkDreekEWmCUVSjknaDc8sCFzKzcbfexm9bY4p+Zj3cMNn3b0+rZI
WdhZ9Mle7PTzoeNnh4JD1fM2dxOSXamDN8ylLGq0=
Date: Mon, 01 Mar 2021 20:10:11 +0100
From: Eda <[FOI #646 email]>
To: =?UTF-8?B?ZHJvaXQgZCdhY2PDqHMgw6AgbCdpbmZvcm1hdGlvbiBkZW1hbmRlcyDDoCBN?= =?UTF-8?B?YWlyaWUgLSBJZ255IDkxMzEyLTAx?= <[adresse email]>
Message-ID: <[adresse email]>
Subject: =?UTF-8?Q?Demande_au_titre_du_droit_d=E2=80=99acc=C3=A8s_aux?=
=?UTF-8?Q?_documents_administratifs_-_Arr=C3=AAt=C3=A9s_pr=C3=A9fectoraux?=
=?UTF-8?Q?_autorisant_les_emplacements_de_cam=C3=A9ras_de_surveillance?=
MIME-Version: 1.0
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Return-Path: [FOI #646 email]
X-EOPAttributedMessage: 0
X-EOPTenantAttributedMessage: b667a651-9174-4a37-9497-1b739063cbb8:0
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: cf9b941a-8fbb-4c94-9210-08d8dce5a37c
X-MS-TrafficTypeDiagnostic: AM0P195MB0515:
X-MS-Exchange-MinimumUrlDomainAge: madada.fr#587

References

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

Nous avons envoyé à nouveau la demande à Mairie - Igny, en utilisant une nouvelle adresse de contact.