Répertoire d'informations publiques (RIP)
Madame, Monsieur,
L'article L322-6 du Code des relations entre le public et l'administration (CRPA) oblige depuis 2005 toutes les administrations qui produisent ou détiennent des informations publiques à tenir à la disposition des usagers "un répertoire des principaux documents dans lesquels ces informations figurent". Comme son nom l'indique, ce répertoire est destiné à fournir une liste des principaux documents administratifs en votre possession (documents de marchés publics, statistiques, rapports, codes sources, notes de frais, correspondances, etc.).
Au titre du droit d'accès aux documents administratifs, tel que prévu notamment par le Livre III du CRPA, je sollicite donc auprès de vous la communication de votre répertoire d'informations publiques (RIP).
Sur le fondement du 4° l'article L311-9 du CRPA, je vous prie de bien vouloir répondre à cette demande d'accès par mise en ligne de ce document administratif, afin qu'il profite au plus grand nombre. Cela vous évitera en outre d'avoir à le communiquer individuellement à de potentiels futurs demandeurs.
Notez à ce sujet que le RIP doit être mis en ligne si l'autorité administrative dispose d'un site Internet (R322-7 du CRPA), et dans tous les cas mis à jour chaque année (L322-6).
Je me permets enfin de souligner à toutes fins utiles que la Commission d'accès aux documents administratifs (CADA) a déjà jugé à plusieurs reprises que le répertoire d'informations publiques visé à l'article L322-6 du CRPA constituait "un document administratif communicable à toute personne qui en fait la demande, en application de l'article L311-1 de ce code" (voir avis 20184908 ou 20180157 par exemple).
En vous remerciant par avance de la bienveillance que vous pourrez porter à cette demande,
L'association Open Knowledge France
RNA n°W751219500
Your message to [Mairie - Falleron request email] couldn't be delivered.
secrtariat.direction wasn't found at falleron.fr.
dada+request-41523-b. . . Office 365 secrtariat.direction
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: 5/19/2023 8:28:46 PM
Sender Address: [FOI #41523 email]
Recipient [Mairie - Falleron request email]
Address:
Subject: Demande au titre du droit d’accès aux documents
administratifs - Répertoire d'informations publiques (RIP)
Error Details
Error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient
[Mairie - Falleron request email] not found by SMTP
address lookup
Message rejected PR1P264MB3448.FRAP264.PROD.OUTLOOK.COM
by:
Notification Details
Sent by: PR1P264MB3448.FRAP264.PROD.OUTLOOK.COM
Message Hops
HOP TIME FROM TO WITH RELAY
(UTC) TIME
5/19/2023
1 8:28:46 dadaprod1.madada.fr *
PM
5/19/2023
2 8:28:46 dadaprod1.madada.fr DB5EUR01FT079.mail.protection.outlook.com Microsoft SMTP Server *
PM
5/19/2023 Microsoft SMTP Server (version=TLS1_2,
3 8:28:46 DB5EUR01FT079.eop-EUR01.prod.protection.outlook.com DB6P191CA0003.outlook.office365.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
PM
5/19/2023 Microsoft SMTP Server (version=TLS1_2,
4 8:28:46 DB6P191CA0003.EURP191.PROD.OUTLOOK.COM PR1P264MB3448.FRAP264.PROD.OUTLOOK.COM cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
PM
Original Message Headers
Received: from DB6P191CA0003.EURP191.PROD.OUTLOOK.COM (2603:10a6:6:28::13) by
PR1P264MB3448.FRAP264.PROD.OUTLOOK.COM (2603:10a6:102:184::6) with Microsoft
SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
15.20.6411.21; Fri, 19 May 2023 20:28:46 +0000
Received: from DB5EUR01FT079.eop-EUR01.prod.protection.outlook.com
(2603:10a6:6:28:cafe::2a) by DB6P191CA0003.outlook.office365.com
(2603:10a6:6:28::13) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6411.18 via Frontend
Transport; Fri, 19 May 2023 20:28:46 +0000
Authentication-Results: spf=pass (sender IP is 92.243.18.104)
smtp.mailfrom=madada.fr; dkim=test (signature was verified)
header.d=madada.fr;dmarc=pass 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; pr=C
Received: from dadaprod1.madada.fr (92.243.18.104) by
DB5EUR01FT079.mail.protection.outlook.com (10.152.5.67) with Microsoft SMTP
Server id 15.20.6411.21 via Frontend Transport; Fri, 19 May 2023 20:28:46
+0000
Received: by dadaprod1.madada.fr (Postfix, from userid 1001)
id 42E6C44315; Fri, 19 May 2023 22:28:46 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=madada.fr; s=mail;
t=1684528126; bh=CJS3vikAdnWBh+AUyFhqEjry12glqufizEDbmA9V/6E=;
h=Date:From:To:Subject:From;
b=MfLawcfvbKdqJYXOYodtuj5ietZSsw3LmnnrxW2GARXz5+/ajhMtChyVFIz3QJBq3
+9naTsVde4E1h2sKCSWqJmvs1mDQ2/OirxcbFVo0R8iMq9WGbX+VZiXEORa9nSAP/P
Dd92/BM4Irv96PDHscKuTKVurj6cycNxaTH4Qxtg=
Date: Fri, 19 May 2023 22:28:46 +0200
From: Open Knowledge France <[FOI #41523 email]>
To: =?UTF-8?B?ZHJvaXQgZCdhY2PDqHMgw6AgbCdpbmZvcm1hdGlvbiBkZW1hbmRlcyDDoCBN?= =?UTF-8?B?YWlyaWUgLSBGYWxsZXJvbg==?= <[Mairie - Falleron request 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_-_R=C3=A9pertoire_d'informations_publiq?=
=?UTF-8?Q?ues_=28RIP=29?=
MIME-Version: 1.0
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Return-Path: [FOI #41523 email]
X-EOPAttributedMessage: 0
X-EOPTenantAttributedMessage: fce0cde7-4aa9-4eac-8cef-2b55b108d995:0
X-MS-PublicTrafficType: Email
X-MS-TrafficTypeDiagnostic: DB5EUR01FT079:EE_|PR1P264MB3448:EE_
X-MS-Office365-Filtering-Correlation-Id: 792e4a78-94f6-44f7-342f-08db58a7a5a4
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 - Falleron, en utilisant une nouvelle adresse de contact.