IMPORTANT: Effective February, 2024, Google and Yahoo will have new requirements for bulk email senders on their platforms. Learn about the new requirements and what you have to do in New Bulk Sender Requirements.
To begin the DKIM authentication process for your sending domains, access the Admin interface and navigate to:
- Settings > Setup > Email Authentication.
Enter your account sending domain into the text field and click GET INSTRUCTIONS for customized DNS instructions.
NOTE: These steps are typically completed by your DNS admin or IT professional, so it is recommend they have access to log in to your account.
After the CNAME records are added to your DNS, return to the Email Authentication page to run a test.
NOTE: The configuration won't be completed until the authentication test passes in your account.
Click TEST to see if the domain has passed authentication. If so, you'll see a message indicating the domain has passed the authentication test. The domain will then be added to the list on that page which can be deleted or retested if any changes are necessary.
NOTE: If the authentication test indicates that the domain has failed, try the troubleshooting steps in CNAME Troubleshooting for DKIM.
You can follow the above steps for additional domains that will be used to send through your account. You will see each of the active/authenticated domains listed in your authentication settings.
If there is more than one account (child accounts) being used to send mail, you have the option of either making the parent account the default manager for DKIM entries or allow each child account to add and make changes to domains sent through their account. If you make the parent account the default, then email authentication settings will be used across all child accounts and only the parent account will have the rights to make changes.
SPF is configured on the bounce address "informz.net", so no additional steps are necessary. However, you could add "include:informz.net" to your existing SPF record for receivers still checking SPF on the "from" address (i.e., Sender-ID which is deprecated).
See the SPF & Sender ID topic in Sender Authentication to learn more.