Make sure Yori emails arrive

Yori sends a few emails you need to act on, such as sign-in codes and invitations to join a workspace. Strict company email filters sometimes hold these back, even though they're genuine. This guide explains where Yori emails come from, what to check when one is missing, and how your IT team can make sure they get through.

Where Yori emails come from

Yori's account emails and workspace invitations come from the askyori.cloud domain.

Email	Sent from
Sign-in and verification codes, password resets and other account notices	notifications@askyori.cloud
Invitations to join a workspace or partner workspace	invitations@askyori.cloud

Replies to Yori's account emails and invitations go to support@askyori.cloud.

The code and links in these messages come from Yori's sign-in service. If a message is missing, request a new code or invitation rather than using an older one.

Yori emails are signed and authenticated with SPF, DKIM and DMARC, so your email system can confirm they really come from Yori.

Stripe sends invoice and payment emails separately. If one is missing, ask your workspace's billing manager to check the billing email address.

If an email doesn't arrive

1. Wait a few minutes. Yori may queue emails during a busy period, and company filters can hold mail for a short check.
2. Check your junk or spam folder. In Outlook, also check the Other tab if you use Focused Inbox.
3. Search your mailbox. Search for "Yori" or "askyori.cloud" to find the email in any folder.
4. Check you used the right address. An invitation goes to the exact email address it was sent to.
5. Ask for a new one. For a sign-in code, select Resend code. For an invitation, ask the person who invited you to resend it.

If an invitation still doesn't arrive, the person who invited you can copy the invite link and send it to you another way, such as in Teams or Slack. Workspace admins can copy it from People, and Enterprise admins can copy a partner admin's link from the partner's Members tab. See Partner workspaces.

If your company uses Microsoft 365 or another business email service, an email can be quarantined by your company's filter before it reaches you. Only your IT team can see and release quarantined email, so ask them to check, and share the next section with them.

For IT teams: allow Yori emails

Allow emails from askyori.cloud when they pass authentication. Don't allow the domain without an authentication check, because that would also let through anyone pretending to be Yori.

Microsoft 365

1. In the Microsoft Defender portal, open Email & collaboration, then Review, then Quarantine. Release any held Yori emails and report them as not junk. Reporting a released message also helps Microsoft learn that Yori emails are safe.
2. To let future Yori emails skip spam filtering, create a mail flow rule in the Exchange admin center under Mail flow, then Rules:
   • Apply this rule if the sender's domain is askyori.cloud and the message header Authentication-Results includes dmarc=pass.
   • Do the following: set the spam confidence level (SCL) to Bypass spam filtering.

A mail flow rule doesn't override Microsoft's malware or high confidence phishing checks. If Microsoft still quarantines a Yori email as phishing, release it and report it from the quarantine so Microsoft can review it.

Google Workspace

1. In the Google Admin console, open Apps, then Google Workspace, then Gmail, then Spam, phishing and malware.
2. Under Spam, add a setting that bypasses spam filters for messages from an approved senders list.
3. Create a list that contains askyori.cloud, and leave Require sender authentication turned on.

Mimecast

Create a Permitted Senders policy for askyori.cloud, so Mimecast doesn't hold Yori emails for spam checks. Keep Mimecast's authentication and impersonation checks turned on.

Other email filters

In any other email security service, add askyori.cloud as a trusted or safe sender domain, and require the message to pass SPF, DKIM or DMARC.

Related guides

• People and roles
• Partner workspaces
• Troubleshooting