Email deliverability

Thawly digests are only useful if they actually reach your inbox. This page is written for your IT or admin team — forward it on, or do it yourself if you're the admin.

The short version#

Add thawly.co.uk (and the address your digest comes from, e.g. digest@thawly.co.uk) to your safe-sender list. Two minutes of admin work, zero ongoing maintenance.

SPF, DKIM and DMARC — what they are#

These are three email-authentication standards your mail server checks before deciding to deliver, junk, or reject a message. Thawly's outbound mail (via Resend) is correctly signed under all three:

• SPF says "this server is allowed to send mail for thawly.co.uk".
• DKIM cryptographically signs every message so you can verify it wasn't tampered with in transit.
• DMARC is the policy that tells your mail server what to do if SPF or DKIM fail — and we publish a passing one.

You don't need to do anything to receive Thawly correctly. The configuration steps below are about overriding overzealous junk filters that quarantine legitimate, signed mail anyway.

Microsoft 365#

In Exchange Admin Center → Mail flow → Rules, create a new rule:

• Apply this rule if → The sender domain is → thawly.co.uk.
• Do the following → Set the spam confidence level (SCL) to → -1 (bypass spam filtering).

Or, less aggressively, allow-list thawly.co.uk under Anti-spam policies → Allowed senders and domains.

Google Workspace#

In Admin Console → Apps → Google Workspace → Gmail → Spam, Phishing and Malware:

1. Create a new email allow-list entry.
2. Add the IP ranges Resend publishes at resend.com/docs/send-with-resend/dedicated-ips, or simply add thawly.co.uk as a trusted sender in Approved senders.
3. Apply to the relevant organisational unit and save.

Still going to junk?#

Mark one digest as "Not junk" / "Move to inbox". Most providers learn quickly from a single explicit signal. If it persists, email hello@thawly.co.uk with the message headers and we'll diagnose.