XES allows for three different methods of email authentication: DKIM, SPF and DMARC.
XES users can choose to use one, two or all methods, depending on the level of authentication they wish to achieve.
Below is a short explanation on how the implementation of these methods works in XES.
● DomainKeys Identified Mail (DKIM) is a standard that allows senders to sign their email messages with a cryptographic key. Email providers then use these signatures to verify that the messages weren't modified by a third party while in transit. Using DKIM in XES, the email client server can verify that the email was sent from the expected domain/address.
● Sender Policy Framework (SPF) is an email validation standard that is designed to prevent email spoofing. Domain owners use SPF to tell email providers which servers are allowed to send email from their domains. In this way, email client servers can verify that the email was sent through AWS servers.
● Domain-based Message Authentication, Reporting and Conformance (DMARC) is an email authentication protocol that uses SPF and/or DKIM to detect email spoofing. In order to comply with DMARC, messages must be authenticated through SPF, DKIM, or both. An example of a policy that can be set up with DMARC can be Quarantine 25% of the emails that failed authentication by sending them to the Spam folder.
To set up email authentication methods, contact Support.
In Amazon SES, a verified identity is a domain or email address that you use to send email. Before you can send an email using Amazon SES, you must create and verify each identity that you're going to use as a "From" address. Verifying an identity with Amazon SES confirms that you own it and helps prevent unauthorized use.
XES uses the Simple Mail Transfer Protocol (SMTP) to send email. Because SMTP does not provide any authentication by itself, spammers can send email messages that claim to originate from someone else, while hiding their true origin. By falsifying email headers and spoofing source IP addresses, spammers can mislead recipients into believing that the email messages that they are receiving are authentic.
Domain-based Message Authentication, Reporting and Conformance (DMARC) is an email authentication protocol that uses Sender Policy Framework (SPF) and DomainKeys Identified Mail (DKIM) to detect email spoofing and phishing. In order to comply with DMARC, messages must be authenticated through either SPF or DKIM, but ideally, when both are used with DMARC, you'll be ensuring the highest level of protection possible for your email sending.
You can read more about it in this article: Complying with DMARC authentication protocol in Amazon SES - Amazon Simple Email Service.
If you need help in setting up email authentication on your domain, please contact Support.
In the Circle email touchpoint you can verify the email address. You can also verify it in the Delivery Providers setting in uProduce.
For more information, see Verifying the Sender’s Address.
Email support@xmpie.com with the domain name that requires verification. XMPie support will start the verification process and provide DKIM, SPF and DMARC records as required.
Note: Support will not add domain records to the customer’s DNS. This must be done by the customer who administers the domain. Support will provide guidance and files as needed.
Domain-based Message Authentication, Reporting and Conformance (DMARC) is an email authentication protocol that uses Sender Policy Framework (SPF) and DomainKeys Identified Mail (DKIM) to detect email spoofing and phishing. In order to comply with DMARC, messages must be authenticated through either SPF or DKIM, but ideally, when both are used with DMARC, you'll be ensuring the highest level of protection possible for your email sending.
You can read more about it in this article: Complying with DMARC authentication protocol in Amazon SES - Amazon Simple Email Service.
If you need help in setting up email authentication on your domain, please contact Support.
After the fulfillment process and the account set up, the Support team conducts minimum setup for the customers. These are the steps the Support team will provide.
Basic setup
● Set up the following components in uProduce:
– Delivery provider setup
– AWS server control
– Sender address and verification process
● Circle verification:
– Check that Circle is connected correctly to the XES account added to uProduce (system and email account).
– Check the following:
§ Review email touchpoint settings
§ Review email body in order to adhere to "easy unsubscribe requirements"
§ Add a new sender to a touchpoint from the Circle UI
● Increase send rate. This will be done upon request (pending AWS approval).
● Domain verification and authentication (SES dashboard, up to 10 domains per account):
– Verification of the domain – allows to use all email addresses in the domain as From EMAIL.
– Setup authentication using DKIM.
– DMARC set up – Support will send DKIM authentication CNAME entry to the customer (support provides only the TXT records to be included by customer in the DNS).
– After the customer completes the CNAME entry update in the DNS, support will make sure customer’s identity status is marked as verified.
● Additional domains: basic setup for additional 10 domains (up to 10 domains, if more domains are needed the Support team will approve payment).
● Additional services:
– SPF (support provides only the TXT records to be included by customer in the DNS).
– Custom MAIL FROM domain (SES Dashboard) – complaints and hard bounce are not tracked by XMPie system. Customer will have to sign a document which approves taking responsibility for complaints and bounces. Analytics will not be provided also.
Notes:
● To comply with Yahoo and Gmail regulations you will need one of the DMARC or SPF, both are not required. SPF comes with mandatory MAIL FROM customization. This is not fully supported by XMPie. XMPie recommends our customers to add DMARC.
● Support will not be adding domain records to the customer DNS. This must be done by the customer on his side, support will provide guidance and files if needed.
Additional account
● 200$ annual payment, in addition to maintenance payment.
● Additional account to the same plan to ensure insulation of the reputation and manage each of their customers separately.
● Domain basic setup will be provided to up to 3 domains.
● ASP – will be provided to 10 additional domains. Can be distributed between accounts.
Dedicated IP
● 1,500$ annual payment, in addition to maintenance payment.
● The send rate for the IP is 40 emails per second. Increasing this rate will be done by additional IP purchase.
● No need for the 175K minimum sends.
You’ll need to pay extra for:
Additional domain authentication – the basic includes up to 10 domains per account. Additional domain authentication will be charged separately by the Support team.
● Dedicated IP
● Additional account:
– Additional account for the same plan to ensure insulation of the reputation and manage each of their customers separately.
– Domain Basic setup will be provided to up to 10 domains.