Strategies to Improve Feedly Newsletter Deliverability and Security

Feedly newsletters are an essential tool for many teams to stay informed and connected. However, there have been various challenges reported regarding the delivery and reception of these newsletters. To address these issues, Feedly has provided some recommendations to help mitigate them.

Currently, Feedly newsletters are sent from enterprise AT feedly DOT com via an email client called Postmark. To ensure the authenticity and security of these emails, Feedly uses three email authentication protocols: SPF, DKIM, and DMARC. These protocols are crucial in preventing email fraud, verifying sender identity, and ensuring legitimate emails are delivered while blocking fraudulent ones.

One common issue that users have encountered is that Feedly newsletters end up in the spam folder or are not received at all. This may be due to the recipient’s email server not trusting Feedly’s domain. To improve deliverability, it is recommended to add both the sender address (enterprise AT feedly DOT com) and the return path (pm_bounces AT pm-bounces DOT feedly DOT com) to the safe senders list and validate the SPF, DKIM, and DMARC protocols.

Additionally, some teams have inquired about removing the “external tag” from Feedly newsletters. To do this, users can request their IT team to add Feedly’s domain to the allow list. If changing the sender address to your own domain is preferred, Feedly is willing to assist in the process.

By following these recommendations and utilizing the available resources, teams can enhance the efficiency and reliability of Feedly newsletters for better communication and collaboration.