SMTP error 452 (too many recipients in the last hour)

[#1]

We didn't get a 'watch this space' email or a 60-day warning email. Only a 30 day warning and apparently we were migrated yesterday but haven't had any confirmation or info from Greenby. So it appears the execution of the communication strategy for this project is patchy at best.

[#2]

There are various metrics, not disclosed for clear security reasons.

Users will receive communication when their cohort is scheduled.  The cohorts are divided by a combination of...

• Having an identified current broadband account
• Brand
• User of webmail
• Having a hosted domain
• Having a hosted website
• Having the cgi and database platform
• Then probably letter of the alphabet

The further you are down that list, the later is your cohort.  Using webmail and having none of the rest will pull you to the front.  Personally I have all of the above and am content to simply wait patiently until they get to the end.

I do not understand the clamour around this; it will happen when it happens and it should be largely non-disruptive.  Frankly its better to wait, so that if there are gremlins, they have a chance of being fixed before your turn arrives.

[#3]

@Townman I totally agree with your last paragraph - when it happens, it happens, and if there no problems, great. Equally, if there are problems users need to shout up.

Out if interest, where do those of us with 'mail only' accounts come in the pecking order? I''m not worried, just curious.

[#4]

> Out if interest, where do those of us with 'mail only' accounts come in the pecking order? I''m not worried, just curious.

Depends.

There are various types of 'mail only' accounts. We have mail only with added extras (such as domains) which haven't been done yet, and of course Plusnet mail only.

[#5]

Mine is 'mail only' (ex Plusnet) with no 'added extras', @plusnettony . As said though, I'm not worried, it will happen when it happens.

[#6]

I welcome further examples of this, but have raised directly to the supplier. 

[#7]

---

@martinund wrote:

So is it related to the number of emails that a given user Y (with addresses X@Y.force9.co.uk) sends, or is it the number of emails that all users (all the Ys) send through relay.force9.net?

There is a mixture of triggers, but all discussion is that for a normal non-abusive user 'Y'  the blocking comes from some kind of aggregate 'count up' across a large number of users 'Y' sending through a small number of route(s).

So closer to your latter premise, but not as simplistic as all of 'relay.branding.net'.  The exact count up arrangement is withheld for security reasons.

The counter is reported to reset on the hour, so sending at hh:01 usually works.