How to avoid delivery issues with Feedly Newsletters
Tips and tricks to avoid spam or delivery issues with Feedly newsletters.
How to avoid delivery issues with Feedly Newsletters
Tips and tricks to avoid spam or delivery issues with Feedly newsletters
- How Feedly newsletters are sent today
- How to fix the spam folder issue
- How to remove the external tag from Feedly newsletters
- Changing the internal sender address from Feedly to your own domain
- Resources
Several of you have reached out to us asking how to avoid spam or delivery issues with Feedly newsletters. This short article is meant to give you some recommendations that we’ve given to dozens of teams and that helped them mitigate the issue.
How Feedly newsletters are sent today
- Feedly newsletters are sent from enterprise AT feedly DOT com via an email client called Postmark.
- We use 3 email authentication protocols: SPF, DKIM and DMARC. SPF identifies valid sending servers, DKIM verifies message integrity, and DMARC provides policy and reporting for both. Those three protocols are critical in preventing email fraud. They help verify sender identity, prevent phishing attacks, and provide visibility into email activity, ensuring that legitimate email is delivered while fraudulent email is blocked.
How to fix the spam folder issue
The most common issues we have heard is that either Feedly newsletters land in the Spam folder or that the recipients do not receive them.
This might be happening because your email server does not trust our domain. The sender address of our Feedly newsletters is enterprise AT feedly DOT com, and the return path of our email is pm_bounces AT pm-bounces DOT feedly DOT com.
Different email servers will look at one or the other, so the best way to improve the deliverability of Feedly newsletters is to ask your IT team to add both email addresses to their safe senders list. Your company can trust our domain if the following protocol tests are valid: SPF, DKIM and DMARC.
How to remove the external tag from Feedly newsletters
Finally, some teams asked how to remove the “external tag” in the newsletter header. To do so, you’d need to ask your IT team to add Feedly domain to your allow list. With our email security protocols (SPF and DKIM), it’s very unlikely you get spoofed. This source will help: https://www.alitajran.com/add-tag-to-external-emails-in-microsoft-365-for-extra-security/.
Changing the internal sender address from Feedly to your own domain
If you wish to change the sender address from enterprise AT feedly DOT com, to your own domain, we’d be happy to help. To do so, please reach out to us so we can set up some time between your IT team and our team and discuss next steps.
Resources
What's Your Reaction?
