Demande justificatifs note de frais
Cher/Chère Mairie - Houilles,
En application de la loi n° 78-575 du 17 juillet 1978 relative aux documents administratifs, je souhaite recevoir communication des documents administratifs suivants: l'ensemble des justificatifs des note de frais du maire M Chambon ( restauration, déplacement et autres) depuis les dernières élections de 2020.
Je souhaite recevoir ces documents dans un format numérique, ouvert et réutilisable. Pour ce faire, veuillez m’indiquer leur adresse de téléchargement ou me les envoyer en pièce jointe.
Comme le livre III du code des relations entre le public et l’administration 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.
Thibaut SECHET
Your message to [Mairie - Houilles request email] couldn't be delivered.
delphine.kerleau wasn't found at ville-houilles.fr.
dada+request-44046-8. . . Office 365 delphine.kerleau
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 10:41:10 AM
Sender Address: [FOI #44046 email]
Recipient [Mairie - Houilles request email]
Address:
Subject: Demande au titre du droit d’accès aux documents
administratifs - Demande justificatifs note de frais
Error Details
Error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient
[Mairie - Houilles request email] not found by SMTP
address lookup
Message rejected MR1P264MB2450.FRAP264.PROD.OUTLOOK.COM
by:
Notification Details
Sent by: MR1P264MB2450.FRAP264.PROD.OUTLOOK.COM
Message Hops
HOP TIME FROM TO WITH RELAY
(UTC) TIME
6/1/2023
1 10:41:10 dadaprod1.madada.fr *
AM
6/1/2023
2 10:41:10 dadaprod1.madada.fr PR2FRA01FT003.mail.protection.outlook.com Microsoft SMTP Server *
AM
6/1/2023 Microsoft SMTP Server (version=TLS1_2,
3 10:41:11 PR2FRA01FT003.eop-fra01.prod.protection.outlook.com PR1P264CA0144.outlook.office365.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec
AM
6/1/2023 Microsoft SMTP Server (version=TLS1_2,
4 10:41:11 PR1P264CA0144.FRAP264.PROD.OUTLOOK.COM MR1P264MB2450.FRAP264.PROD.OUTLOOK.COM cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
AM
Original Message Headers
Received: from PR1P264CA0144.FRAP264.PROD.OUTLOOK.COM (2603:10a6:102:346::8)
by MR1P264MB2450.FRAP264.PROD.OUTLOOK.COM (2603:10a6:501:33::13) 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 10:41:11 +0000
Received: from PR2FRA01FT003.eop-fra01.prod.protection.outlook.com
(2603:10a6:102:346:cafe::40) by PR1P264CA0144.outlook.office365.com
(2603:10a6:102:346::8) 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 10:41:11 +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
PR2FRA01FT003.mail.protection.outlook.com (10.152.48.96) with Microsoft SMTP
Server id 15.20.6455.23 via Frontend Transport; Thu, 1 Jun 2023 10:41:10
+0000
Received: by dadaprod1.madada.fr (Postfix, from userid 1001)
id B7E6140CA3; Thu, 1 Jun 2023 12:41:10 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=madada.fr; s=mail;
t=1685616070; bh=UCh13TTAx2O/pJOot8vPUUrgkZQXcYaq1TXn43U3Mlw=;
h=Date:From:To:Subject:From;
b=ZxhP8f2ZK5Wdgjw/5uVA0ZUm5PAfcAUpK08HJQeFOkbo0pFEzcwqzQSO0EltQLewF
0x3OlD/BUFGep97VZ5DtGusGK0d2wIUoeJuVLh/N8VIIgZWaeX7hXhLaN/uB9BFGZJ
ghtaIjgoNNuyM/LHbKNZVmR0GYandQ7599iQ+jZ8=
Date: Thu, 01 Jun 2023 12:41:10 +0200
From: ST <[FOI #44046 email]>
To: =?UTF-8?B?ZHJvaXQgZCdhY2PDqHMgw6AgbCdpbmZvcm1hdGlvbiBkZW1hbmRlcyDDoCBN?= =?UTF-8?B?YWlyaWUgLSBIb3VpbGxlcw==?= <[Mairie - Houilles 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_justificatifs_note_de_frais?=
MIME-Version: 1.0
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Return-Path: [FOI #44046 email]
X-EOPAttributedMessage: 0
X-EOPTenantAttributedMessage: 3e54e5ec-ec0c-472c-b790-78ae8df074d5:0
X-MS-PublicTrafficType: Email
X-MS-TrafficTypeDiagnostic: PR2FRA01FT003:EE_|MR1P264MB2450:EE_
X-MS-Office365-Filtering-Correlation-Id: b0100428-079f-4306-af57-08db628cb709
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 - Houilles, en utilisant une nouvelle adresse de contact.
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 :
-
-
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.
ST
Bonjour,
Pour identifier le service correspondant à votre question, il serait bien de savoir de qu'elle document il s’agit.
Veuillez agréer Monsieur, Madame mes sincères salutations.
-----Message d'origine-----
De : ST <[FOI #44046 email]>
Envoyé : jeudi 10 août 2023 14:04
À : contactVille <[adresse email]>
Objet : Demande de recours de Demande au titre du droit d’accès aux documents administratifs - Demande justificatifs note de frais
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 :
-
-
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.
ST
-----Original Message-----
Your message to [Mairie - Houilles request email] couldn't be delivered.
delphine.kerleau wasn't found at ville-houilles.fr.
dada+request-44046-8. . . Office 365 delphine.kerleau 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 10:41:10 AM
Sender Address: [FOI #44046 email]
Recipient [Mairie - Houilles request email]
Address:
Subject: Demande au titre du droit d’accès aux documents administratifs - Demande justificatifs note de frais Error Details
Error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient [Mairie - Houilles request email] not found by SMTP address lookup Message rejected MR1P264MB2450.FRAP264.PROD.OUTLOOK.COM
by:
Notification Details
Sent by: MR1P264MB2450.FRAP264.PROD.OUTLOOK.COM
Message Hops
HOP TIME FROM TO WITH RELAY
(UTC) TIME
6/1/2023
1 10:41:10 dadaprod1.madada.fr *
AM
6/1/2023
2 10:41:10 dadaprod1.madada.fr PR2FRA01FT003.mail.protection.outlook.com Microsoft SMTP Server * AM
6/1/2023 Microsoft SMTP Server (version=TLS1_2,
3 10:41:11 PR2FRA01FT003.eop-fra01.prod.protection.outlook.com PR1P264CA0144.outlook.office365.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec AM
6/1/2023 Microsoft SMTP Server (version=TLS1_2,
4 10:41:11 PR1P264CA0144.FRAP264.PROD.OUTLOOK.COM MR1P264MB2450.FRAP264.PROD.OUTLOOK.COM cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) * AM
Original Message Headers
Received: from PR1P264CA0144.FRAP264.PROD.OUTLOOK.COM (2603:10a6:102:346::8) by MR1P264MB2450.FRAP264.PROD.OUTLOOK.COM (2603:10a6:501:33::13) 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 10:41:11 +0000
Received: from PR2FRA01FT003.eop-fra01.prod.protection.outlook.com
(2603:10a6:102:346:cafe::40) by PR1P264CA0144.outlook.office365.com
(2603:10a6:102:346::8) 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 10:41:11 +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 PR2FRA01FT003.mail.protection.outlook.com (10.152.48.96) with Microsoft SMTP Server id 15.20.6455.23 via Frontend Transport; Thu, 1 Jun 2023 10:41:10
+0000
Received: by dadaprod1.madada.fr (Postfix, from userid 1001) id B7E6140CA3; Thu, 1 Jun 2023 12:41:10 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=madada.fr; s=mail; t=1685616070; bh=UCh13TTAx2O/pJOot8vPUUrgkZQXcYaq1TXn43U3Mlw=;
h=Date:From:To:Subject:From;
b=ZxhP8f2ZK5Wdgjw/5uVA0ZUm5PAfcAUpK08HJQeFOkbo0pFEzcwqzQSO0EltQLewF
0x3OlD/BUFGep97VZ5DtGusGK0d2wIUoeJuVLh/N8VIIgZWaeX7hXhLaN/uB9BFGZJ
ghtaIjgoNNuyM/LHbKNZVmR0GYandQ7599iQ+jZ8=
Date: Thu, 01 Jun 2023 12:41:10 +0200
From: ST <[FOI #44046 email]>
To: =?UTF-8?B?ZHJvaXQgZCdhY2PDqHMgw6AgbCdpbmZvcm1hdGlvbiBkZW1hbmRlcyDDoCBN?= =?UTF-8?B?YWlyaWUgLSBIb3VpbGxlcw==?= <[Mairie - Houilles 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_justificatifs_note_de_frais?=
MIME-Version: 1.0
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Return-Path: [FOI #44046 email]
X-EOPAttributedMessage: 0
X-EOPTenantAttributedMessage: 3e54e5ec-ec0c-472c-b790-78ae8df074d5:0
X-MS-PublicTrafficType: Email
X-MS-TrafficTypeDiagnostic: PR2FRA01FT003:EE_|MR1P264MB2450:EE_
X-MS-Office365-Filtering-Correlation-Id: b0100428-079f-4306-af57-08db628cb709
References
Visible links
1. https://go.microsoft.com/fwlink/?LinkId=...
2. https://go.microsoft.com/fwlink/?LinkId=...
3. https://go.microsoft.com/fwlink/?LinkId=...
-------------------------------------------------------------------
Le code des relations entre le public et l’administration fixe les conditions dans lesquels les documents administratifs sont communiqués aux citoyens. En particulier, dès qu’un citoyen en fait la demande, tout document administratif communicable doit être mis en ligne de façon à être accessible à chacun.e (article L311-9), et ce dans leur version mise à jour (article L312-1-1).
Merci d'utiliser cette adresse email pour toutes les réponses à cette demande :
[FOI #44046 email]
Attention : Ce message et les réponses/documents que vous écrivez seront publiés en libre accès sur internet. Notre politique en matière de confidentialité et de droits d'auteur :
https://doc.madada.fr/prada/
Notez bien que dans certains cas, la publication des demandes et des réponses sera retardée.
Si vous trouvez ce service utile en tant que plateforme d'accès à l'information, pouvez-vous demander à votre webmaster de mettre un lien vers notre site à partir de la page "droit d'accès à l'information" de votre organisation ?
-------------------------------------------------------------------