In the reputation dashboard, SES tracks your bounce rate and complaint rate, and has the following notice about bounce rates:
#INSTAPAPER SEND TO EMAIL FULL#
We open sourced the SQS worker and task we implemented to process bounce and complaints events on GitHub if you’re interested in the full code. Lastly, I created the SQS queue workers to read the SES events, and store the bounced information with a user’s email settings. Next we add the bounced column to our object model. First step is to store the bounced information in a user’s email settings:ĪLTER TABLE email_settings ADD COLUMN bounced TINYINT(1) DEFAULT 0, ALGORITHM=INPLACE, LOCK=NONE Storing the bounce information is a bit of extra overhead for Instapaper to track, but ultimately more efficient and the bounce information can be used elsewhere. We never previously tracked bounced emails directly in Instapaper since Mailgun stores bounced emails and prevents duplicate sends to permanently bounced addresses. Bounce, Complaint, Delivery, etc.) to a Simple Notification Service topic, which can then send messages to Simple Queue Service to be consumed by your application: SES allows you to send email events (e.g. In order to send to any email address, not just a verified email address, you need to both verify a domain and handle bounce events. In the above, we added a use_mailgun keyword argument to determine whether to send to Mailgun or SES, then set the argument to False for exception emails. Ses.send_email(sender, recipient, subject, Html=html, attachments=attachments, tag=tag, Recipient=config.EXCEPTION_EMAIL_ADDRESS,ĭef _deliver_email(sender, recipient, subject, text=None, Subject = " Exception: %s" % (server, traceback)ĭeliver(sender=config.INTERNAL_EMAIL_ADDRESS, I then modified some functions as follows:ĭef deliver_exception(traceback, extra='', server=''): In the past, we’ve had fancier ways of handling errors, but I’ve found that getting them emailed directly to me is a cheap, easy, and efficient way to get visibility.Īfter verifying our internal email address for errors in Simple Email Service, I applied for a limit increase to allow me to send 20,000 emails per day which more than covers the volume.
As a result, we finally re-enabled the Weekly email after an almost 2 year hiatus! I open sourced several tools we used for the integration, and I’ll share the steps we took for the migration below… Migrating an Internal Use CaseĪll errors from the Instapaper servers get emailed directly to me. Shortly after the price change, we disabled the Weekly email while taking the steps toward making Instapaper GDPR compliant, but it’s remained off because it was prohibitively expensive to continue operating the email.Īfter a few weeks of work, we are almost entirely migrated onto SES. In 2018, Mailgun changed their email pricing from volume-based to tier-based and, as a result, the cost of sending the Instapaper Weekly nearly doubled. While sheltered in place, I finally had the time to do something I’ve been meaning to do for years: migrate Instapaper’s email service from Mailgun to Amazon’s Simple Email Service (SES).
0 kommentar(er)
