Madame, Monsieur,

Au titre du droit d’accès aux documents administratifs, tel que prévu notamment par le Livre III du Code des relations entre le public et l'administration, je sollicite auprès de vous la communication des documents administratifs suivants :

- les notes de frais de déplacements du maire (ainsi que les reçus afférents), sur la période courant de juin 2020 à aujourd'hui.
- les notes de frais de restauration du maire (ainsi que les reçus afférents), sur la période courant de juin 2020 à aujourd'hui.
- les notes de frais de représentation du maire (ainsi que les reçus afférents), sur la période courant de juin 2020 à aujourd'hui.

Je vous rappelle à toutes fins utiles que le Conseil d’État a déjà eu l’occasion de juger que “des notes de frais et reçus de déplacements ainsi que des notes de frais de restauration et reçus de frais de représentation d'élus locaux ou d'agents publics constituent des documents administratifs, communicables à toute personne qui en fait la demande” (Conseil d'État 52521, lecture du 8 février 2023).

Je souhaite recevoir ces documents dans un format numérique, ouvert et réutilisable.

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

Xavier BERNE

Mairie de Montreuil

2 pièces jointes

  • Attachment

    attachment.delivery status

    0K Download

  • Attachment

    Demande au titre du droit d acc s aux documents administratifs Note de frais.txt

    2K Download View as HTML

Your message to [Mairie de Montreuil request email] couldn't be delivered.
delphine.lopes wasn't found at montreuil.fr.
dada+request-44061-4. . . Office 365 delphine.lopes
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: 6/1/2023 11:11:04 AM
Sender Address: [FOI #44061 email]
Recipient Address: [Mairie de Montreuil request email]
Subject: Demande au titre du droit d’accès aux documents
administratifs - Note de frais
Error Details
Error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient
[Mairie de Montreuil request email] not found by SMTP address
lookup
Message rejected PR0P264MB3239.FRAP264.PROD.OUTLOOK.COM
by:
Notification Details
Sent by: PR0P264MB3239.FRAP264.PROD.OUTLOOK.COM

Message Hops
HOP TIME FROM TO WITH RELAY
(UTC) TIME
6/1/2023
1 11:11:04 dadaprod1.madada.fr *
AM
6/1/2023
2 11:11:05 dadaprod1.madada.fr PR2FRA01FT005.mail.protection.outlook.com Microsoft SMTP Server 1 sec
AM
6/1/2023 Microsoft SMTP Server (version=TLS1_2,
3 11:11:05 PR2FRA01FT005.eop-fra01.prod.protection.outlook.com PA7P264CA0125.outlook.office365.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
AM
6/1/2023 Microsoft SMTP Server (version=TLS1_2,
4 11:11:05 PA7P264CA0125.FRAP264.PROD.OUTLOOK.COM PR0P264MB3239.FRAP264.PROD.OUTLOOK.COM cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
AM

Original Message Headers

Received: from PA7P264CA0125.FRAP264.PROD.OUTLOOK.COM (2603:10a6:102:36e::7)
by PR0P264MB3239.FRAP264.PROD.OUTLOOK.COM (2603:10a6:102:1d6::16) with
Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6455.23; Thu, 1 Jun
2023 11:11:05 +0000
Received: from PR2FRA01FT005.eop-fra01.prod.protection.outlook.com
(2603:10a6:102:36e:cafe::a4) by PA7P264CA0125.outlook.office365.com
(2603:10a6:102:36e::7) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6455.22 via Frontend
Transport; Thu, 1 Jun 2023 11:11:05 +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
PR2FRA01FT005.mail.protection.outlook.com (10.152.48.98) with Microsoft SMTP
Server id 15.20.6455.23 via Frontend Transport; Thu, 1 Jun 2023 11:11:05
+0000
Received: by dadaprod1.madada.fr (Postfix, from userid 1001)
id DCFC040CE3; Thu, 1 Jun 2023 13:11:04 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=madada.fr; s=mail;
t=1685617864; bh=vkFJmbtMButca/nyc64zgJZDUz02lI0OYXfifIZheKQ=;
h=Date:From:To:Subject:From;
b=XJFsTfyl59RdZA086EIhsFLc+FsAzA5MHagawcVZ/rb43Bive9ny2BFy1JgWyr39z
UO8u+I5BD5cl07YlaWgkoFg8G4kXy5NW/h8nsThnD9eorPHdd8e7ubCKdgzeKt0PkF
1xyZhpVfLYA67zIjyth9w1x1sDw8uTPtFNqIyBt8=
Date: Thu, 01 Jun 2023 13:11:04 +0200
From: Xavier Berne <[FOI #44061 email]>
To: =?UTF-8?B?ZHJvaXQgZCdhY2PDqHMgw6AgbCdpbmZvcm1hdGlvbiBkZW1hbmRlcyDDoCBN?= =?UTF-8?B?YWlyaWUgZGUgTW9udHJldWls?= <[Mairie de Montreuil 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_-_Note_de_frais?=
MIME-Version: 1.0
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Return-Path: [FOI #44061 email]
X-EOPAttributedMessage: 0
X-EOPTenantAttributedMessage: 2190c5b7-e9a0-4677-8684-bfeb2df56ba9:0
X-MS-PublicTrafficType: Email
X-MS-TrafficTypeDiagnostic: PR2FRA01FT005:EE_|PR0P264MB3239:EE_
X-MS-Office365-Filtering-Correlation-Id: 5a9e993e-9e3f-4657-2ba9-08db6290e46c

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 de Montreuil, en utilisant une nouvelle adresse de contact.

Xavier Berne a posté un commentaire ()

Demande renvoyée à une nouvelle adresse, actualisée.