amaise sends notifications by email (case ready, new documents, collaboration requests, invitations, password reset). The messages are fully authenticated (SPF, DKIM, DMARC with a «reject» policy, TLS). Even so, a strict corporate spam filter can move a notification from a sender it does not yet know into the junk folder, into quarantine, or into the «Other» tab. Once your IT allows the sender, that stops happening. Depending on the system, an allow entry expires after a period without mail traffic or is lost when the mail system changes; for each route we say how long it lasts.

Give your IT these details. amaise sends from the region your workspace is hosted in:

For collaboration messages the name of the person who wrote appears in the sender («Anna Muster via amaise»); the address stays no-reply@…. Replies happen in amaise, so the notification carries no personal reply address.

Please do not allow IP addresses: amaise sends through Amazon SES, whose IP addresses can change. An allow entry belongs on the domains from the table.

Before you involve IT:

Microsoft offers several ways to allow a sender. We list them in the order most operations teams accept them.

1. Submit misclassified mail (recommended, no policy change)

Defender portal → Email & collaboration → Submissions → submit the affected message → «I have confirmed it is clean» → «Allow this message». Microsoft creates an allow entry from it that applies even under strict verdicts and that Microsoft maintains itself. Entries expire after 45 days without use; that is intended, because they are only needed while the filter is wrong.

2. Tenant allow list (fast, no submission)

Defender portal → Threat policies → Tenant Allow/Block Lists → Domains & addresses → allow eu.amaise.com (or ch.amaise.com / us.amaise.com, depending on your region). Same validity as above: 45 days after last use.

3. Microsoft Defender for Office 365: impersonation protection

If your tenant uses Defender, add [email protected] and the domains eu.amaise.com, ch.amaise.com and us.amaise.com under Anti-phishing policy → Impersonation → Trusted senders and domains. Impersonation protection is not overridden by allow lists. This entry does not expire.

4. Focused Inbox

To stop amaise mail landing in the «Other» tab, a mail flow rule without spam bypass helps: condition The sender → domain is eu.amaise.com (or ch.amaise.com, us.amaise.com) and message headers → contain Authentication-Results with dmarc=pass, action Set message header X-MS-Exchange-Organization-BypassFocusedInbox to true. This rule does not change the spam score and is compatible with common hardening baselines.

5. Showing images in Outlook

Classic Outlook does not load images from unknown senders and then shows the note «Outlook prevented automatic download of some pictures». The logo is embedded in the message and always visible; the note refers only to the counting pixel. If you would rather not see it, add the domain to the Safe senders list (via group policy or Set-MailboxJunkEmailConfiguration -TrustedSendersAndDomains); that also keeps the mail out of the individual mailbox's junk folder.

Not recommended: bypassing spam filtering by rule

A mail flow rule with «bypass spam filtering» (SCL -1) for the sender domain does work permanently, but it contradicts the CIS Benchmark for Microsoft 365 (control 6.2.2) and is rejected by many operations teams or removed at the next audit. If your policies do allow it, always combine it with the dmarc=pass condition; without that condition the rule would let forged senders through as well.

What no allow entry bypasses

Malware scanning, Safe Links, Safe Attachments and verdicts for high-confidence phishing always apply. An allow entry that would have to override those is a case for amaise support.

Send us the full headers of an affected message (in Outlook: File → Properties → Internet headers, in particular X-Forefront-Antispam-Report and Authentication-Results) to [email protected]. From those we can see why your mail system classified the message the way it did.