Your message to [Philippeville request email] couldn't be
delivered.
andre.demartin wasn't found at commune-philippeville.be.
request-5315-3dd0e66. . . Office 365 andre.demartin
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: 8/6/2024 8:35:27 PM
Sender Address: [FOI #5315 email]
Recipient [Philippeville request email]
Address:
Demande au nom de la Liberté d'accès à l'information -
Subject: Analyse comparative des finances de la commune avec son
cluster, fournie par Belfius
Error Details
Error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient
[Philippeville request email] not found by SMTP
address lookup
Message rejected AS8PR05MB8609.eurprd05.prod.outlook.com
by:
Notification Details
Sent by: AS8PR05MB8609.eurprd05.prod.outlook.com

Message Hops
HOP TIME FROM TO WITH RELAY
(UTC) TIME
8/6/2024 local (Exim 4.94.2) (envelope-from
1 8:35:27 foibelgium mstr001sova.srv.mysociety.org <[FOI #5315 email]>) *
PM
8/6/2024 esmtps (TLS1.3) tls
2 8:35:27 mstr001sova.srv.mysociety.org mslb001sova.srv.mysociety.org TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim *
PM 4.94.2) (envelope-from
<[FOI #5315 email]>)
8/6/2024 Microsoft SMTP Server (version=TLS1_3,
3 8:35:28 mslb001sova.srv.mysociety.org AM4PEPF00027A5E.mail.protection.outlook.com cipher=TLS_AES_256_GCM_SHA384) 1 sec
PM
8/6/2024 Microsoft SMTP Server (version=TLS1_2,
4 8:35:28 AM4PEPF00027A5E.eurprd04.prod.outlook.com AM0PR01CA0134.outlook.office365.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
PM
8/6/2024 Microsoft SMTP Server (version=TLS1_2,
5 8:35:29 AM0PR01CA0134.eurprd01.prod.exchangelabs.com AS8PR05MB8609.eurprd05.prod.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec
PM

Original Message Headers

Received: from AM0PR01CA0134.eurprd01.prod.exchangelabs.com
(2603:10a6:208:168::39) by AS8PR05MB8609.eurprd05.prod.outlook.com
(2603:10a6:20b:344::12) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.7762.23; Tue, 6 Aug
2024 20:35:29 +0000
Received: from AM4PEPF00027A5E.eurprd04.prod.outlook.com
(2603:10a6:208:168:cafe::84) by AM0PR01CA0134.outlook.office365.com
(2603:10a6:208:168::39) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.7828.27 via Frontend
Transport; Tue, 6 Aug 2024 20:35:28 +0000
Authentication-Results: spf=pass (sender IP is 93.93.128.121)
smtp.mailfrom=transparencia.be; dkim=pass (signature was verified)
header.d=transparencia.be;dmarc=pass action=none
header.from=transparencia.be;
Received-SPF: Pass (protection.outlook.com: domain of transparencia.be
designates 93.93.128.121 as permitted sender)
receiver=protection.outlook.com; client-ip=93.93.128.121;
helo=mslb001sova.srv.mysociety.org; pr=C
Received: from mslb001sova.srv.mysociety.org (93.93.128.121) by
AM4PEPF00027A5E.mail.protection.outlook.com (10.167.16.72) with Microsoft
SMTP Server (version=TLS1_3, cipher=TLS_AES_256_GCM_SHA384) id 15.20.7849.8
via Frontend Transport; Tue, 6 Aug 2024 20:35:28 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;
d=transparencia.be; s=2020a.mysociety; h=Content-Transfer-Encoding:
Content-Type:Mime-Version:Subject:Message-ID:To:From:Date:Sender:Reply-To:Cc:
Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender:
Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id:
List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive;
bh=0+CKfP+C34y/7iyigW/WQclH3EVZfT/X8wsWYF+Uyzg=; b=Bx6oozZS3AhiQDx7l2EJSU8Aux
MP2aY6H1vB6RRh9S/uGkwj5OI8yKr2q+fNLo4P6uy9oa2h1cAUmo2S/w9EQhjVGI4rs2a3fgTVb8l
xkHNvmLXa4zjatxYSEaVfB68c4yA5kzx7eoNSGIgLlRFa5sDMX8bCaQo/9nkYzu0E8eA3vdst25fw
G2R9f+A+J7/UCOFBL4etS8Q283zJ0vOj0zLWySA2Fv+veukHUyzvC+lkVNOl/7zH/b35DBmZZd+jh
M/BGNVMcxAyorN+AqigIMJ/C43AZimx1h5OnxF+6IH6ESxdkp7095d7LMBwbPlKhCnKSzi/Yjh+TZ
477blvjw==;
Received: from mstr001sova.srv.mysociety.org ([2a00:1098:80:3b::b:1]:48866)
by mslb001sova.srv.mysociety.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
(Exim 4.94.2)
(envelope-from <[FOI #5315 email]>)
id 1sbQtz-007RRD-Oz
for [Philippeville request email]; Tue, 06 Aug 2024 20:35:27 +0000
Received: from foibelgium by mstr001sova.srv.mysociety.org with local (Exim 4.94.2)
(envelope-from <[FOI #5315 email]>)
id 1sbQtz-0039jH-CU
for [Philippeville request email]; Tue, 06 Aug 2024 20:35:27 +0000
Date: Tue, 06 Aug 2024 20:35:27 +0000
From: =?UTF-8?B?U2XDr2RvZmYgTWljaGHDq2w=?= <[FOI #5315 email]>
To: =?UTF-8?B?TGliZXJ0w6kgZCdhY2PDqHMgw6AgbCdpbmZvcm1hdGlvbiBkZW1hbmRlcyA=?= =?UTF-8?B?w6AgUGhpbGlwcGV2aWxsZQ==?= <[Philippeville request email]>
Message-ID: <[adresse email]>
Subject: =?UTF-8?Q?Demande_au_nom_de_la_Libert=C3=A9_d'acc=C3=A8s_=C3=A0?=
=?UTF-8?Q?_l'information_-_Analyse_comparative_des_finances_de_la_commune?=
=?UTF-8?Q?_avec_son_cluster,_fournie_par_Belfius?=
MIME-Version: 1.0
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Return-Path: [FOI #5315 email]
X-EOPAttributedMessage: 0
X-EOPTenantAttributedMessage: 42c660e4-ea81-49ac-8d21-f8761016b97f:0
X-MS-PublicTrafficType: Email
X-MS-TrafficTypeDiagnostic: AM4PEPF00027A5E:EE_|AS8PR05MB8609:EE_
X-MS-Office365-Filtering-Correlation-Id: 35e29a6b-1403-4a26-72e1-08dcb6574f0d

References

Visible links
1. https://go.microsoft.com/fwlink/?LinkId=...
2. https://go.microsoft.com/fwlink/?LinkId=...
3. https://go.microsoft.com/fwlink/?LinkId=...

Your message to [Philippeville request email] couldn't be
delivered.
andre.demartin wasn't found at commune-philippeville.be.
request-5315-3dd0e66. . . Office 365 andre.demartin
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: 8/8/2024 10:51:17 AM
Sender Address: [FOI #5315 email]
Recipient [Philippeville request email]
Address:
Demande au nom de la Liberté d'accès à l'information -
Subject: Analyse comparative des finances de la commune avec son
cluster, fournie par Belfius
Error Details
Error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient
[Philippeville request email] not found by SMTP
address lookup
Message rejected AM9PR05MB8860.eurprd05.prod.outlook.com
by:
Notification Details
Sent by: AM9PR05MB8860.eurprd05.prod.outlook.com

Message Hops
HOP TIME FROM TO WITH RELAY
(UTC) TIME
8/8/2024 local (Exim 4.94.2) (envelope-from
1 10:51:17 foibelgium mstr001sova.srv.mysociety.org <[FOI #5315 email]>) *
AM
8/8/2024 esmtps (TLS1.3) tls
2 10:51:17 mstr001sova.srv.mysociety.org mslb001hexa.srv.mysociety.org TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim *
AM 4.94.2) (envelope-from
<[FOI #5315 email]>)
8/8/2024 Microsoft SMTP Server (version=TLS1_3,
3 10:51:18 mslb001hexa.srv.mysociety.org AM4PEPF00025F9C.mail.protection.outlook.com cipher=TLS_AES_256_GCM_SHA384) 1 sec
AM
8/8/2024 Microsoft SMTP Server (version=TLS1_2,
4 10:51:19 AM4PEPF00025F9C.EURPRD83.prod.outlook.com AS9P194CA0025.outlook.office365.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec
AM
8/8/2024 Microsoft SMTP Server (version=TLS1_2,
5 10:51:19 AS9P194CA0025.EURP194.PROD.OUTLOOK.COM AM9PR05MB8860.eurprd05.prod.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
AM

Original Message Headers

Received: from AS9P194CA0025.EURP194.PROD.OUTLOOK.COM (2603:10a6:20b:46d::15)
by AM9PR05MB8860.eurprd05.prod.outlook.com (2603:10a6:20b:43b::5) with
Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.7849.13; Thu, 8 Aug
2024 10:51:19 +0000
Received: from AM4PEPF00025F9C.EURPRD83.prod.outlook.com
(2603:10a6:20b:46d:cafe::fe) by AS9P194CA0025.outlook.office365.com
(2603:10a6:20b:46d::15) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.7849.14 via Frontend
Transport; Thu, 8 Aug 2024 10:51:19 +0000
Authentication-Results: spf=pass (sender IP is 93.93.130.118)
smtp.mailfrom=transparencia.be; dkim=pass (signature was verified)
header.d=transparencia.be;dmarc=pass action=none
header.from=transparencia.be;
Received-SPF: Pass (protection.outlook.com: domain of transparencia.be
designates 93.93.130.118 as permitted sender)
receiver=protection.outlook.com; client-ip=93.93.130.118;
helo=mslb001hexa.srv.mysociety.org; pr=C
Received: from mslb001hexa.srv.mysociety.org (93.93.130.118) by
AM4PEPF00025F9C.mail.protection.outlook.com (10.167.16.11) with Microsoft
SMTP Server (version=TLS1_3, cipher=TLS_AES_256_GCM_SHA384) id 15.20.7875.2
via Frontend Transport; Thu, 8 Aug 2024 10:51:18 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;
d=transparencia.be; s=2020a.mysociety; h=Content-Transfer-Encoding:
Content-Type:Mime-Version:Subject:Message-ID:To:From:Date:Sender:Reply-To:Cc:
Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender:
Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id:
List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive;
bh=0+CKfP+C34y/7iyigW/WQclH3EVZfT/X8wsWYF+Uyzg=; b=EWQpmUG5ud9RhPFKaOfNwkMykb
Qy7j9hOHauaoO7LOdU0xSIcnIKIOO9VKGbpuK0WXVROfxb62erVoMzxaLr60VQC9Xy3AVxQwLK62t
1M8Go2zEoBhRJXzJmF6vw8EstA5SWZ/lbKdpFDv5Ft63YVIxpdPtMB6tUALpGdxyz6ZLPWo5EGLPs
Z6IcJXrAVrn5x5BNT781Q0S+OVzlcH5dRkFkWSlSygGVQLN2R0BgaJp45DjcKyEm1/Fns9aNNl3hG
Y7KIPo6D3ajZbf1YcMt2cs0weyg7QGTm+qjhhr3rd5MauXLQR7Jrd/AwquUmMWMRrh7wm77RpD+oZ
hBlIm9QA==;
Received: from mstr001sova.srv.mysociety.org ([2a00:1098:80:3b::b:1]:33652)
by mslb001hexa.srv.mysociety.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
(Exim 4.94.2)
(envelope-from <[FOI #5315 email]>)
id 1sc0jl-00AGzI-KH
for [Philippeville request email]; Thu, 08 Aug 2024 10:51:17 +0000
Received: from foibelgium by mstr001sova.srv.mysociety.org with local (Exim 4.94.2)
(envelope-from <[FOI #5315 email]>)
id 1sc0jl-00554d-7s
for [Philippeville request email]; Thu, 08 Aug 2024 10:51:17 +0000
Date: Thu, 08 Aug 2024 10:51:17 +0000
From: =?UTF-8?B?U2XDr2RvZmYgTWljaGHDq2w=?= <[FOI #5315 email]>
To: =?UTF-8?B?TGliZXJ0w6kgZCdhY2PDqHMgw6AgbCdpbmZvcm1hdGlvbiBkZW1hbmRlcyA=?= =?UTF-8?B?w6AgUGhpbGlwcGV2aWxsZQ==?= <[Philippeville request email]>
Message-ID: <[adresse email]>
Subject: =?UTF-8?Q?Demande_au_nom_de_la_Libert=C3=A9_d'acc=C3=A8s_=C3=A0?=
=?UTF-8?Q?_l'information_-_Analyse_comparative_des_finances_de_la_commune?=
=?UTF-8?Q?_avec_son_cluster,_fournie_par_Belfius?=
MIME-Version: 1.0
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Return-Path: [FOI #5315 email]
X-EOPAttributedMessage: 0
X-EOPTenantAttributedMessage: 42c660e4-ea81-49ac-8d21-f8761016b97f:0
X-MS-PublicTrafficType: Email
X-MS-TrafficTypeDiagnostic: AM4PEPF00025F9C:EE_|AM9PR05MB8860:EE_
X-MS-Office365-Filtering-Correlation-Id: 9f4fa0e8-2fd2-4cff-3be0-08dcb7980870

References

Visible links
1. https://go.microsoft.com/fwlink/?LinkId=...
2. https://go.microsoft.com/fwlink/?LinkId=...
3. https://go.microsoft.com/fwlink/?LinkId=...

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

[Philippeville request email]
host mail.philippeville.be [188.130.44.60]
SMTP error from remote mail server after RCPT TO:<[Philippeville request email]>:
550 5.1.1 <[Philippeville request email]>: Recipient address rejected:
User unknown in virtual mailbox table

Monsieur Seïdoff,

Vous trouverez en pièce jointe le document sollicité.

Cordialement,

Caroline Corman
Directrice générale ff
Ville de Philippeville

071/66.00.64

[Philippeville request email]

www.philippeville.be

Place d'Armes 12, 5600 Philippeville

N.B. : Ce message reste informel et n’engage aucunement la commune de Philippeville. Tout courrier officiel doit être confirmé
par lettre revêtue de la signature du Bourgmestre, contresignée par le directeur général et recevoir en sus le sceau communal
conformément à l’article L1132-3 du Code de la démocratie locale et de la décentralisation. Ce message et tous les fichiers
transmis en annexe sont confidentiels et destinés seulement à l’utilisation de l’individu ou de l’entité à qui ils sont adressés.
Si vous avez reçu ce message par erreur, ayez la gentillesse d’informer l’auteur de celui-ci.

-----Message d'origine-----
De : Seïdoff Michaël <[FOI #5315 email]>
Envoyé : vendredi 9 août 2024 16:37
À : DG <[Philippeville request email]>
Objet : Demande au nom de la Liberté d'accès à l'information - Analyse comparative des finances de la commune avec son cluster, fournie par Belfius

Cher/Chère Ville de Philippeville,

Pourriez-vous me fournir la dernière Analyse comparative des finances de la commune avec son cluster, fournie par Belfius (i e avec la dernière typologie socio-economique des communes wallonnes) ?

PS : je souhaiterais recevoir la version dans un format qui permette une recherche textuelle (pas d'image ou de pdf scannés au format image inutilisable, s'il vous plait) voici par exemple ce qu'une autre commune a transmis
https://transparencia.be/request/1093/re...

https://transparencia.be/request/1093/re...

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

Seïdoff Michaël

Afficher les sections citées

Gelieve dit e-mailadres te gebruiken voor alle antwoorden op deze vraag.
[FOI #5315 email]

Is [adresse email] een verkeerd adres om Openbaarheid van bestuur aan te vragen Stad Philippeville? Indien ja, gelieve met ons contact op te nemenvia deze weg:
https://transparencia.be/nl_BE/change_re...

Disclaimer: dit bericht en de antwoorden/documenten die u aanmaakt, worden vrij toegankelijk op internet geplaatst. Ons privacy- en auteursrechtsbeleid:
https://transparencia.be/nl_BE/help/offi...

Dank voor uw begrip dat in bepaalde gevallen de publicatie van aanvragen en antwoorden uitgesteld wordt.

Als u deze dienstverlening inzake openbaarheid van bestuur, dankzij deze website, nuttig vindt, kan u aan de webmaster van uw organisatie vragen om een link te plaatsen naar onze website.

-------------------------------------------------------------------