Je ne peux plus envoyer de mails
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(294.40000000000003, 85%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECC%3C/text%3E%3C/svg%3E)
Cécile Callens
0
Points de réputation
Bonjour
Dès que j'envoie un e-mail, je reçois systématiquement le message ci-dessous.
Pouvez-vous débloquer la situation ?
Merci
Cécile
Informations de diagnostic pour les administrateurs :
Serveur de génération : AM8P191MB1393.EURP191.PROD.OUTLOOK.COM
"mail de la personne"
Remote server returned '554 5.7.0 < #5.7.520 smtp;550 5.7.520 Message blocked because it contains content identified as spam. AS(4810)>'
En-têtes de message d'origine :
Received: from AM0P191MB0385.EURP191.PROD.OUTLOOK.COM (2603:10a6:208:4c::33)
by AM8P191MB1393.EURP191.PROD.OUTLOOK.COM (2603:10a6:20b:1cb::23) with
Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.9542.9; Wed, 21 Jan
2026 09:02:04 +0000
Received: from AM0P191MB0385.EURP191.PROD.OUTLOOK.COM
([fe80::145b:cdad:b030:da2e]) by AM0P191MB0385.EURP191.PROD.OUTLOOK.COM
([fe80::145b:cdad:b030:da2e%4]) with mapi id 15.20.9542.008; Wed, 21 Jan 2026
09:02:04 +0000
Content-Type: application/ms-tnef; name="winmail.dat"
Content-Transfer-Encoding: base64
déménagé de Microsoft 365 et Office | Autres
Outlook | Web | Outlook.com | Email
{count} votes
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(156.8, 92%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGB%3C/text%3E%3C/svg%3E)
Gabe Bratton 606 Points de réputation Employée Microsoft Modérateur2026-01-22T14:55:30.7733333+00:00 The consumer support team escalated an issue with this error to the Outlook Team and they say they have reverted the change that caused it. It might take a few hours to stop occurring.
Se connecter pour commenter
Se connecter pour répondre