Amazon SES Migration Guide - Pepipost

Amazon SES Migration Guide

May 4, 2017

Amazon SES stands very good on the benchmarks of scalability and reliability. If you are looking to move from traditional email delivery channels to smart ones that not just deliver your emails promptly to the inbox but also give you deep insights on your customer behaviour and email activities, its time you switched to Pepipost.

Unlike many other email delivery services that claim to have millions of customers and delivering billions of emails, Pepipost’s focus is on building the cleanest reputable email networks. We do not compromise quality over quantity. So you never have to worry on which IP space you’re in and what is the reputation of email infra.

When you switch to Pepipost, you can track every granular information that gives you more insights on your user engagement like –

• who all opened the email
• which links are being clicked and by whom
• the IP address and User Agent of the recipient
• who all requested to unsubscribe or marked the email as spam

If you are a current user of Amazon SES, then you might be either sending email using your EC2 instance by connecting it with Amazon SES SMTP or API.

Whether you are integrated with Amazon SES via SMTP or API, this guide provides you the steps to easily migrate to Pepipost.

 

Migrating from Amazon SES SMTP to Pepipost:

In case you are using Amazon SES via SMTP calls, then migration is quite simple. Here are the steps:

  1. Signup to Pepipost and get your account activated by clicking on the activation link received over email.
  2. Configure and get your sending domain approved.
  3. Go to Settings and copy Pepipost SMTP credentials.
  4. Open your application (CRM, backend app, website, Sendy or any other plugin) which generates email.
  5. Navigate to their Email/SMTP settings tab and just replace the set Amazon SMTP settings with the copied Pepipost settings.

An example of new settings:
Hostname: smtp.pepipost.com
Port: 25, 587 or 2525
Sender email address: something@mydomain.com

As mentioned earlier, the @mydomain.com is the sender domain and hence prior to sending email this needs to be configured and approved under Pepipost account.

Migrating from Amazon SES API to Pepipost:

Unlike Amazon SES, the API setup process at Pepipost is easy and straightforward. In Amazon you might have struggled settings up the EC2, installing the AWS Access Key, validating the test email recipients and finally the SDK/code changes. But here at Pepipost you just need the API key and SDK and you are all done.

As you are integrated with Amazon SES using APIs, you might be familiar with the terms like –
[‘Action’]
[‘Source’]
[‘Destination’][‘ToAddresses’]
[‘Message’][‘Subject’][‘Data’]
[‘Message’][‘Body’][‘Text’][‘Data’]

Here are the Pepipost equivalent parameters for the above:

Amazon SES Equivalent Pepipost parameter Description
[‘Action’] NA In case of SES, Action=SendEmail, but in Pepipost Action parameter is not required as in the base URL itself it is pointing to sending email. i.e. https://api.pepipost.com/api/web.send.json
[‘Source’] from This is the sender email address. e.g.something@mydomain.com. Here the @mydomain.com needs to be configured and approved in your Pepipost account.
Destination.ToAddresses.member.1
Destination.ToAddresses.member.2
Destination.ToAddresses.member.3
“recipients”: [
recipient1@gmail.com“,
recipient2@yahoo.com“,
“recipient3@hotmail.com”,
]
These are the set of recipient email addresses on which you want to send the email.
[‘Message’][‘Subject’][‘Data’] subject Subject of the email
[‘Message’][‘Body’][‘Text’][‘Data’] content The body content of the email

====================================================
POST Examples for Amazon SES Email Sending API

POST / HTTP/1.1

Host: email.us-west-2.amazonaws.com

Content-Type: application/x-www-form-urlencoded

Action=SendEmail

&Source=user%40example.com

&Destination.ToAddresses.member.1=allan%40example.com

&Message.Subject.Data=This%20is%20the%20subject%20line.

&Message.Body.Text.Data=Hello.%20I%20hope%20you%20are%20having%20a%20good%20day.

&AWSAccessKeyId=AKIAIOSFODNN7EXAMPLE

&Signature=RhU864jFu893mg7g9N9j9nr6h7EXAMPLE

&Algorithm=HMACSHA256

POST Examples for Pepipost Email Sending API

POST / HTTP/1.1

Host: https://api.pepipost.com/

Content-Type: application/x-www-form-urlencoded

POST /api/web.send.json HTTP/1.1

{

"api_key": "string",

"email_details": {

"fromname": "yourfromname",

"subject": "this is test email subject",

"from": "from@example.com",

"content": "

hi, this is a test email sent via Pepipost JSON API.
 
"

},

"recipients": [

"recipient@example.com"

]

}

Note: Before running your first test email through Pepipost API, you need to ensure that the domain example.com is configured and approved under your Pepipost Account.

Just pick any of your favorite SDK from below and get started with Pepipost. Explore our complete API documentation.

  • PHP
  • Python
  • Ruby
  • NodeJS
  • NodeJS – Nodemailer
  • Java
  • Perl
  • C#

You can try every endpoint in the Pepipost API right from your browser using our Live API Explorer. There’s no longer a need to run cURL commands in terminal to test things out (though it’s totally fine if that’s your preference).

At Pepipost we believe in keeping things simple and easy. Should you still face trouble migrating from Amazon SES or have any queries, just ping us on our 24X7 live chat support and our developer evangelists will be happy to walk you through the migration process. Alternatively, you may also write to support@pepipost.com.

 

Write a comment

img

Dibya Prakash Sahoo|The Business Guy