Notification and SMTP setup
- Review existing rules before creating or changing a rule.
- Choose the supported event, channel and recipient settings shown in the form.
- Review delivery status and investigate failed or pending work through the operational runbook.
- Under SMTP email relay, enter the provider hostname, port, TLS mode, sender, and public HTTPS CaseHub address. Choose SMTP login or provider authorization of the VPS IP.
- Save details and pause relay, then Check saved connection (no email). After a successful check, select Enable relay. Configure email recipients, schedule and anti-spam limits in Escalation rules.
- Leave the password blank to retain it only for the same server, port, TLS mode and username. Re-enter it when those details change. Selecting IP relay clears the saved login.
- Use Pause relay to stop new sends. Saving any SMTP details pauses it and requires a new connection check. Reload if another administrator changed the settings.
Things to know
General notification rules remain in-app. SMTP escalation digests have separate controls on Escalation rules.
Help opens in a separate tab at this topic. Use Contents to browse guidance, then return to your original CaseHub tab to continue; your unsaved entries stay there.
Notification rules deliver alerts after events. To create timed/category/priority escalation conditions, use Escalation rules.
Invalid rules keep your entries on the form and show how to correct them. SLA/contract events require Case lead role or Configuration administrator role; case assignee/creator are only for case events.
SMTP setup requires notification.configure permission. Passwords are encrypted with a server-managed key and never redisplayed. If protected storage is unavailable, a server administrator must provision or restore the matching key.
The connection check sends no email and verifies TLS and optional login only. It cannot confirm permission to use the sender address, recipient acceptance or inbox delivery. Provider errors are summarized without exposing credentials.
Changes apply without restarting CaseHub. A send already in progress may finish after pausing. Digest deduplication, cooldowns and daily attempt limits still apply.
Help reviewed 2026-09-25
Return to your original CaseHub tab to continue working.