Show HN: Mailready – meet the new email deliverability standards
1–10 of 39 posts
Re: Show HN: Mailready – meet the new email deliverability standards
#2Some of these popped up on Hacker New recently;
- Learn and Test DMARC[1] does a visual breakdown of how email servers communicate, giving you a better understanding of SPF, DKIM, and DMARC and how they work together.
- Mail-Tester[2] - test the spammyness of your emails.
- MECSA[3] is an online tool developed by the Joint Research Centre (JRC)[4] to assess the security of email communication between providers.
2. https://www.mail-tester.com
Re: Show HN: Mailready – meet the new email deliverability standards
#3If you have SPF but not DKIM is that sufficient for deliverability to these providers?
Re: Show HN: Mailready – meet the new email deliverability standards
#4If you have SPF but not DKIM is that sufficient for deliverability to these providers?
For DMARC alignment you need either SPF alignment or DKIM alignment, either one will do. (note that 'alignment' is not the same as an SPF pass).
Which means that you _could_ get away with just SPF alignment, but you wouldn't want to trust on that since SPF is horribly broken and most third party senders don't even bother with SPF alignment anymore. Always focus on DKIM alignment instead.
But if you are now just thinking about this, you're in trouble anyway. If you are sending bulk amounts of email (that is, 5k a day per Google's rules) and you are not yet signing with DKIM, then you are probably not ready for adopting a strong DMARC policy ('quarantine' or 'reject') before Feb 1st.
Email hardening takes time, the larger/more complex your domain is, the more time you probably need to ensure you are DKIM aligned for all your delegated senders. Don't be tempted to just add a DMARC record with p=reject policy, that would be irresponsible and asking for problems (read: undeliverable email).
Re: Show HN: Mailready – meet the new email deliverability standards
#5If you have SPF but not DKIM is that sufficient for deliverability to these providers?
For mail that you're sending yourself, from your own infrastructure (e.g. the envelope-from address matches the header-from address), DMARC + SPF should be sufficient and is easy to implement.
For third parties that are sending on your behalf, you'll likely need DKIM - but that will be implemented on their side, and all you'll have to do is add the DNS record they give you.
Re: Show HN: Mailready – meet the new email deliverability standards
#6"Send reconfirmation emails to people that have not interacted with your email (no opens or clicks)"
How can I check opens? I'm not aware of any reliable way to check this. Mail clients not loading pixels means the software is unaware of opens?
Re: Show HN: Mailready – meet the new email deliverability standards
#7Re: Show HN: Mailready – meet the new email deliverability standards
#8Basic XSS - https://mailready.info/authentication?domain=grepular.com
Thanks for this. Will fix.
Re: Show HN: Mailready – meet the new email deliverability standards
#9"Send reconfirmation emails to people that have not interacted with your email (no opens or clicks)" How can I check opens? I'm not aware of any reliable way to check this. Mail clients not loading pixels means the software is unaware of opens?
Maybe because they click a link in the confirmation email?
Re: Show HN: Mailready – meet the new email deliverability standards
#10"Send reconfirmation emails to people that have not interacted with your email (no opens or clicks)" How can I check opens? I'm not aware of any reliable way to check this. Mail clients not loading pixels means the software is unaware of opens?
Same way as always, image loading. If image URLs are unique and external then you can track their opening. Not all users will allow it so you also track clicking on in email links.