Décisions et registres sur les dispositifs de surveillance de la commune
A l’attention de Madame/Monsieur la/le Bourgmestre,
Objet : Transparence administrative – Demande d’informations via le site de Transparencia
Personne de Contact : Emmanuelle Hardy, conseillère juridique – [email address]
Dans le cadre de ses missions et conformément à son objet social, la Ligue des droits humains s’intéresse au déploiement des dispositifs de surveillance dans l’espace public.
Aussi, je me permets de vous solliciter en vertu du droit à la transparence consacré par l’art. 32 de la Constitution et de l’article de la loi du 12 novembre 1997 relative à la publicité de l’administration dans les provinces et les communes, afin d’obtenir une copie informatisée des documents administratifs suivants :
a) la liste des caméras fixes dans des lieux ouverts accessibles au public, en ce compris les localisations et les responsables de traitement ;
b) les documents administratifs relatifs à l’installation des dites caméras : les avis délivrés par la commune à destination des responsables de traitement conformément à l’article 5 de la loi du 21 mars 2007 réglant l’installation et l’utilisation de caméras de surveillance ;
c) les analyses d’impact et les documents relatifs aux marchés publics (appels d’offre, cahiers de charges, documents d’attribution, contrats signés pour l’ensemble des marchés passés, dans le cas des marchés classiques et des accords-cadres) concernant les systèmes de surveillance (caméras fixes et mobiles, visuelles et/ou thermiques, drones et bodycams, ANPR, commutateurs et logiciels, etc.) acquis depuis 2000 par la commune, conformément aux lois du 21 mars 2007 et du 17 juin 2016 relative aux marchés publics et de l’arrêté royal du 30 juin 2017 relatif à la passation des marchés publics dans les secteurs classiques.
Je vous remercie de bien vouloir réserver les suites utiles à ce courrier dans le délai de réponse de trente jours prescrit par la loi du 12 novembre 1997.
Je vous prie de croire, Madame/Monsieur la/le Bourgmestre, à l’expression de nos sentiments distingués.
Pour la Commission Nouvelles technologies et vie privée,
Emmanuelle Hardy, conseillère juridique.
Ligue des droits humains
22 rue du boulet
1000 Bruxelles
Your message to [adresse email] couldn't be delivered.
ac.frameries wasn't found at frameries.be.
request-3168-8495e74. . . Office 365 ac.frameries
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/12/2022 5:14:51 PM
Sender Address: [FOI #3168 email]
Recipient [adresse email]
Address:
Demande au nom de la Liberté d'accès à l'information -
Subject: Décisions et registres sur les dispositifs de surveillance
de la commune
Error Details
Reported error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient
[adresse email] not found by SMTP address
lookup
DSN generated by: VI1PR02MB4095.eurprd02.prod.outlook.com
Message Hops
HOP TIME FROM TO WITH RELAY
(UTC) TIME
3/12/2022 local (Exim 4.94.2) (envelope-from
1 5:14:51 foibelgium mstr001sova.srv.mysociety.org <[FOI #3168 email]>) *
PM
3/12/2022 esmtps
2 5:14:52 mstr001sova.srv.mysociety.org starling.ukcod.org.uk (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) 1 sec
PM (Exim 4.89) (envelope-from
<[FOI #3168 email]>)
3/12/2022 Microsoft SMTP Server (version=TLS1_2,
3 5:14:52 starling.ukcod.org.uk VI1EUR04FT024.mail.protection.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
PM
3/12/2022 Microsoft SMTP Server (version=TLS1_2,
4 5:14:53 VI1EUR04FT024.eop-eur04.prod.protection.outlook.com AS8P189CA0008.outlook.office365.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec
PM
3/12/2022 Microsoft SMTP Server (version=TLS1_2,
5 5:14:53 AS8P189CA0008.EURP189.PROD.OUTLOOK.COM VI1PR02MB4095.eurprd02.prod.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
PM
Original Message Headers
Received: from AS8P189CA0008.EURP189.PROD.OUTLOOK.COM (2603:10a6:20b:31f::16)
by VI1PR02MB4095.eurprd02.prod.outlook.com (2603:10a6:803:7a::30) with
Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5061.25; Sat, 12 Mar
2022 17:14:53 +0000
Received: from VI1EUR04FT024.eop-eur04.prod.protection.outlook.com
(2603:10a6:20b:31f:cafe::7d) by AS8P189CA0008.outlook.office365.com
(2603:10a6:20b:31f::16) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5061.24 via Frontend
Transport; Sat, 12 Mar 2022 17:14:53 +0000
Authentication-Results: spf=pass (sender IP is 46.43.39.112)
smtp.mailfrom=transparencia.be; dkim=none (message not signed)
header.d=none;dmarc=bestguesspass action=none header.from=transparencia.be;
Received-SPF: Pass (protection.outlook.com: domain of transparencia.be
designates 46.43.39.112 as permitted sender) receiver=protection.outlook.com;
client-ip=46.43.39.112; helo=starling.ukcod.org.uk;
Received: from starling.ukcod.org.uk (46.43.39.112) by
VI1EUR04FT024.mail.protection.outlook.com (10.152.29.156) with Microsoft SMTP
Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
15.20.5061.22 via Frontend Transport; Sat, 12 Mar 2022 17:14:52 +0000
Received: from mstr001sova.srv.mysociety.org ([2a00:1098:80:3b::b:1]:60786)
by starling.ukcod.org.uk with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
(Exim 4.89)
(envelope-from <[FOI #3168 email]>)
id 1nT5KO-0005Ex-3S
for [adresse email]; Sat, 12 Mar 2022 17:14:52 +0000
Received: from foibelgium by mstr001sova.srv.mysociety.org with local (Exim 4.94.2)
(envelope-from <[FOI #3168 email]>)
id 1nT5KN-003G7N-OO
for [adresse email]; Sat, 12 Mar 2022 17:14:51 +0000
Date: Sat, 12 Mar 2022 17:14:51 +0000
From: Ligue des Droits Humains <[FOI #3168 email]>
To: =?UTF-8?B?TGliZXJ0w6kgZCdhY2PDqHMgw6AgbCdpbmZvcm1hdGlvbiBkZW1hbmRlcyA=?= =?UTF-8?B?w6AgRnJhbWVyaWVz?= <[adresse email]>
Message-ID: <[adresse email]>
Subject: =?UTF-8?Q?Demande_au_nom_de_la_Libert=C3=A9_d'acc=C3=A8s_=C3=A0?=
=?UTF-8?Q?_l'information_-_D=C3=A9cisions_et_registres_sur_les_dispositifs?=
=?UTF-8?Q?_de_surveillance_de_la_commune?=
MIME-Version: 1.0
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Return-Path: [FOI #3168 email]
X-EOPAttributedMessage: 0
X-EOPTenantAttributedMessage: b5b87662-86d0-4531-b666-8680ea2ab60e:0
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 19afcd67-2cfe-4528-f5b4-08da044bd280
X-MS-TrafficTypeDiagnostic: VI1PR02MB4095: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=...
Sent request to Commune de Frameries again, using a new contact address.