SMTP error 452

[#1]

---

@offscotland wrote:

Tell me how to find that and I'll let you know.

---

https://whatismyipaddress.com/

[#2]

That’s the LAN address - it is the WAN address which is relevant - use what’s my IP address 

[#3]

My WAN address  is 84.92.10.xx (static)

[#4]

Oh!

That points away from a suspect profile.

[#5]

See attached

[#6]

I think there is mounting evidence for a time-related problem.

I have just had this problem again, at 15:55:08 and 15:58:27, but at 16:00:07 all was ok.

This is with static IP address 84:92:10:xx, no VPN, and first post for over an hour.

[#7]

Saturday morning 09:45... same issue. Time for a cup of tea and I will press 'send' again just after 10:00

10:01 all good.....

[#8]

Same error here started 11 Sept 2025 having been away for a few days.

Using webmail on a windows 11 PC no VPN. Send about 5 emails per week!

Waiting util the top of the hour works.

Does anyone have a proper solution yet?

[#9]

@Helios150 

This has been an intermittent issue for a few days.  It seems more abundant today - I have seen this twice myself today (but realised it).

@LexLex2020 - can you please get an IMT escalation on this?  Also see the SU discussion.

[#10]

Am I right in interpreting this that we are required to limit the number of emails we send in an hour?  Another thread was locked off on the basis that this thread provides a solution, which I don’t get. Can someone set this out in simple language whether this is a problem being sorted, or is considered fixed and we need to adjust how we use the service?  Sorry for being a dunce.

[#11]

My post this morning on the thread 

Cannot send emails, either from PC or iPhone

which appears to be the same problem, and immediately garnered several responses suggests this has become a bigger problem today.  However the moderator has locked it in favour of this thread (which has yet to show any new responses).

I am not sure how most people would know to report it on this one, as there is nothing in the error messages I received to say it was anything to do with the cryptic "SMTP error 452".

[#12]

---

@Townman wrote:
...it seems more abundant today - I have seen this twice myself today (but realised it).

@LexLex2020 - can you please get an IMT escalation on this?  Also see the SU discussion.

---

Add me to the list of people unable to send mail to any email address because of this "too many recipients" error, despite this being the first time I've tried to send an email today.

At least I've only got to wait for about another 10 mins until the hour ticks over and I can, hopefully, send my message.

EDITED TO ADD:

Yup, waiting until the hour ticked over worked.  My message went without error at 16:05.

[#13]

---

@cmon_mary wrote:

Am I right in interpreting this that we are required to limit the number of emails we send in an hour?

Another thread was locked off on the basis that this thread provides a solution, which I don’t get.

Can someone set this out in simple language whether this is a problem being sorted, or is considered fixed and we need to adjust how we use the service?  Sorry for being a dunce.

---

No there is no need to drastically limit the number of emails sent in an hour.  There is a service quita per user, there is presently a flaw with that mechanism.

Other threads have not been locked in favour of this one on the basis that this one contains a solution - the lock and redirect is to around having to deal with numerous threads on the same subject.

In simple terms the business has the matter in hand.

@JudithPS77 

For the majority of users the SMTP Error 452 is what will be seen in the non-delivery reports arising from this issue.

Server error: '452 <**********@gmail.com> recipient rejected - too many recipient in last hour'

Unfortunately some email clients are less helpful in reporting the issue.

[#14]

Also seeing a reoccurrence today (13-Sept, 15:52) after a few days without obvious issues:

Sending of the message failed.
An error occurred while sending mail. The mail server responded:  
<xxxx> recipient rejected - too many recipient in last hour.
 Please check the message recipient "xxx" and try again.

16:04 - message successfully sent.

[#15]

@JudithPS77 

Your other post has been locked in favour of this main topic, which has the attention of key players, to avoid a scatter gun approach, which causes nugatory work and takes resources away from addressing the problem. If you read this thread you will note that it is being taken seriously and the problem has been escalated by a Superuser.

Be assured that there was no intention to ignore your complaint. As you had already received replies to your original post, merging the two topics would likely of caused confusion.