Making sure our email arrives

What to allow

This site has not been told which address its email comes from. Ask support@etpcampus.com before you change your filters, so you allow the right domain.

We authenticate our mail with SPF, DKIM and DMARC, so most filters will accept it without help. The step below is for the ones that do not.

Google Workspace

1. Open Google Admin → Apps → Google Workspace → Gmail.
2. Choose Spam, phishing and malware.
3. Find Email allowlist and add our sending domain. If you prefer to be narrower, use Content compliance and match the sender address instead.
4. Save. It takes up to an hour to apply.

The allowlist field expects IP addresses in some Workspace versions. If yours does, skip it and use Content compliance — match From containing that domain and set the action to bypass the spam filter.

Microsoft 365

1. Open the Microsoft Defender portal → Email & collaboration → Policies & rules → Threat policies.
2. Choose Tenant Allow/Block Lists, then the Domains & addresses tab.
3. Allow → add our sending domain. Set it not to expire, or to a long expiry — an allow entry that quietly lapses is how this breaks six months later.

Avoid the old “safe senders” list in Exchange transport rules if you can. It skips authentication checks, which is exactly the protection you want kept on.

Tell your staff it is coming

The first message from an unfamiliar address during an outage looks like the phishing attempt everyone has been trained to expect. One line in a staff meeting — “if something is down you will get an email from our sending domain, and it will never ask you for anything” — is worth more than any filter change.

What we will never do

Our emails never ask anyone to sign in, enter a password, or open an attachment. They say what is down and link to your dashboard. If something claiming to be us does otherwise, it is not us — forward it to support@etpcampus.com.