Sending Amazon SES API attachments versus SMTP

Question

When reviewing Amazon SAS API documentation, there seems to be no clear way to send attachments unless you have created a raw email. Where, as when using the SMTP client for Amazons, SES sending emails with attachments looks more manageable. Beyond the message returned from the SES API, is there any benefit from using api through an SMTP client? Or am I completely missing the boat, and is there a simple implementation of adding email attachments in the SES API?

Answer 1

I use SES all the time, never felt the need to use anything other than the SMTP interface, which is a simple replacement for any other SMTP service that you can use. Unless you have a good reason (and I can't think of one), use the usual old SMTP method. Then, if you ever need to move, it would be trivial to switch to another service.

Answer 2

Well, the main reason for using api is that you can set a domain key to increase delivery efficiency. This is useful if you send a huge number of letters. In general, if you don’t have an easy way to implement api (like django-ses or the like), just use SMTP.