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 - Brétigny-sur-Orge request email] couldn't be delivered.
 f.vanhoenacker wasn't found at mairie-bretigny91.fr.
 dada+request-42404-b. . . Office 365 f.vanhoenacker
 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/20/2023 11:14:16 AM
 Sender Address: [FOI #42404 email]
 Recipient [Mairie - Brétigny-sur-Orge 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 - Brétigny-sur-Orge request email] not found by SMTP
 address lookup
 Message rejected PAZP264MB2335.FRAP264.PROD.OUTLOOK.COM
 by:
 Notification Details
 Sent by: PAZP264MB2335.FRAP264.PROD.OUTLOOK.COM
Message Hops
HOP TIME FROM TO WITH RELAY
 (UTC) TIME
 5/20/2023
1 11:14:16 dadaprod1.madada.fr *
 AM
 5/20/2023
2 11:14:16 dadaprod1.madada.fr PR2FRA01FT011.mail.protection.outlook.com Microsoft SMTP Server *
 AM
 5/20/2023 Microsoft SMTP Server (version=TLS1_2,
3 11:14:17 PR2FRA01FT011.eop-fra01.prod.protection.outlook.com PR2P264CA0022.outlook.office365.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec
 AM
 5/20/2023 Microsoft SMTP Server (version=TLS1_2,
4 11:14:17 PR2P264CA0022.FRAP264.PROD.OUTLOOK.COM PAZP264MB2335.FRAP264.PROD.OUTLOOK.COM cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
 AM
Original Message Headers
 Received: from PR2P264CA0022.FRAP264.PROD.OUTLOOK.COM (2603:10a6:101::34) by
 PAZP264MB2335.FRAP264.PROD.OUTLOOK.COM (2603:10a6:102:1f1::16) with Microsoft
 SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
 15.20.6411.22; Sat, 20 May 2023 11:14:17 +0000
 Received: from PR2FRA01FT011.eop-fra01.prod.protection.outlook.com
 (2603:10a6:101:0:cafe::da) by PR2P264CA0022.outlook.office365.com
 (2603:10a6:101::34) with Microsoft SMTP Server (version=TLS1_2,
 cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6411.24 via Frontend
 Transport; Sat, 20 May 2023 11:14:17 +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
 PR2FRA01FT011.mail.protection.outlook.com (10.152.48.104) with Microsoft SMTP
 Server id 15.20.6433.7 via Frontend Transport; Sat, 20 May 2023 11:14:16
 +0000
 Received: by dadaprod1.madada.fr (Postfix, from userid 1001)
 id 78F3B442AD; Sat, 20 May 2023 13:14:16 +0200 (CEST)
 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=madada.fr; s=mail;
 t=1684581256; bh=R/vXCRRO/y2675Ce5CJac5oD1aJ5ciEKyk22ULPE4nQ=;
 h=Date:From:To:Subject:From;
 b=Isb87BHUaTW2xvNgybUc1jMlQ37nc+KJsLZIhTxDgOapdo34lzjj0aSbP9MznU/bd
 LPZT/5GgMP6yrrKUlr2F0t9GuuE1Kju4WFnKK8pTVE7PH6wWF9m8YtdG/6rXOnxQ6N
 jRv/vmjvk5EfEaeUqZV1g1r43iltk2CTM3YqTc+0=
 Date: Sat, 20 May 2023 13:14:16 +0200
 From: Open Knowledge France <[FOI #42404 email]>
 To: =?UTF-8?B?ZHJvaXQgZCdhY2PDqHMgw6AgbCdpbmZvcm1hdGlvbiBkZW1hbmRlcyDDoCBN?= =?UTF-8?B?YWlyaWUgLSBCcsOpdGlnbnktc3VyLU9yZ2U=?= <[Mairie - Brétigny-sur-Orge 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 #42404 email]
 X-EOPAttributedMessage: 0
 X-EOPTenantAttributedMessage: 33aeca05-a225-4f4b-a553-c8d64f367ca5:0
 X-MS-PublicTrafficType: Email
 X-MS-TrafficTypeDiagnostic: PR2FRA01FT011:EE_|PAZP264MB2335:EE_
 X-MS-Office365-Filtering-Correlation-Id: cca0bd28-21c2-4666-c81a-08db592359a9
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 - Brétigny-sur-Orge, en utilisant une nouvelle adresse de contact.
Madame, Monsieur,
 Cette boîte email est dorénavant fermée. Afin d’améliorer la qualité et la
 rapidité des réponses adressées aux Brétignolais, elle est remplacée par
 une nouvelle plateforme « Espace Citoyens » mise en place par la Ville. 
 Nous vous invitons à réaliser votre demande directement sur celle-ci au
 lien suivant : [1]Brétigny-sur-Orge - Accueil (espace-citoyens.net). 
 Pour les demandes institutionnelles, nous vous invitons à contacter le
 Cabinet du Maire : [adresse email].  
En vous remerciant par avance pour votre compréhension,
Service Proximité
References
 Visible links
 1. https://www.espace-citoyens.net/bretigny...
Nous avons envoyé à nouveau la demande à Mairie - Brétigny-sur-Orge, en utilisant une nouvelle adresse de contact.

