<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Newsletters on Lin's Blog</title><link>https://coder.tw/en/tags/newsletters/</link><description>Recent content in Newsletters on Lin's Blog</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Thu, 12 Jan 2017 00:20:59 +0000</lastBuildDate><atom:link href="https://coder.tw/en/tags/newsletters/index.xml" rel="self" type="application/rss+xml"/><item><title>A Simple Approach to Scheduling Bulk Newsletter Sends and Handling Yahoo Deferrals</title><link>https://coder.tw/en/posts/bulk-newsletter-sending-schedule/</link><pubDate>Thu, 12 Jan 2017 00:20:59 +0000</pubDate><guid>https://coder.tw/en/posts/bulk-newsletter-sending-schedule/</guid><description>&lt;p&gt;When you send a large newsletter, have you ever thought about how to send it? Say you have 10,000 addresses. Would you send them all at once, or spread them out over different times? Most people send them all at once, and that&amp;rsquo;s usually fine. If your sender reputation is good and you do this regularly, sending bulk email is normal for email providers, and the messages almost always land in the inbox. But there&amp;rsquo;s one troublemaker: Yahoo. For some reason, if you send too many emails in a short period, they get deferred (temporarily rejected). You can retry, and after a few tries they usually go through. The most I&amp;rsquo;ve seen is one that only got through after being resent 100 times. Looking at the Yahoo situation, it seems that no matter how good your reputation is, you run into deferrals when you send at high frequency in a short time, regardless of content. Here I tried several approaches to solve the problem.&lt;/p&gt;</description></item></channel></rss>