A fascinating talk at Black Hat 2026 about the OpenAI and Hugging Face hacking incident, with insight into the AI agents' chain of thought.

How to check your SPF, DKIM, and DMARC are set up correctly in Google Workspace

Are you using Google Workspace? Did you self-deploy? If so, you’ve likely missed some settings, which is likely putting the emails you send into spam.

Don’t worry, this is incredibly common. I see this pretty much in every business that has set up Google Workspace on its own.

SPF, DKIM, and DMARC can look scary and complicated, so it makes sense that you’d skip them. But missing them doesn’t stop you from sending emails; it’s just that those emails are more likely to end up in spam.

So we’ve made a free Google Workspace email security check tool you can use to check that your Google Workspace email is set up correctly.

If you have a problem, it will take you to a free guide on how to fix it. No sign-in required, no email address needed to be given.

Once you’ve got everything set up, you should get a result like the one below in the screenshot with green ticks throughout.

And if you haven’t got time to fix the problem, or it still seems a bit too complicated and tricky, no worries, just book a video call with me.

I didn’t ask for this. Nicky sent it over unprompted, which makes it worth more than anything I’d have written myself:

We have been working with Kimbley IT for the past three years. They specialise in IT assistance and support for companies that use Google Workspace, and The PR Network is a Google business.

The service provided by James, Kyle and the team is phenomenal. They help with all aspects of our set up as a remote-first company in terms of service and support. They also go way above and beyond to make sure that we are optimising our Workspace subscription.

It’s imperative that we are using all the AI functionality to be as efficient and productive as possible. Kimbley provides loads of learning and training, support and hints and tips to keep us ahead of the curve.

They really are the perfect IT partner and I recommend them without hesitation!

Nicky Regazzoni, co-CEO, The PR Network

Thanks, Nicky, for the amazing words and feedback!

Sent a link to someone to a 19-minute video. They replied less than five minutes later that it was a great video.

Vibe Coding: You don't know what you don't know!

Ever trusted AI to help you code, only to discover it led you straight into a trap you never saw coming? That’s the hidden danger of vibe coding: you don’t know what you don’t know.

Over the weekend, a client contacted us. They are vibe coding a new internal app for their business, which will save them a lot of time. They wanted certain Google Workspace settings changed because the AI told them that was required. All good and well, but the problem was that changing the settings would have opened a vulnerability.

The client wouldn’t know this; they’re simply following the AI’s advice because they’re unaware of what they don’t know, so they can’t recognise when the AI is cutting corners. All the AI wants is to give them the results they request; it doesn’t care how it gets them.

AI and vibe coding are so easy, but it removes the essential element of understanding how something should work. If you go back to the days of Googling, you had to know something about the topic you were researching so you could tell whether the page you landed on was accurate.

This highlights the problem of vibe coding: you don’t know what you don’t know, so AI can lead you down the wrong path.

While major platforms can security‑check the code provided, AI will only act on the prompt you give it, and if the prompt lacks vital information, the AI won’t point out what’s missing - unless you specifically ask.

And that’s why partnering with a leading AI IT support partner like Kimbley IT is vital, so we can identify these risks before you vibe-code them into production.

So how did I help the client at the weekend? I didn’t deploy the changes they asked for; instead, I guided them down the correct path and produced the prompt they should have asked their AI for if they had known what they didn’t know. They are now on their way to creating a really handy app for their business. 👍

Here’s a photo of a friendly juvenile robin that came right up to me in the garden over the weekend.

Our first Google Workspace Marketplace app has been submitted to Google.

Hopefully it gets approved 🤞

It will save our Google Workspace by Kimbley IT clients a lot of the time when dealing with particular file types that aren’t natively supported in Google Drive.

We’re also making it free to the world so anyone can deploy it on their Google Workspace stack.

I’ll reveal more and the Marketplace link once the app gets approved!

If you’ve lost control of the model because it’s actively escaped, how can you guarantee the kill switch would even work?

PSU went bang this morning. It’s the first time I’ve had a PSU fail on one of my machines.

Kai (Kimbley AI) is our agent that interacts directly with our clients.

For the past 18 months, I have been building Kai, testing, spotting problems, testing again, and fine-tuning.

During testing, Kimbley IT clients interacted with Kai during short live test runs, which I constantly monitored; in that time, only one person guessed they were interacting with an AI agent rather than a living member of the team.

This week, Kai has been released and is autonomously interacting with clients without the overwatch I have provided in the past. So far, Kai has done brilliantly, with no need for the team at Kimbley IT to get involved or deploy the kill switch.

With these increased real-life interactions, I’m able to fine-tune Kai even more, especially when scenarios play out that you hadn’t expected or seen during the testing phase.

My vision for Kai is that within the next 12 to 24 months, Kai will be running at least 90% (hopefully more) of Kimbley IT, and the already-large proprietary instruction set and system prompt will be highly valuable.

To get there, I plan to focus on a few key next steps: continue scaling Kai’s involvement across more client interactions, integrate feedback from real-life scenarios to enhance its performance, and continually review the system prompt to ensure it captures our evolving client needs.

The value, though, for our clients is that Kai is enabling us to provide increasingly more services and features at no additional cost, and the feedback so far has been brilliant.

One client recently shared that a new email security system powered by Kai, which analyses dodgy-looking emails and guides team members on how to deal with them, was a “Bloody good system in my book.” When Kai advised them not to engage with a lead that would turn into a scam later down the line. This was based on Kai’s knowledge of past emails and current scam trends, allowing Kai to make an informed decision and provide excellent guidance.

Kai’s definitely going to win the team member of the month award.

The hatchling has emerged. Young pigeons develop quite rapidly; I estimate this one hatched a week ago, but this is the first occasion I’ve been able to observe it.

(The body to the left is the parent) I have only been able to get a photo of the hatchling’s head.