Every organization gets a forwarding address. Anything sent to it becomes feedback — no integration to build, and it works with whatever mail client the people talking to your customers already use.
Forward a message by hand, or set up a rule in Gmail or Outlook that forwards a whole label or folder.
How the address is protected
Not by secrecy. The address is readable, so it is guessable. What protects it is who is allowed to send to it.
Mail is accepted from:
- Your organization's own domain — always, and it cannot be removed.
- Anything an admin has added — a whole domain (
partner.com) or a single address ([email protected]).
Everything else is refused.
:::note Subdomains do not inherit
Allowing acme.com does not allow mail.acme.com. A subdomain is often
operated by somebody else — a marketing tool, a support vendor — and quietly
extending trust down the tree is how an allowlist stops meaning what its author
thought it meant.
:::
Sender authentication
An allowlist on its own would mean "only mail that says it is from
acme.com" — a header anyone can write. So Actify also checks the
Authentication-Results header added by the receiving infrastructure.
DMARC is the verdict that matters, because it checks alignment with the
visible From. SPF is the fallback where no DMARC result is present.
A message with no such header is accepted. Not every delivery path adds one, and
refusing all mail over a missing header would break the integration completely
rather than partially — while an attacker asserting a domain they do not own
does produce a header, with fail in it.
What was turned away
Refused messages are listed under the relay, with the sender, the subject and the reason:
| Reason | Meaning |
|---|---|
sender_not_allowed | The address is not covered by any rule above. |
failed_authentication | The message did not really come from the domain it claimed. |
The body of a refused message is never kept. This is mail Actify decided it had no relationship with, and storing the contents of unsolicited email is a liability. The sender and subject are kept because "someone was turned away" with neither is unactionable.
Forwarded messages
When you forward a message, the sender is you. Actify reads the forwarded block to recover who originally wrote it, and when — so the feedback is attributed to the customer rather than to the colleague who passed it on.
Connecting
The relay is created for you; there is nothing to set up.
Settings → Integrations → Email shows the address, how many messages have arrived, and the sender rules. Adding or removing allowed senders is restricted to an organization's owner or admin.
If the deployment has no inbound domain configured, the feature reports itself as unavailable rather than half-working.
Disconnecting
Settings → Integrations → Email → Disconnect. The address stops accepting mail. Feedback already collected stays.
Reconnecting later restores the same address. A relay address gets written into other people's forwarding rules and contact cards; issuing a new one would turn all of them into silence nobody can see.
Data stored
- The relay address and its allowed-sender list
- For each accepted message: its body, subject, the original author's name and address where recoverable, and when it was sent
- For each refused message: sender, subject and reason — never the body
Questions about this integration: [email protected]