![]() ![]() Your email should absolutely have a subject and a body.Mail clients will often automatically classify your email as spam if you don't comply. The easiest to fix (it may already be OK on your app), but also the most important. Many factors determine if your email will be considered suspicious, let me cover the most important ones. This first mark is terrible, but you can fix it using the tips given by the website! Just send a test email to the address they give you, and it will analyze the likelihood of your message being well received. When sending a user receives an email, there are many factors at stake, that will determine if the email ends up in the mailbox or in the spams.ĭuring my experience developing an email-sending service, I discovered mail-tester: a great tool to evaluate the probability of emails ending up in a inbox. Make sure you don't end up in your users spams But will your users receive them in their inbox? Probably not all of them if you don't customize your configuration a bit.Ģ. Great! You are now sure that your mails will be sent □. It will trigger an alarm if bounce rate breached 4% during the last 30 minutes:Įnter fullscreen mode Exit fullscreen mode Quick example of alarm configuration that could be used to monitor bounce rate. It will allow you to identify faster where problems are coming from, and possibly shut down only parts of your messaging infrastructure if needed. Let me advise you to create a configuration set linked to the SES Identity you send emails from, and monitor it specifically. Allowing you to either monitor your whole accounts reputation, or the reputation linked to specific SES identities. These cloudwatch alarms can be set up at account level or configuration set level. Set up alarms to be warned before its to lateĬloudwatch alarms can be set up to monitor both the bounce and complaint rates, and send you notifications / take actions when they reach a dangerous level. To prevent all this bad stuff from happening to you, here are two of my personal tips: Obviously, you don't want your account to be blacklisted, but I would also advise you to act before being put under review. ❌ Over 0.5% complaint rate, you will be prevented from sending emails until investigation.□ Over 0.1% complaint rate, your SES account will be placed under review by AWS.❌ Over 10% bounce rate, you will be prevented from sending emails until investigation.Ĭomplaints: events that happen when your recipient manually reports your emails as undesired (basically spam).□ Over 5% bounce rate, your SES account will be placed under review by AWS.In order to monitor this sender reputation, two metrics are mostly used :īounces: soft bounces are events happening because of a temporary issue (like recipient mailbox full), hard bounces happen because of permanent ones (like a non-existing recipient address). It may seem trivial but AWS enforces strict rules that may affect the sender reputation attached to your domain. Maintain your sender reputation with AWSįirst step on your way to success is to make sure that your emails are even sent to your recipients. There is a lot of content, and no specific order, if one of the issues is more important than the others, do not hesitate to read it's part first and tackle it quick!ġ. This article tries to bring solutions to these three problems, that are simple and easy to implement. □ Your emails will probably look bad on some clients (⚠️ gmail is one of them!), or not display at all in some cases, for security reasons.□ Your emails will probably end up in some of your users spams.□ You will be prevented from sending messages if your sender reputation goes down.Using only minimal configuration to send your emails: □ □ □ Three obstacles on your road to clean email communicationĪ few months ago, I went through the implementation of transactional emails sending on the project I was working on, and identified three major pitfalls that every developer should be aware of (these pitfalls are also relevant when sending promotional emails!). Let me guide you through three of these issues and help you design beautiful emails that never end up in your users spam. However, this ease of use comes at the price of potential mistakes and pitfalls that can happen at every step of your coding journey. Coupled with the AWS SDK and Lambda functions, it allows you to programmatically send emails to your users with minimal setup. Designing responsive emails that display well on every mail clientĪs you may already know, AWS SES offers a great way to send emails with your AWS serverless app.If you have a short timing, cover what seems the most important to you first! This article is structured in three independent parts : three problems and their solutions. This article assumes the reader has basic knowledge of AWS SES (Simple Email Service), like being able to send simple emails using SES and Lambda or to verify an identity. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |