Custom domain email forwarding, explained.
Bring messages sent to support@yourproduct.com into an inbox you already use. Receiving and replying need separate setup.
What forwarding does
An email forwarding service receives mail for an address on your domain and delivers it to a verified destination. Your website can stay with its current host: website hosting and mail routing use separate DNS settings.
Start with ownership and the destination
Prove that you control the product domain, confirm the destination inbox and inspect existing MX records. SimplerEmail’s current build supports these setup checks. Its receiving and sending transport has not been connected yet.
Forwarding is different from replying
Reading a forwarded message does not authorize Gmail or Outlook to send as your product. A branded reply needs its own verified sending path. Google says Gmail support for third-party Send As addresses ends in January 2027, so plan for a verified web reply or a separately tested reply proxy.
Keep existing email working
MX records apply to the domain or subdomain, rather than one support address. Replacing an existing provider’s MX can interrupt every address on that domain. Consider a test subdomain, forwarding from the existing provider or a staged migration.
Compare the complete service
Look at verified-domain limits, forwarding allowance, active sends, reply identity, attachment sizes, retention and delivery-failure handling. Free forwarding is different from a free hosted mailbox with its own storage and login.