---
title: Email Masking - Types of Email Masking
description: "There are two main ways to mask your sender email when using our platform: MAIL FROM masking and spoof-style masking . Both allow emails to appear asโฆ"
---
[Skip to content](https://knowledgehub.crowdcomms.com/38-3-3-email-masking-types-of-email-masking#main-content)
[](https://crowdcomms.com/)
- Home
- Products
- Pricing
- Blog
- Company
Open main navigation
Close main navigation
- Home
- Products
- Pricing
- Blog
- Company
- Contact us
Contact us
How can we help you?
- There are no suggestions because the search field is empty.
1. [Knowledge Hub](https://knowledgehub.crowdcomms.com/?hsLang=en-gb)
2. [Event App, Virtual & Hybrid Platform](https://knowledgehub.crowdcomms.com/event-app-virtual-hybrid-platform?hsLang=en-gb)
3. [Promotion & Communications](https://knowledgehub.crowdcomms.com/event-app-virtual-hybrid-platform?hsLang=en-gb#promotion-communications)
28 September 2026
# Email Masking - Types of Email Masking
#### Overview
There are two main ways to mask your sender email when using our platform: **MAIL FROM masking** and **spoof-style masking**. Both allow emails to appear as though they come from your domain, but each behaves differently and requires different DNS setup.
We recommend **MAIL FROM masking** where possible - it provides stronger deliverability and better domain alignment. However, it can only be used if your domain isn't already using `mail.` for receiving emails.
#### MAIL FROM Masking (Recommended)
MAIL FROM masking allows us to send email on your behalf using a dedicated subdomain - in our case, this is always `mail.yourdomain.com`. It ensures that email authentication checks like SPF and DMARC align properly.
### What it requires:
- You must be able to set DNS records under `mail.yourdomain.com`
- **You cannot already be using** `mail.` **as an MX (mail exchange) entry to receive mail**
- SPF and MX records must be configured for `mail.yourdomain.com`
- DKIM record must be added on the root domain
### Benefits:
- **๐ก๏ธ Better deliverability** โ SPF and MAIL FROM domain are aligned, reducing chances of mail being flagged
- **๐ Passes DMARC alignment** โ Receiving servers can verify the sending domain properly
- **๐งน Cleaner headers** โ Inbox providers show your domain more prominently and may hide "via amazonses.com" info
### Limitations:
- **๐ซ Cannot be used if `mail.` already receives mail** โ If your MX record is set on `mail.yourdomain.com`, you won't be able to use this method
- **๐ ๏ธ Requires more DNS setup** โ SPF and MX must be added under the `mail.` subdomain
- **๐ Less flexible** โ Our system currently does not support custom subdomains like `emails.` or `send.` - only `mail.` is allowed
If your existing mail setup relies on receiving mail at `mail.yourdomain.com`, you will need to use spoof-style masking instead.
---
Spoof-Style Masking (Non-MAIL FROM)
This fallback option sets your **From** address to a domain you control (e.g. `info@yourdomain.com`) but doesn't configure a MAIL FROM domain. The email is still technically sent from Amazon SES on your behalf, but alignment checks like DMARC may not fully pass.
##### What it requires:
- DKIM record on the root domain
- SPF record is recommended but optional
- No MX or MAIL FROM setup required
##### Benefits:
- **โก Fast to set up** โ Only one or two records are needed
- **โ
No MX conflict** โ Works even if `mail.` is already used to receive email
- **๐งฉ Minimal DNS changes** โ Useful if you have limited access or control over DNS zones
##### Drawbacks:
- **โ ๏ธ Slightly lower deliverability** โ Missing MAIL FROM alignment may reduce trust scores in some inboxes
- **๐ต๏ธ Reveals SES in headers** โ Users can view technical details that expose Amazon as the sender
- **โ Fails DMARC alignment** โ SPF and From address don't fully align, though DKIM can still pass
---
#### What Is SPF and Why Does It Matter?
SPF (Sender Policy Framework) is a DNS record that tells inboxes which servers are allowed to send email on behalf of your domain.
- For MAIL FROM masking, SPF must be set on `mail.yourdomain.com`
- For spoof-style masking, SPF should be set on your root domain (`yourdomain.com`) and include Amazon's servers
Adding SPF improves your trust rating and helps prevent spoofing - even if MAIL FROM is not used.
---
#### Summary
**โ
MAIL FROM masking**
*Pros:* Best deliverability and full alignment
*Cons:* Can't be used if `mail.` subdomain is already in use for receiving mail
**โ ๏ธ Spoof-style masking**
*Pros:* Easier setup, no MX conflict
*Cons:* Slightly lower trust, reveals SES, fails DMARC alignment
---
If you're not using `mail.` for anything else, we strongly recommend setting up MAIL FROM masking. But if your organisation already uses `mail.` for receiving email (e.g. MX records), spoof-style masking is your only option - and it still works well for most cases.
[.svg "CrowdComms Logo")](https://www.crowdcomms.com/)
[mailto:email@email.com](mailto:email@email.com)
Copyright ยฉ 2026, CrowdComms