Elastic Email FAQ
What is email authentication, and why does it matter?
Email authentication verifies that emails sent on behalf of your school are legitimate, ensuring better deliverability and reducing the risk of emails being marked as spam. Schools use three key authentication methods: SPF, DKIM, and DMARC.
What is SPF, and why do we need to update it?
SPF (Sender Policy Framework) is a security measure that ensures only authorized mail servers can send emails on behalf of your domain. Without updating your SPF record to include Elastic Email, emails sent through our system may be marked as spam or rejected.
How do we update our SPF record?
- Locate your existing SPF record in your DNS settings.
- If you have an SPF record, add: include:_spf.elasticemail.com before the final all.
- If you don’t have an SPF record, create a TXT record with: v=spf1 include:_spf.elasticemail.com ~all.
- Save the changes and allow up to 48 hours for them to take effect.
What is DKIM, and how does it help?
DKIM (DomainKeys Identified Mail) adds a digital signature to your emails, verifying their authenticity and preventing tampering. This improves deliverability and ensures that emails appear trustworthy.
How do we set up DKIM for our domain?
- Create a new TXT record in your DNS settings.
- Use api._domainkey.YOURDOMAIN.com as the record name.
- Enter the DKIM key value provided by Elastic Email.
- Save the record and allow up to 48 hours for propagation.
What is DMARC, and do we need it?
DMARC (Domain-based Message Authentication, Reporting & Conformance) instructs email providers on how to handle messages that fail SPF or DKIM authentication. While not required, it adds an extra layer of security and visibility.
How do we set up a DMARC record?
- Add a TXT record to your DNS with the name _dmarc.YOURDOMAIN.com.
- Use this value: v=DMARC1; p=none; rua=mailto:dmarc@YOURDOMAIN.com.
- Save the record and allow time for propagation.
What if our IT team is unfamiliar with these settings?
We recommend sharing this guide with them. If further assistance is needed, we’re happy to schedule a call with your IT team to walk through the setup.
How do we verify that the changes were made correctly?
After updating your DNS settings:
- Confirm changes with your IT team.
- Wait 24-48 hours for DNS propagation.
- We’ll send a test email to verify proper authentication.
What if we encounter issues?
- If SPF errors occur, ensure there are no duplicate all mechanisms.
- If DKIM verification fails, double-check that the record name and value match Elastic Email’s requirements.
- If your domain fails verification, wait 48 hours and try again.
Setting up email authentication ensures that students receive important communications without deliverability issues. If you have any questions, contact your CSM, we’re here to help!
For more detailed information on these steps, review our article on Email Deliverability and Authentication Requirements.