API keys and authentication: Email Authentication

Last Updated: Jan 20 2015 09:30 am UTC

Download document

Email authentication is needed to verify email sender identity and to confirm an email has been sent from the right source, which is listed as a sender.

You can set up domain authentication in your account, in section "Email Authentication".

“From: Company X [info=deliverability.com@mlgnsrv.com] on behalf of Company X [info@deliverability.com]”. When you use Mailigen to send an email campaign and your own email address has been validated, your recipients will receive your email address shown in the “From” line, not the Mailigen server domain.

Note: To authenticate your domain correctly you must enter only the name of your domain.

Correct: mailigen.com

Wrong: www.mailigen.com


Authentication was successful if SPF, DKIM and Sender ID were marked "Verified".

You need to authenticate your email in order to authorize/approve the campaign to be sent from your email address with Mailigen server entries, which will be later identified by the receivers in Gmail, AOL, Hotmail, Yahoo and MSN.

All major Internet and email service providers (later- ISP) use email authentication data to protect themselves against spam.

You can learn more about advantages of authenticated email domain in our blog articles "How to Improve Email Delivery to Gmail?" and "If You Send Emails from Public Domains, Agree with the DMARC Policy".