skip to content »

inbasys.ru

Validating and tracking email addresses

validating and tracking email addresses-79

Using your own domain has many advantages and Elastic Email requires it if you wish to send more than 50 emails a day.This is a step by step guide to getting your domain verified on your Elastic Email Account. An SPF record is in place to identify which mail servers are authorized to send mail for a given domain.

validating and tracking email addresses-59validating and tracking email addresses-39validating and tracking email addresses-89validating and tracking email addresses-44

The only reason why you would change or add an MX record for use with Elastic Email is if you are using Inbound Email Notifications which are webhooks that are part of our HTTP API.A DMARC policy allows a sender to indicate that their emails are signed by SPF and DKIM and tells a receiver what to do if neither of those authentication methods passes – such as junk or bounce the email.DMARC removes the guesswork from the receiver’s handling of these failed emails, limiting or eliminating the user’s exposure to potentially fraudulent & harmful emails.Further, a DMARC policy on your domain(s) will affect all of your email sending from that domain (not just the mail you are sending through Elastic Email) so you need to ensure you are using SPF and DKIM for all your email delivery. The following are example DMARC TXT entries to setup on your domain(s) DNS.Option 1- Setup your DMARC policy to simply notify you of mail that is not passing SPF and DKIM Host/Name:_dmarc Value: v=DMARC1;p=none;pct=100;rua=mailto:[email protected];ruf=mailto:[email protected] 2- When you are no longer receiving negative reports, change your DMARC policy to quarantine which will not necessarily bounce email, but indicate to the recipient server they should consider quarantining it (junk or spam folder).DMARC also provides a way for the email receiver to report back to the sender about emails that pass and/or fail DMARC evaluation.

Note there is no specific configuration needed in Elastic Email besides ensuring that your SPF and DKIM are both valid.

This is OK - it is not required and all it means is that you do not currently have a mail server setup for your domain. If there is no default domain set, and an email is sent from a non-verified domain then is used.

Also, if a default domain is set, then sub-accounts will inherit the ability to use the default verified sender domain on the main account.

To do that we must rewrite links and use web pages.

Setting up a "tracking domain" brands these rewritten links and pages with your own domain. Enter: Host/Name: tracking Value: api.*Elastic Email system will look for either "tracking" or "email" automatically.

In some DNS settings the Host/Name field may require you to enter "api._domainkey.yourdomain.com", replacing your domain with your actual domain.