Demande de communication des notes de frais du Maire

La CADA a été saisie pour cette demande. À notre connaissance, aucun avis n'a été rendu à ce jour. La CADA a normalement un mois à compter de la date de la saisine pour émettre un avis.

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 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 souhaite recevoir ces documents sous forme électronique, dans un standard ouvert, aisément réutilisable et exploitable par un système de traitement automatisé, comme le prévoit l’article L300-4 du Code des relations entre le public et l’administration.

Comme l’article L311-2 du code précité le prévoit lorsque le demandeur a mal identifié celui qui est susceptible de répondre à sa requête, je vous prie de bien vouloir transmettre ma demande au service qui détient les documents demandés si tel est le cas.

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

Guillaume Leroy,
Président de l'association Transparence Citoyenne

Mairie - Chevigny-Saint-Sauveur

2 pièces jointes

  • Attachment

    attachment.delivery status

    0K Download

  • Attachment

    Demande au titre du droit d acc s aux documents administratifs Demande de communication des notes de frais du Maire.txt

    3K Download View as HTML

Your message to [Mairie - Chevigny-Saint-Sauveur request email] couldn't be
delivered.
mairie.cada wasn't found at chevigny-saint-sauveur.fr.
dada+request-45650-d. . . Office 365 mairie.cada
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/28/2024 1:25:49 PM
Sender Address: [FOI #45650 email]
Recipient [Mairie - Chevigny-Saint-Sauveur request email]
Address:
Demande au titre du droit d’accès aux documents
Subject: administratifs - Demande de communication des notes de
frais du Maire
Error Details
Error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient
[Mairie - Chevigny-Saint-Sauveur request email] not found by SMTP
address lookup
Message rejected PAZP264MB2575.FRAP264.PROD.OUTLOOK.COM
by:
Notification Details
Sent by: PAZP264MB2575.FRAP264.PROD.OUTLOOK.COM

Message Hops
HOP TIME FROM TO WITH RELAY
(UTC) TIME
3/28/2024
1 1:25:50 dadaprod1.madada.fr 1 sec
PM
3/28/2024
2 1:25:52 dadaprod1.madada.fr PA3PEPF000089B8.mail.protection.outlook.com Microsoft SMTP Server 2 sec
PM
3/28/2024 Microsoft SMTP Server (version=TLS1_2,
3 1:25:52 PA3PEPF000089B8.FRAP264.PROD.OUTLOOK.COM PR1P264CA0119.outlook.office365.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
PM
3/28/2024 Microsoft SMTP Server (version=TLS1_2,
4 1:25:52 PR1P264CA0119.FRAP264.PROD.OUTLOOK.COM PAZP264MB2575.FRAP264.PROD.OUTLOOK.COM cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
PM

Original Message Headers

Received: from PR1P264CA0119.FRAP264.PROD.OUTLOOK.COM (2603:10a6:102:2cd::13)
by PAZP264MB2575.FRAP264.PROD.OUTLOOK.COM (2603:10a6:102:1f1::5) with
Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.7409.32; Thu, 28 Mar
2024 13:25:52 +0000
Received: from PA3PEPF000089B8.FRAP264.PROD.OUTLOOK.COM
(2603:10a6:102:2cd:cafe::42) by PR1P264CA0119.outlook.office365.com
(2603:10a6:102:2cd::13) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.7409.13 via Frontend
Transport; Thu, 28 Mar 2024 13:25:52 +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
PA3PEPF000089B8.mail.protection.outlook.com (10.167.242.20) with Microsoft
SMTP Server id 15.20.7409.10 via Frontend Transport; Thu, 28 Mar 2024
13:25:52 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=madada.fr; s=mail;
t=1711632351; bh=Owi6q8oGvdvYArTmBMLPLMeZvuAOJnyG5GgOLgAEfuY=;
h=Date:From:To:Subject:From;
b=nSr37yWmtQWgX/jycpKJ1fOAHafQPhfT86ruScPCI0KLbA3C/njKAeYM68QQxFnwA
zciCsZSFo7uZWDRuDkVuEYPrPORK6RmFUmA3YgCR9ZdtHAd/XrP9pFomPb4tLy2O5b
JJPxAsqzKLKRM7Ekl7nzVJiobUAIqm5I4BkVsWmU=
Received: by dadaprod1.madada.fr (Postfix, from userid 1001)
id 578CD44D45; Thu, 28 Mar 2024 14:25:50 +0100 (CET)
Date: Thu, 28 Mar 2024 14:25:49 +0100
From: Association Transparence Citoyenne <[FOI #45650 email]>
To: =?UTF-8?B?ZHJvaXQgZCdhY2PDqHMgw6AgbCdpbmZvcm1hdGlvbiBkZW1hbmRlcyDDoCBN?= =?UTF-8?B?YWlyaWUgLSBDaGV2aWdueS1TYWludC1TYXV2ZXVy?= <[Mairie - Chevigny-Saint-Sauveur 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_-_Demande_de_communication_des_notes_de?=
=?UTF-8?Q?_frais_du_Maire?=
MIME-Version: 1.0
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Return-Path: [FOI #45650 email]
X-EOPAttributedMessage: 0
X-EOPTenantAttributedMessage: 513121e4-0520-4203-9c1e-8c0c01fcefc2:0
X-MS-PublicTrafficType: Email
X-MS-TrafficTypeDiagnostic: PA3PEPF000089B8:EE_|PAZP264MB2575:EE_
X-MS-Office365-Filtering-Correlation-Id: 02bc5079-3cbd-48ef-2261-08dc4f2a972a

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