Email Configuration
Minut sends email notifications to your users — noise alerts, sensors going offline, integration failures, and account and billing messages. If your organisation filters inbound mail through a security gateway, your IT team may need to allowlist Minut before those notifications arrive reliably.
This page collects the technical details needed to do that. It is written for mail administrators; nothing here requires an API integration.
Summary
- Allow mail from the domain
minut.com, authenticated by DKIMd=minut.com. - Allow the URL domain
track.pstmrk.itin any link-scanning or URL-rewriting policy.
Item 2 is the one most often missed. Without it our emails arrive normally, but every button and link inside them is blocked. See Links inside our emails.
Sender addresses
All Minut email is sent from a single address:
noreply@minut.com
This covers account, property, and device notifications — noise alerts, sensor offline, integration issues, and billing — as well as messages sent to your guests.
The address is not monitored for replies. For support, contact Minut through your usual channel.
Authentication
Minut sends through Postmark. Our records are published as follows:
| Record | Value |
|---|---|
| SPF | minut.com includes spf.mtasv.net |
| Return-Path / envelope sender | pm-bounces.minut.com |
| DKIM | Signed as d=minut.com |
| DMARC | p=quarantine |
SPF authenticates against the Return-Path domain, pm-bounces.minut.com — not minut.com. This matters if your gateway evaluates the envelope sender rather than the From: header.
Because our DMARC policy is quarantine rather than reject, an authentication or filtering mismatch on either side sends our mail to junk silently, with no bounce message. If users report missing notifications and you see no rejections in your logs, check quarantine first.
IP ranges
We recommend a domain- and DKIM-based rule rather than an IP allowlist. Postmark updates its outbound ranges periodically, and an IP-based rule will eventually go stale without warning.
If your gateway requires IP-based rules, Postmark publishes its current ranges in IPs for Firewalls. Use that article as the source of truth — it separates the transactional and broadcast ranges and is kept up to date.
Links inside our emails
For delivery and engagement tracking, links in our emails are rewritten to Postmark's tracking domain. A link that reaches the recipient looks like this:
https://track.pstmrk.it/3s/web.minut.com%2Fhomes%2F...
Allow track.pstmrk.it and pstmrk.it in any URL filtering, link isolation, or link-rewriting policy. This includes Mimecast, Proofpoint, and Microsoft Defender Safe Links, as well as any rule that blocks unrecognised redirect services.
Allowlisting minut.com alone does not cover this, because the links no longer point at minut.com.
If the tracking domain is blocked, the symptom is easy to misdiagnose: the emails arrive and look correct, but actions inside them fail — verifying an email address, reconnecting an integration, opening a unit.
Our emails also contain a tracking pixel on the same domain. Blocking images is harmless and does not affect functionality.
Mail streams
Minut sends on two separate Postmark streams:
- Transactional — alerts and account mail.
- Broadcast — surveys, reminders, and product announcements.
Broadcast mail may be classified as bulk by your filters. If you allowlist transactional traffic only, some legitimate Minut mail may still be junked.
Troubleshooting
| Symptom | Likely cause |
|---|---|
| No notifications arrive, and no bounces appear in your logs | DMARC quarantine — check your junk or quarantine store first |
| Emails arrive and look correct, but buttons and links do nothing | track.pstmrk.it blocked by a URL-filtering or link-rewriting policy |
| Alerts arrive, but surveys and announcements don't | Broadcast stream classified as bulk |
| Delivery worked, then stopped with no configuration change on your side | IP-based allowlist has gone stale — move to a domain and DKIM rule |