On 25/04/2022 17:48, Robert Sparks wrote:This transition is complete. If you see anything that looks like it
shouldn't, please let me know.
Well, the almost total absence of all mail - WG, announce, ietf.org etc - from the IETF in the course of 27th April. I have now, 28th April, received a lot of IETF mail dated 26th April so clearly there was a hiccup. I had assumed, as I posted to a list, a DoS attack and I even assumed that I knew which evil actor was at work - but I was wrong.
One of the changes made in this transition was to the IP address range of our mail servers. As the IETF is a very high volume mail sender our address ranges often need whitelisting or other special treatment by large mail receivers. Having that special treatment restored with one large receiver took a couple of days (and much thanks to the IETF’r who helped with that).
Jay Tom Petch
RjS
On 4/12/22 4:46 PM, Robert Sparks wrote:
All -
We are transitioning most of our service onto faster hardware with a
better network connection.
This is currently planned for approximately 1500-1900 UTC on April 25
(0800-1200 US Pacific).
This will affect ietf.org email (including list processing and archive
access), www.ietf.org, www.irtf.org, and the datatracker.
Email sent to ietf.org addresses during this time will queue, and will
be delivered after the transition is complete.
We are working to minimize the downtime of any individual service.
This transition includes steps towards not having to have transitions
that affect all services like this going forward.
Apologies in advance for the inconvenience,
RjS
Please note that Reply-To is set to tools-discuss@xxxxxxxx
A version of this announcement is in process for ietf-announce.
.
|
