Sudden failure to send emails through specified SMTP server with python script

Anonymous
2021-07-15T20:57:04+00:00

Hi,

We have been sending automated emails through a python script for a while now and suddenly getting this error:

Failed to send an E-mail through the specified SMTP server [smtp.office365.com]:
Mailbox unavailable. The server response was: 5.2.252 Sender throttled due to continuous send as denied errors.
[Hostname=BN9PR12MB5179.namprd12.prod.outlook.com]

All of the login/password information is correct in the python script for sending the email, so why is this suddenly happening?

Microsoft 365 and Office | Subscription, account, billing | For business | Other

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

43 answers

Sort by: Oldest
  1. Anonymous
    2021-07-21T01:45:04+00:00

    Found this thread because we're also suddenly encountering the same error:

    "550 5.2.252 Sender throttled due to continuous send as denied errors."

    We've been sending automated emails from a Filemaker database using a plugin for years now, but it started throwing this error within the last week. We routinely use a ReplyTo email which differs from the sending account, but we also normally specify the "Send as permissions" permissions for each account as well.

    We however forgot to set the "Send as permissions" recently for a ReplyTo account, so a working theory is that this tripped the throttling, and perhaps if/when the throttling timeout expires (anyone know how long that takes?) - and now that we've set the permission for the offending account - perhaps things will work reliably again.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2021-07-21T12:45:39+00:00

    We are getting this on all our customer sites sending mail from systems using SMTP but getting no error but that could be the not so great SMTP implementation not being able to handle the error. If we manually restart the process sending the mail then it starts sending again.

    We have asked some of the friendlier ones to log tickets with MS to see what the issue is but it feels like a new rate limit or an existing rate limit that is now being hard enforced.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2021-07-21T13:30:58+00:00

    I can't believe that there is no any official response from MS about this issue, consider it affects multiple customers already. I suggest everyone who has this issue open a ticket with MS.

    I am still waiting for the reply from the MS tech. This already had a big impact to our business as we can't send automated emails to customers. We are thinking of using other SMTP provider to do the email relay.

    Very frustrated with MS!

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2021-07-21T13:38:21+00:00

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  5. Anonymous
    2021-07-21T13:47:25+00:00

    Thank you Frank.

    I think this is somewhat related to our issues. However, from the article the error message should be "432 4.3.2 STOREDRV.ClientSubmit; sender thread limit exceeded", not "550 5.2.252 Sender throttled due to continuous send as denied errors.". And the behavior should be delay in email sending, not rejecting connection completely.

    It could be when MS deploy this new throttle, they mess up something else, now we have an unexpected throttle.

    Was this answer helpful?

    0 comments No comments