# Email delivery and participation tracking

Allowlist RandomCoffee's sending domains and exclude its links from security scanning so members receive their emails and their participation is tracked correctly.

import Callout from '@components/Callout.astro';

Make sure your email and security settings let RandomCoffee emails through, and do not trigger automated link scanning.

<Callout type="note">
  Share this article with your IT security, email infrastructure, or Microsoft 365 and Google Workspace admins.
</Callout>

## Allowlist the RandomCoffee domains

Check that emails sent by RandomCoffee are not quarantined by your security or antivirus solutions. Allowlist the following domains:

| Domain | Used for |
| --- | --- |
| `random-coffee.com` | Our main domain, used by the support team to help your admins and users when needed. |
| `transactional.eu.random-coffee.com` and `my.random-coffee.com` | Invitation and match messages. |
| `rc14.random-coffee.com` | Service messages. |

If you set up a [custom sending domain](/documentation/emails/sending-domain/), RandomCoffee emails are sent from your own domain: make sure it is allowed too.

## Keep RandomCoffee emails out of spam

- Confirm that RandomCoffee emails are not classified as spam in your organization.
- Add RandomCoffee's sending address to your corporate allowlist and Safe Senders list, so users' inboxes do not filter it. By default, emails are sent by `juliette@random-coffee.com`, unless your admins chose another sender.
- Check your spam logs regularly during onboarding, to fix false positives early.

## Do not block emails with a proxy

- Make sure no proxy or SMTP relay policy interferes with the direct delivery of RandomCoffee emails.
- Emails should flow without being blocked or delayed by intermediate security proxies.

## Allow emails from external domains

- RandomCoffee emails are sent from external servers. Check that your organization's email policies accept emails from the external domains used by RandomCoffee.
- Adjust any "internal only" delivery restriction that blocks or rejects RandomCoffee emails by mistake.

<Callout type="note">
  Your email security settings are managed by your organization. Putting these checks and allowlists in place is what guarantees that your users receive their introductions and communications without disruption.
</Callout>

## Stop security bots from clicking participation links

Many organizations use email security systems that automatically scan or pre-click every link in an email to detect malicious content. This protects users from phishing, but it can trigger participation or registration actions in RandomCoffee that the user never made.

### What link scanning does

Security bots visit every link in an email to analyze it before the email reaches the user. RandomCoffee then records a click before the user actually engages, which leads to:

- false participation records;
- inaccurate engagement statistics;
- missed introductions.

### Exclude RandomCoffee links from scanning

Work with your IT and security team to:

1. Allowlist RandomCoffee URLs in your link scanning or Safe Links settings, to bypass automated pre-clicking.
2. Exclude RandomCoffee emails from pre-click scanning, or disable it for them, if your security solution allows it.

The feature has a different name depending on your provider:

| Provider | Feature name | Action required |
| --- | --- | --- |
| Microsoft Defender for Office 365 | Safe Links | Create a URL allowlist or Safe Links exclusions |
| Proofpoint TAP | URL Defense | Create a bypass policy for RandomCoffee URLs |
| Mimecast | Targeted Threat Protection URL Protect | Add URL exclusions for RandomCoffee |