It is incredibly common to start a new organization, project, or business using a free email address like yourbusiness@gmail.com. However, when transitioning to a professional communications platform like Envoke, you cannot use a free email provider as your sender address. To send emails through our platform, you must use a custom domain that you or your IT team personally own and control (for example, newsletter@yourdomain.com).
Here is a breakdown of why this restriction is in place, the technical reasons behind it, and how to resolve it.
1. The Core Reason: Domain Authentication
To ensure your emails successfully reach recipient inboxes instead of landing in the spam folder, Envoke requires you to verify your sender domain.
Inbox providers (like Google, Microsoft, and Apple) are heavily focused on fighting spam and phishing. When an email arrives, they check to see if the sender is actually authorized to send messages on behalf of that domain. We require domain verification so you can prove to these providers that you are a legitimate sender.
2. The Technical Roadblock: DNS Access
The mandatory domain verification process involves adding specific technical authentication records (known as SPF, DKIM, and DMARC) to your domain's DNS (Domain Name System) settings.
Because you do not own domains like @gmail.com or @yahoo.com, you do not have administrative access to their DNS settings. Without the ability to modify these settings, the domain cannot be authenticated to send messages through Envoke.
3. Strict Inbox Provider Policies (DMARC)
Even if platforms allowed you to send bulk email from a free domain, the emails would not be delivered. Major providers like Yahoo and Google have strict security policies in place. If an email claims to be from an @yahoo.com or @gmail.com address, but it is actually sent through a third-party marketing platform instead of Yahoo or Google's native servers, the receiving inbox will automatically reject it or flag it as dangerous spam.
Common Free Domains That Cannot Be Used
This rule applies to all free email services and Internet Service Provider (ISP) domains. Examples of unsupported domains include, but are not limited to:
@gmail.com
@yahoo.com
@hotmail.com
@aol.com
@outlook.com
@icloud.com
@mail.com
@protonmail.com
ISP domains (e.g., @telus.com, @comcast.net, @rogers.com)
The Solution: What You Need to Do
To send messages from Envoke, you will need to switch to a custom sender domain.
Register a Custom Domain: If you don't already have one, you will need to purchase a domain name (e.g.,
yourorganization.com) through a registrar like GoDaddy, Namecheap, or Google Domains.Set Up Email Hosting: Set up an active email address attached to that domain (e.g.,
info@yourorganization.com) using a service like Google Workspace or Microsoft 365.Add and Verify in Envoke: Add this new custom email address as your sender in Envoke. We will provide you with the necessary DNS records.
Update Your DNS: Provide these records to your IT team or webmaster so they can add them to your domain's DNS host, officially verifying your domain.