Email trifecta: SPF, DKIM, and DMARC with AWS SES
To be honest, based on my experiences, sending email is hard. Sometimes the email we expect goes to inbox, it is not. Internet is a weird place we love. For this reason, I am delegating email wroks to 3rd party, like AWS SES. But's also not like simple setup for using it. Whenever setup email on AWS SES, basically we need to setup: Create configuration set Verify domain ownership Setup correct SPF, DKIM, and DMARC Configuration set Think of a configuration set as a "sending profile" for your emails. By default, when you send an email with SES, it's like sending it into a black box. You know it was sent, but you don't know what happened next. Did it get delivered? Did it bounce? Did the user mark it as spam? A configuration set allows you to apply a specific set of rules and, most importantly, get detailed feedback on the outcome of your emails. For example: noreply email . With noreply email , you're not expecting a reply, but you abso...