Enquête du journal LeSoir : projets de délibérations du conseil communal du mois de juin et notes explicatives
Cher/Chère Commune de Frameries,
Concerne : Enquête du journal Le Soir : demande des projets de délibérations du conseil communal du mois de juin et note de synthèse explicative
En ce moment, le Parlement wallon discute d'un décret qui permettra aux citoyens de consulter en ligne les projets de délibérations avant chaque conseil communal afin d'augmenter la confiance et la participation dans la vie locale. Cette mise en ligne est déjà effective dans plusieurs communes comme Liège*, Mons, Huy, Verviers, Tubize ou encore Ottignies-Louvain-la-Neuve. A priori, simple et évident, la publication des projets de délibération du conseil communal est loin d’être mise en place partout.
Tous les partis politiques se sont accordés le 11 mai sur ce principe. (voir la vidéo du parlement wallon du 11/5/2021 : https://youtu.be/ZurP0WAzVgQ )
Dans ce cadre, LeSoir répertorie les communes qui acceptent de transmettre les projets de délibérations publics, celles qui refusent et celles qui ont l'intention de mettre les projets de délibérations en ligne avant le prochain conseil communal.
( Voire notre article à paraître )
Pour cette enquête, serait-il possible d’obtenir, en réponse à ce message, une copie numérique des projets de délibération des points inscrits à l’ordre du jour public de la séance publique, tel que transmis aux conseillers communaux (il ne s'agit donc pas du PV réalisé à posteriori, mais de sa version provisoire d'avant le conseil)
- pour le conseil communal de juin,
- quand ils seront prêts, ceux du prochain conseil communal.
J’aurais également aimé obtenir la note de synthèse explicative des points publics des mêmes conseils communaux et savoir pour quels points du conseil communal de juin, la décision finale diffère du projet de délibération.
Pour terminer, pourriez-vous me fournir l'énumération des annexes faisant partie intégrante de ces délibérations de juin (juste leur intitulé, sans les pièces) ?
Merci pour votre collaboration en attente d’une réponse de votre part
Bien à vous,
Pascal Lorent, Journaliste au Soir
(*) voir également
https://www.rtbf.be/info/regions/liege/d... )
Sent request to Gemeente Frameries again.
Your message to [adresse email] couldn't be delivered.
ac.frameries wasn't found at frameries.be.
request-2575-2964810. . . 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: 7/31/2021 5:17:02 PM
Sender Address: [FOI #2575 email]
Recipient [adresse email]
Address:
Demande au nom de la Liberté d'accès à l'information -
Subject: Enquête du journal LeSoir : projets de délibérations du
conseil communal du mois de juin et notes explicatives
Error Details
Reported error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient
[adresse email] not found by SMTP address
lookup
DSN generated by: PAXPR02MB7455.eurprd02.prod.outlook.com
Message Hops
HOP TIME FROM TO WITH RELAY
(UTC) TIME
7/31/2021 local (Exim 4.89) (envelope-from
1 5:17:02 foibelgium owl.ukcod.org.uk <[FOI #2575 email]>) *
PM
7/31/2021 esmtps
2 5:17:02 owl.ukcod.org.uk bittern.ukcod.org.uk (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) *
PM (Exim 4.89) (envelope-from
<[FOI #2575 email]>)
7/31/2021 Microsoft SMTP Server (version=TLS1_2,
3 5:17:03 bittern.ukcod.org.uk VI1EUR04FT064.mail.protection.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec
PM
7/31/2021 Microsoft SMTP Server (version=TLS1_2,
4 5:17:04 VI1EUR04FT064.eop-eur04.prod.protection.outlook.com AM6PR10CA0065.outlook.office365.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec
PM
7/31/2021 Microsoft SMTP Server (version=TLS1_2,
5 5:17:04 AM6PR10CA0065.EURPRD10.PROD.OUTLOOK.COM PAXPR02MB7455.eurprd02.prod.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
PM
Original Message Headers
Received: from AM6PR10CA0065.EURPRD10.PROD.OUTLOOK.COM (2603:10a6:209:80::42)
by PAXPR02MB7455.eurprd02.prod.outlook.com (2603:10a6:102:1cf::19) with
Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4373.18; Sat, 31 Jul
2021 17:17:04 +0000
Received: from VI1EUR04FT064.eop-eur04.prod.protection.outlook.com
(2603:10a6:209:80:cafe::72) by AM6PR10CA0065.outlook.office365.com
(2603:10a6:209:80::42) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4373.18 via Frontend
Transport; Sat, 31 Jul 2021 17:17:04 +0000
Authentication-Results: spf=pass (sender IP is 46.43.39.111)
smtp.mailfrom=transparencia.be; frameries.be; dkim=none (message not signed)
header.d=none;frameries.be; dmarc=bestguesspass action=none
header.from=transparencia.be;
Received-SPF: Pass (protection.outlook.com: domain of transparencia.be
designates 46.43.39.111 as permitted sender) receiver=protection.outlook.com;
client-ip=46.43.39.111; helo=bittern.ukcod.org.uk;
Received: from bittern.ukcod.org.uk (46.43.39.111) by
VI1EUR04FT064.mail.protection.outlook.com (10.152.28.124) with Microsoft SMTP
Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
15.20.4373.18 via Frontend Transport; Sat, 31 Jul 2021 17:17:03 +0000
Received: from owl.ukcod.org.uk ([46.43.39.108]:60800)
by bittern.ukcod.org.uk with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
(Exim 4.89)
(envelope-from <[FOI #2575 email]>)
id 1m9sbe-0006gO-E7
for [adresse email]; Sat, 31 Jul 2021 18:17:02 +0100
Received: from foibelgium by owl.ukcod.org.uk with local (Exim 4.89)
(envelope-from <[FOI #2575 email]>)
id 1m9sbe-00027x-AW
for [adresse email]; Sat, 31 Jul 2021 18:17:02 +0100
Date: Sat, 31 Jul 2021 18:17:02 +0100
From: "Pascal Lorent, Journaliste au Soir" <[FOI #2575 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_-_Enqu=C3=AAte_du_journal_LeSoir_:_projets_de?=
=?UTF-8?Q?_d=C3=A9lib=C3=A9rations_du_conseil_communal_du_mois_de_juin_et?=
=?UTF-8?Q?_notes_explicatives?=
MIME-Version: 1.0
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Return-Path: [FOI #2575 email]
X-EOPAttributedMessage: 0
X-EOPTenantAttributedMessage: b5b87662-86d0-4531-b666-8680ea2ab60e:0
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 403fc643-df60-4581-25c1-08d9544703e5
X-MS-TrafficTypeDiagnostic: PAXPR02MB7455:
References
Visible links
1. https://go.microsoft.com/fwlink/?LinkId=...
2. https://go.microsoft.com/fwlink/?LinkId=...
3. https://go.microsoft.com/fwlink/?LinkId=...
Chère Commune de Frameries
reconsidération - Concerne : Enquête Vif/Soir - copie des notes explicatives, projets et annexes juin/septembre - transparence des projets de délibérations des conseils communaux
N'ayant toujours reçu aucune réponse à notre demande du 1er juillet, nous vous renvoyons un courriel.
Comme vous le savez, une proposition de décret (n°224), déposée le 13 juillet 2020 et actuellement discutée au Parlement wallon, permettra aux citoyens de consulter en ligne les projets de délibérations avant chaque conseil communal, afin d'augmenter la confiance et la participation dans la vie locale.
Pour l’occasion, Le Vif et Le Soir ont décidé de se lancer ensemble dans un inventaire complet de toutes les communes francophones du pays, pour y répertorier celles qui publient déjà ces projets de délibérations, celles qui ont l’intention de le faire, et celles qui refusent.
Dans ce cadre, merci de répondre aux questions suivantes :
-Pourriez-vous nous transmettre une copie, au format numérique, des projets de délibérations des points inscrits à l’ordre du jour de la séance publique du dernier conseil communal de juin, tels que transmis aux conseillers communaux (il ne s'agit donc pas du PV réalisé a posteriori, mais de sa version provisoire d'avant le conseil). Pour ce même conseil, pourriez-vous transmettre également une copie des notes explicatives (comme définies dans l’article 1 du décret du 31 janvier 2013 ; la CADA a déjà établi le caractère public des notes de synthèse explicatives des points publics, dans son avis numéro 120) pour chacun des points publics précités, ainsi que l’inventaire des annexes faisant partie intégrante de ces délibérations, et les annexes elles-mêmes (voir la décision CADA positive pour les annexes des points publics).
-Au plus tard une semaine avant le prochain conseil communal du mois de septembre, pourriez-vous nous transmettre la même série de documents (projets de délibérations, notes explicatives, inventaire des annexes et annexes elles-mêmes) ?
-Vous engagez-vous à mettre en ligne systématiquement ces documents à l’avenir, au plus tard sept jours avant le conseil communal, pour que les citoyens puissent y avoir accès ?
-Si ces documents sont déjà accessibles à tous les citoyens, pouvez-vous nous transmettre l’adresse URL où ils sont publiés ou nous indiquer si cela est publié via Imio. Et nous préciser depuis quand vous avez mis en place ce système ?
Sans réponse de votre part, nous considérerons que votre commune ne souhaite pas rendre publics les documents demandés.
Merci d’avance pour votre collaboration.
Xavier Counasse (Le Soir)
Thierry Denoël (Le Vif)
David Leloup (Le Vif)
Pascal Lorent (Le Soir)
Eglantine Nyssen (Le Vif)
Cédric Petit (Le Soir)
Your message to [adresse email] couldn't be delivered.
ac.frameries wasn't found at frameries.be.
request-2575-2964810. . . 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: 9/4/2021 9:27:08 PM
Sender Address: [FOI #2575 email]
Recipient [adresse email]
Address:
Demande de reconsidération de Demande au nom de la Liberté
Subject: d'accès à l'information - Enquête du journal LeSoir :
projets de délibérations du conseil communal du mois de
juin et notes explicatives
Error Details
Reported error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient
[adresse email] not found by SMTP address
lookup
DSN generated by: PA4PR02MB6831.eurprd02.prod.outlook.com
Message Hops
HOP TIME FROM TO WITH RELAY
(UTC) TIME
9/4/2021 local (Exim 4.89) (envelope-from
1 9:27:08 foibelgium owl.ukcod.org.uk <[FOI #2575 email]>) *
PM
9/4/2021 esmtps
2 9:27:08 owl.ukcod.org.uk bittern.ukcod.org.uk (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) *
PM (Exim 4.89) (envelope-from
<[FOI #2575 email]>)
9/4/2021 Microsoft SMTP Server (version=TLS1_2,
3 9:27:09 bittern.ukcod.org.uk DB3EUR04FT061.mail.protection.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec
PM
9/4/2021 Microsoft SMTP Server (version=TLS1_2,
4 9:27:10 DB3EUR04FT061.eop-eur04.prod.protection.outlook.com DB6P191CA0007.outlook.office365.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec
PM
9/4/2021 Microsoft SMTP Server (version=TLS1_2,
5 9:27:10 DB6P191CA0007.EURP191.PROD.OUTLOOK.COM PA4PR02MB6831.eurprd02.prod.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
PM
Original Message Headers
Received: from DB6P191CA0007.EURP191.PROD.OUTLOOK.COM (2603:10a6:6:28::17) by
PA4PR02MB6831.eurprd02.prod.outlook.com (2603:10a6:102:f5::22) with Microsoft
SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
15.20.4478.17; Sat, 4 Sep 2021 21:27:10 +0000
Received: from DB3EUR04FT061.eop-eur04.prod.protection.outlook.com
(2603:10a6:6:28:cafe::d9) by DB6P191CA0007.outlook.office365.com
(2603:10a6:6:28::17) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4478.19 via Frontend
Transport; Sat, 4 Sep 2021 21:27:10 +0000
Authentication-Results: spf=pass (sender IP is 46.43.39.111)
smtp.mailfrom=transparencia.be; frameries.be; dkim=none (message not signed)
header.d=none;frameries.be; dmarc=bestguesspass action=none
header.from=transparencia.be;
Received-SPF: Pass (protection.outlook.com: domain of transparencia.be
designates 46.43.39.111 as permitted sender) receiver=protection.outlook.com;
client-ip=46.43.39.111; helo=bittern.ukcod.org.uk;
Received: from bittern.ukcod.org.uk (46.43.39.111) by
DB3EUR04FT061.mail.protection.outlook.com (10.152.24.72) with Microsoft SMTP
Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
15.20.4478.19 via Frontend Transport; Sat, 4 Sep 2021 21:27:09 +0000
Received: from owl.ukcod.org.uk ([46.43.39.108]:50476)
by bittern.ukcod.org.uk with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
(Exim 4.89)
(envelope-from <[FOI #2575 email]>)
id 1mMdBs-0000Mq-Ic
for [adresse email]; Sat, 04 Sep 2021 22:27:08 +0100
Received: from foibelgium by owl.ukcod.org.uk with local (Exim 4.89)
(envelope-from <[FOI #2575 email]>)
id 1mMdBs-0006PP-D2
for [adresse email]; Sat, 04 Sep 2021 22:27:08 +0100
Date: Sat, 04 Sep 2021 22:27:08 +0100
From: "Pascal Lorent, Journaliste au Soir" <[FOI #2575 email]>
To: =?UTF-8?B?TGliZXJ0w6kgZCdhY2PDqHMgw6AgbCdpbmZvcm1hdGlvbiBkZW1hbmRlcyA=?= =?UTF-8?B?w6AgRnJhbWVyaWVz?= <[adresse email]>
Message-ID: <[adresse email]>
Subject: =?UTF-8?Q?Demande_de_reconsid=C3=A9ration_de_Demande_au_nom_de_la?=
=?UTF-8?Q?_Libert=C3=A9_d'acc=C3=A8s_=C3=A0_l'information_-_Enqu=C3=AAte_du?=
=?UTF-8?Q?_journal_LeSoir_:_projets_de_d=C3=A9lib=C3=A9rations_du_conseil?=
=?UTF-8?Q?_communal_du_mois_de_juin_et_notes_explicatives?=
MIME-Version: 1.0
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Return-Path: [FOI #2575 email]
X-EOPAttributedMessage: 0
X-EOPTenantAttributedMessage: b5b87662-86d0-4531-b666-8680ea2ab60e:0
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 0095b71a-9c37-46f2-4383-08d96feac09f
X-MS-TrafficTypeDiagnostic: PA4PR02MB6831:
References
Visible links
1. https://go.microsoft.com/fwlink/?LinkId=...
2. https://go.microsoft.com/fwlink/?LinkId=...
3. https://go.microsoft.com/fwlink/?LinkId=...