The gang is trickling in

It’s been a few years since we’ve actually made it to a MAAWG. We missed much of 2018 and 2019 due to our international move. Then 2020 San Francisco conflicted with a personal engagement. Then, well, pandemic hit and it’s been virtual and then we were moving and … wow, it’s been busy!

We did make it to London, though, and have started reconnecting with colleagues new and old. We also got a chance to take a trip down the river over the weekend leading to a chance to get some pretty pictures.

After a day of touristing, we’re now buckling down to do some hard work. Steve’s doing a training session this afternoon and I’m moderating a panel tomorrow. I’m so excited to be back in person learning from my colleagues. Don’t forget to come by and say hi if you’re here.

Click to rate this post!
[Total: 0 Average: 0]

Check Also

message-not-compliant-with-the-rfcs

Message not compliant with the RFCs

Every once in a while we’ll see a rejection from Yahoo that says RFCs 554 5.0.0 Message not accepted due to failed RFC compliance. What does that mean and what can we do about it? It really does mean exactly what it says on the label: there’s something about the message that is not in compliance with any number of RFCs and are not going

>