Amazon's AWS Simple Email Service integration

Amazon's AWS Simple Email Service integration - Rye

If you are working on IT solutions in this day and age, there is a big chance you will get to use at least some of Amazon's AWS services. They are best known for their elastic compute cloud (EC2) and simple storage service (S3), but they offer more than 30 other services, from email, notifications, queues, archiving, machine learning and various databases.

Their simple email service (SES) is one of the most battle tested and cost effective solutions for sending email messages out there. To me, the most important feature is that they offer bounce and complaint parsing and notifications, that you can, through their another service (SNS) connect back to your app.

SES doesn't allow creation of emails with attachments directly through their API. In case of an attachment, you needed to generate raw email payload on your end.

This looses a lot of benefits of an API, because you are back to various arcane encodings, mime parts and similar problems. If you live in a country that needs more than 127 bits to represent their letters, you usually search for a very solid email composition library at this point. And even that can get problematic results in some (again arcane/legacy/local) email (web)clients.

Luckily Go has a very solid email composition library (gomail), and I already integrated it in Rye a while ago so Rye could sent emails through regular SMTP servers. Now I've started integrating AWS's official Go library, first step is SES, next will be SNS.

Below, you can see example where we use gomail and SES, to send raw email with a PDF attachment, and the resulting email.

Here is a similar example in Python for comparison (link):

Rye code is going through a little of reorg right now. More external bindings, like AWS for example, will get their own folder (contrib) and this will also be it's own github repository. Anyway .. follow us on Github.

Komentarji

Priljubljene objave iz tega spletnega dnevnika

Less variables, more flows example vs Python

In the last blogpost ( Less variables, more flows ) I wrote a quick practical script I needed. It was an uncommon combination of CGI, two GET requests with Cookies and a POST request with Authorization header. I really like practical random/dirty problems, rather than ideal - made up problems to test the language. To get a sense of comparison I rewrote the example 2 times while removing specific Rye features. But that comparison is meaningless to a person that doesn't know Rye or at least Rebol already. So I went on fiverr and made a request for a Python script with these requirements. I got a nicely written Python script that uses functions for each step. To be more comparable, I rewrote the Rye code to a similar structure. Below is the result ... For a next step, it would be interesting, to extract a little simpler example out and add error handling. With Rye-s specific failure handling, I think the difference would become even greater. You can find Rye on github .

Preberite več

Ryelang - controlled file serving example and comparison to Python

This is as anecdotal as it gets, but basic HTTP serving functions in Rye seem to be working quite OK. They do directly use the extremely solid Go 's HTTP functions, so that should be somewhat expected. I made a ryelang.org web-server with few lines of Rye code 3 months ago and the process was running ever since and served more than 30.000 pages. If not else, it seems there are no inherent memory leaks in Rye interpreter. Those would probably show up in a 3 month long running process? And now I got another simple project. I needed to make a HTTP API for some mobile app. API should accept a key, and return / download a binary file in response if the key is correct. Otherwise it should return a HTTP error. So I strapped in and created Rye code below. I think I only needed to add generic methods stat and size? , all other were already implemented, which is a good sign. Of course, we are in an age of ChatGPT, so I used it to generate the equivalent Python code. It used the elegant

Preberite več

Receiving emails with Go's smtpd and Rye

This goes a while back. At some project for user support, we needed to receive emails and save them to appropriate databases. The best option back in the day seemed project Lamson . And it worked well ever since. It was written in Python by then quite known programmer Zed Shaw. It worked like a Python based SMTP server, that called your handlers when emails arrived. It was sort of Ruby on Rails for email. We were using this ever since. Now our system needs to be improved, there are still some emails or attachments that don't get parsed correctly. That isn't the problem of Lamson, but of our code that parses the emails. But Lamson development has been passive for more than 10 years. And I am already moving smaller utilities to Rye. Rye uses Go, and Go has this nice library smtpd , which seems like made for this task. I integrated it and parsemail into Rye and tested it in the Rye console first. Interesting function here is enter-console , that can put you into Rye console any

Preberite več

ryelang

Preišči ta spletni dnevnik