Scribe sends emails for team invites, email verification, invite reminders, account and workspace notifications, billing updates, and policy notices. If you or your teammates expected one of these and it never arrived, this article covers the quick checks you can do yourself and the allowlist your email administrator may need to set up.
In most cases, the message was accepted by your mail server and then filed somewhere unexpected. So here are some quick checks to start before involving IT.
Quick checks (no admin needed)
- Check the address is spelled correctly. A single mistyped character in the domain (for example gmail.con instead of gmail.com) means the message was never deliverable. If the invite was sent to the wrong address, re-send it to the correct one.
- Check your Junk or Spam folder. Scribe invites are sometimes filed there before your organization has allowlisted our sending domains.
- Search your mailbox for "scribe" — invite emails have subjects like "[Name] invited you to join their team on Scribe."
- Check your organization's quarantine. Some companies hold external email in a quarantine you can review yourself (for example, a daily digest from Microsoft or Mimecast). If you're not sure, ask your IT team.
- Ask the sender to re-send. Team admins can re-send an invite from their team's member management page. If a re-send still doesn't arrive and the address is definitely correct, contact Scribe Support — the address may have been suppressed after an earlier delivery failure, and only we can clear that.
For email administrators: allowlisting Scribe
Scribe emails come from the domains and email addresses listed below. Allowlisting them significantly improves the chance that our email reaches your users' inboxes instead of their Junk folder or quarantine, and makes sure the links inside those emails work when clicked.
1. Sender domains (email gateway / safe senders)
Add these to your mail gateway's allowed senders (for example Mimecast, Proofpoint, Microsoft Defender / Exchange Online):
- noreply@t.scribe.com - team invites, email verification, and other account emails
- scribeteam@scribe.com - invite reminders, onboarding, product updates, and workspace notifications such as approvals, license requests, comments, and tasks
- scribeteam@scribe.com - onboarding, account lifecycle, and policy and legal notices
- no-reply@news.scribe.com - activities and pending-request notices
- product@scribehow.com - general product updates
- no-reply@scribehow.com - general product information
- marketing@scribehow.com - marketing emails
- success@scribehow.com - customer success
Or allow by domain: t.scribe.com, news.scribe.com, scribehow.com, scribe.com
2. Link domains (web proxy / URL filtering)
Links inside Scribe emails route through these domains. If your network filters outbound web traffic, allow them so the buttons and links in our emails work when clicked:
3. Image domain (optional, recommended)
-
userimg-assets.customeriomail.com- hosts the logos and images inside Scribe emails. This is a shared content-delivery domain operated by our email provider and is also used by other companies. If your policy doesn't permit it, Scribe emails still work; they'll just show broken image placeholders.
Two common pitfalls
- Email allowlisting and firewall allowlisting are separate controls. Allowing Scribe's application domains in your firewall or web proxy (see Does Scribe work behind firewalls?) does not affect email delivery, and vice versa. Both may be needed.
- Many gateways match domains exactly. Allowing scribe.com does not automatically allow t.scribe.com, new.scribe.com, or lt.scribe.com - add each subdomain explicitly. If your gateway supports wildcards, *.scribe.com and *.scribehow.com are simpler, but check whether its wildcards match more than one level. Some gateways will not match a host like email.news.scribe.com with a single-level wildcard.
Still stuck?
Submit a request to Scribe Support and include:
- the affected recipient addresses,
- the approximate time the email was expected, and
- what type of email it was (invite, verification, reminder, digest, pending-request notice, or policy notice).
We can check the delivery status of each message on our side and confirm whether it was accepted by your mail servers.