![]() ![]() ![]() ![]() I asked the local IT guys to go to this specific workstation, perform an ant-virus run to clean-up the workstation so I can unlock the account. So, it was already blocked for 9 days and 122 outbound spam messages were detected the last 24 hours. OutboundSpamLast24Hours=122 OutboundMailLast24Hours=128 OutboundSpamPercent=953 Last Message MessagetraceId:4495783e-13af-483c-b8d2-08d643c0f46c Here you can see the user account that is blocked, including the reason and date for blocking as shown in the following screenshot: To check the outbound spam and the user that is blocked, open the Exchange Online Admin Center, select protection in the navigation bar and click the action center tab. It’s not a permission issue (was my first thought) but Exchange Online Protection is blocking the account because of spam.Įven in a hybrid scenario with centralized mail transport this can happen, because Exchange Online outbound mail (to Exchange 2010 on-premises) is still handled by Exchange Online Protection. Contact your email admin for assistance.Īt first, the only I read was “Your message couldn’t be delivered because you weren’t recognized as a valid sender” so it took me some time to figure out what was wrong. The most common reason for this is that your email address is suspected of sending spam and it’s no longer allowed to send messages outside of your organization. The NDR that was returned to the user said:ĭelivery has failed to these recipients or message couldn’t be delivered because you weren’t recognized as a valid sender. A user was not able to send out email to external recipients (this was already the case for a couple of weeks) but internal email, both in Office 365 as well as hybrid Exchange 2010 did work fine. Today a customer ran into an interesting issue. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |