Email alerts
An expiry alert email is sent the moment an alert is raised on a rule with the email channel switched on.
Who receives them
Section titled “Who receives them”A rule chooses between two kinds of recipient.
| Rule setting | Who is emailed |
|---|---|
| No addresses listed | Every owner and admin in the workspace who has Immediate critical alerts switched on |
| One or more addresses listed | Only those addresses |
Addresses typed into a rule are treated as fixed destinations. A shared NOC inbox, a client contact or a ticket drop-box is not a Tidehawk user, so it holds no notification preference and is never filtered out.
Users whose address has been recorded as bouncing are skipped in the owners and admins list, so a dead mailbox does not silently hold up the rest.
Notification preferences
Section titled “Notification preferences”Each user controls their own email on Settings, under notifications. The toggle that governs expiry alerts is Immediate critical alerts. Switching it off removes that user from the fallback list. It has no effect on addresses typed into a rule.
What the email contains
Section titled “What the email contains”Certificate alerts arrive with a subject like SSL certificate expires in 12 days — mail.example.co.uk, or SSL certificate EXPIRED — mail.example.co.uk once the date has passed. Domain alerts use Domain registration expires in 12 days — example.co.uk.
Inside you get:
- A coloured banner giving the urgency. Seven days or fewer is critical, 30 days or fewer is a warning, anything further out is informational.
- One sentence stating the exact expiry date.
- The client name, the expiry date and the time remaining. Domain alerts add the registrar when Tidehawk knows it.
- A View certificate or View domain button that opens the record in Tidehawk.
- A footnote naming the threshold that fired, for example “This alert fired because the certificate expiry fell within your 30-day threshold.”
Domain emails state plainly that this is a domain registration expiry and not a certificate expiry, because the two are easy to confuse when they arrive in the same inbox.
Delivery and retries
Section titled “Delivery and retries”Every address on the rule is attempted, one at a time. One address failing does not cost the others their alert.
If at least one address accepted the message, the alert is marked delivered and the failures are recorded against the alert event. If no address accepted it, the whole send is retried, up to three attempts with a growing delay. Because the alert itself is only raised once, a retry can never send the alert twice to an address that already received it.
On the Alerts page, an event whose email is still in flight shows Queued. More than an hour after the alert fired without a successful send, it shows Failed.
Sender addresses
Section titled “Sender addresses”Alerts come from noreply@tidehawk.co, with replies directed to support@tidehawk.co. Add both to your allow lists.