London Forum Day 1
Some notes I’ve made during the first day of the London Forum. Not really edited for publication, so y’all are getting pretty much what I wrote at the time.
It’s a lovely venue, in a beautiful church. Andrew finds excellent locations.
There are two tracks, plus some workshops so you’re getting less than half of what’s going on.
Reputation
There’s no such thing as “domain reputation”, and anything that looks like that is going to be misleading. And that’s why GPT took it away and it’s not coming back. In reality it’s dozens of different related reputation points, and combinations of them. Domain, authentication, content, recipient cohort. Misunderstanding of the single “domain reputation” number wasted a lot of peoples time, including a lot of people who didn’t have a problem.
IP reputation is still measured, but unless you’re a skript kiddy or malware or a compromised server it’s not going to affect your delivery at all.
Throttling and volume triggers. 3600 mails an hour is very different to 60 mails a minute. As a sender it’s better to do your rate limiting using buckets of a minute.
Authentication
You can’t DKIM sign a potato. You can avoid a lot of weird authentication issues by being careful to send valid email.
Having one person or group - IT Security or an Email Czar - who understands email and tracks all the email senders in an org could be helpful.
DKIM replay - detect by per-recipient counts. DKIM2 will fix.
Post quantum crypto for DKIM2, 2030. Maybe we can get CNAMEs and rotation this time.
You think you can detect Gmail image prefetches; you probably can’t reliably.
Boring consistency is the key to sustainable deliverability
Don’t try and game the filtering/reputation metrics. Don’t look like a spammer.
Don’t change everything at once. Moving to a new ESP and a new domain and new branding and new templates for a “new year, new start” is a bad idea.
Accessibility
Design it in at the beginning, it’ll be cheaper and faster than retrofitting. Load spread across copywriting, design and code.
Design system, reuse components.
Build it in, to code, to process to make it easier to maintain.
Hierarchy helps. Semantic structure helps.
Good accessibility (live text, structure) may make “AI” generated summaries better. Apple is different, doesn’t look at images, doesn’t understand emoji.
Android Watch only displays live text, while Apple resizes the html nicely.
https://lessonsinemail.com/resources/a11y-field-guide/index.html from Jay
Email HTML has the same things available as the Space Jam website.
Missing attributes (dir, role, lang, alt) are the low hanging fruit.
Do something, do anything. Run some tests, file some tickets - both with your team, and with tool vendors.
UK government email
Interesting - and timely - session about digital sovereignty for email in UK. Comparing with Germany, Austria and Switzerland.
UK shut down their NCSC mail check tool in March, but a huge number of gov servers are still sending reports there. Nobody knows if there’s a problem.
MTA-STS policies are being geoblocked, which is bad.
https://mxmap.github.io/mxmap-gb/
Interesting tooling using similar data points that we’d use for delivery monitoring to identify operational security problems.
Zero-trust architecture for email.
Tourism Ireland & Zeta
Tourism Ireland did a revamp of their design templates with Zeta. A little less dated looking, and less manual work to generate. Significant improvement in clicks, and in effort required to run the campaign. No mention of “opens” at all.
Vending machines
Laura’s comment “recipients aren’t vending machines you put email into and get purchases out” has been mentioned several times in later sessions.
Addendum
There were a few generative AI slides, which in addition to looking like ads for a bad pub karaoke night also relied on stale, borderline offensive stereotypes. Don’t do that.