Notifications

MailShield tells you about changes and problems through alerts. This page covers where alerts show up, how to choose which ones reach you, the daily summary, notification channels (your own and the team's) and scheduled reports. For what each alert type means, see Alerts.

The Notifications Page

Click Notifications in the sidebar to see every alert for the organization, newest first, 50 per page. Use Newer and Older to move between pages.

• Use the All, Unread and Critical tabs to narrow the list.
• Filter by alert type, and by domain when the organization has more than one.
• Click Mark as read on an alert, or Mark All Read to clear the list.

Every alert appears here, whatever your email and channel settings are.

Choose Which Alerts Reach You

Go to Settings → Notifications. The Alerts card has one switch per alert type:

Switch	Alerts you when
Score changes	A domain's score moves by 10 or more points, or its grade changes
DNS changes	A monitored DNS record changes, or a check finds a problem in one (such as two DMARC records)
High failure rates	DMARC or TLS reports show a high share of failures
Certificate expiry	A mail server TLS certificate or BIMI VMC expires within 14 days (critical at 3 days), or a new certificate or TLS problem appears on a mail server

All four are on by default, and changes save as you flip a switch. The switches are personal: they apply to you, in the organization that's currently selected. If you belong to several organizations, set them in each one.

MailShield emails each alert type you've switched on to the address on your account. Switching a type off stops its emails and the messages to your own channels, but the alerts still appear on the Notifications page. Team channels don't follow your switches: each one has its own alert types.

Daily Summary

To get fewer emails, turn on Daily summary in the Email part of the Alerts card. Info and warning alerts then arrive as one email a day, at 08:00 UTC, instead of one by one. Critical alerts still arrive right away.

• The summary lists the alerts since the previous one, grouped by domain, with a link to each domain. It only includes the alert types you've switched on.
• The first summary covers the alerts since you turned it on. On a day without alerts, no summary is sent.
• The setting is personal, like the switches, and you get one summary per organization.
• Notification channels aren't affected: they still get each alert as it happens.
• If you turn the summary off, the alerts it was holding arrive in one final summary within a few minutes. After that, each alert is emailed as it happens.

Notification Channels

Requires: Pro plan.

Channels send alerts to other tools, in addition to email. Supported services: Slack, Microsoft Teams, Discord, Telegram, Matrix, Mattermost, Pushover, PagerDuty, Datadog and Webhook.

There are two kinds:

• Your channels are personal, like the alert switches: a channel receives the alert types you've switched on, from its minimum severity up. Every member can add their own.
• Team channels belong to the organization. Owners and admins add them, and each one has its own alert types and minimum severity. They don't depend on any member's settings, so they keep working when members leave or delete their account. See Team Channels.

If the same destination is added more than once, for example as a team channel and as someone's own channel, it gets each alert once. Each message has the alert, what changed where that applies, and a link to the details in MailShield.

Add a Channel

1. Go to Settings → Notifications.
2. In Your Channels, click Add Channel.
3. Pick the Service and fill in its fields (see below).
4. Under Send, choose All alerts, Warnings and critical or Critical only. PagerDuty starts at Critical only, the other services at All alerts. Improvements and other informational alerts only go to channels set to All alerts.
5. Optionally give the channel a Label.
6. Click Save & Test to save and send a test message, or Save. If the test fails, the channel isn't kept.

Each channel in the list has a menu to change which alerts it gets, a Test button, a switch to pause it and a remove button.

Service	What you need
Slack, Discord, Microsoft Teams, Mattermost	An incoming webhook URL from that service
Telegram	Your Telegram username. First open Telegram, search for @MailShieldBot and send it /start, then click Verify Account
Pushover	Your Pushover user key
Matrix	A username, password, homeserver (for example matrix.org) and room
PagerDuty	An Events API v2 integration key and a REST API key
Datadog	An API key and an application key; region us (default) or eu
Webhook	An https:// URL on a public host. MailShield sends each alert as a JSON POST request with the keys title, message, type (info, warning, or failure for critical alerts) and version. If you set a shared secret, it's sent in the X-Webhook-Secret header

Team Channels

Requires: Pro plan. Owners and admins add, change and remove team channels; members can see them.

Use a team channel for a shared destination, such as your team's Slack channel or an on-call PagerDuty service, so alerts keep reaching it whoever is in the organization.

1. Go to Settings → Notifications.
2. In Team Channels, click Add Team Channel.
3. Pick the Service and fill in its fields, as for your own channels.
4. Under Send, choose All alerts, Warnings and critical or Critical only.
5. Under Alert types, choose what the channel receives: Score changes, DNS changes, High failure rates and Certificate expiry (the same types as the alert switches). All four are selected to start with.
6. Optionally give the channel a Label, then click Save & Test or Save.

Owners and admins can test a team channel, pause it with its switch, edit it and remove it. Editing changes the label, Send and Alert types. To send to a different destination, remove the channel and add a new one.

Members see each team channel's service, minimum severity and alert types, but never its webhook URL or keys. Adding, changing, pausing and removing a team channel is recorded in the audit log.

Scheduled Reports

Requires: Pro plan. Owners and admins create and edit scheduled reports; members can see them.

A scheduled report emails a summary of your domains' security on a fixed schedule, with a PDF report attached. If you've set up report branding, the PDF carries your brand instead of MailShield's, and so does the email of a customer report.

1. Go to Settings → Notifications.
2. In Scheduled Reports, click Add Report.
3. Under Send for, choose All domains (whole organization) or one customer. A customer report covers only that customer's domains and goes to the customer's contact email automatically.
4. Choose the Frequency: Daily, Weekly (pick the day) or Monthly (pick a day from 1 to 28). Reports go out at 08:00 UTC on those days.
5. Enter Recipients, separated by commas or new lines. They're optional when the customer you chose has a contact email.
6. Leave Enabled on and click Create.

To change a report, click its edit button: the form opens with the report's saved settings. To pause a report, edit it and turn off Enabled. Customers and their contact emails are managed on the Domains page with Manage customers.

Every report email has an unsubscribe link. It stops that report for that address, including a customer's contact, and leaves other emails alone. Recipients outside your organization, such as a customer's contact, get the report without links into MailShield. If the organization moves back to Free, scheduled reports pause until you upgrade again.

Troubleshooting

Not Receiving Emails

1. Check your spam or junk folder.
2. Check that the alert type is switched on under Settings → Notifications, in the right organization.
3. If Daily summary is on, info and warning alerts arrive once a day, at 08:00 UTC.
4. Score, DNS change and certificate alerts are only sent for verified domains.

A Channel Isn't Receiving Alerts

1. Click Test next to the channel. If the test fails, check the URL or keys and add the channel again.
2. Make sure the channel's switch is on.
3. Check which alerts the channel gets. A channel set to Critical only or Warnings and critical doesn't get the less severe alerts, and a team channel only gets its chosen Alert types.
4. Channels need the Pro plan. If the organization moved back to Free, channels stop sending, and Settings → Notifications shows them as paused. They resume when you upgrade.