✍️
Emaildelivery.com Documentation
EmailDelivery.com
  • FAQ
    • ✍️FAQ
    • 🎬Explainer Video
    • 🤳Why go self-hosted?
    • 🌋Recommended VPS
    • Ⓜ️Velocity MTA FAQ
    • 🌴Amazon SES production access
    • 👋From the founder
  • Features List
    • 🖌️ESP Features
      • 🟢Pabbly Connect
      • 🪝Event Webhooks
    • 🎨Delivery Features
  • install
    • 🤓Racknerd Installation
    • 👩‍💻Generic VPS Installation
    • 🌊Installation video for Digital Ocean droplets
    • 🧠Advanced Installation
  • Common installation issues
    • 🙅Don't use sudo
    • ✋Bind: address already in use
    • 👬Resolving port conflicts with a second IP
    • 😑Hostinger is your registrar
    • 💪Use the ARM build for AArch64/ARM64 CPUs
    • ⭕Oracle Cloud / Amazon Lightsail: "bind cannot assign requested address 8025"
    • 🔗Links in email messages are doing something unexpected
  • Post Installation
    • 🔺Upgrade instructions
    • 💾Backup and Restore
    • 🐳Docker Information
    • 🪵Logging
    • 🚚Moving to a new server
    • 📇Changing the installation domain
    • 🎟️Reset lost administrator password
    • ♻️How to reinstall
    • 🔑Add our SSH keys for support
  • options for adding https
    • 🔐Free Native SSL via Let's Encrypt
    • 🔐Adding HTTPS to email message links
    • 🔐Cloudflare as SSL proxy
    • 📮Transactional SMTP Relay requirements for Cloudflare
    • 🚧Troubleshooting common SSL issues
    • 🔏Native SSL via ZeroSSL
  • Introduction
    • 👥Backend, Frontend, Customers, Users
    • 🧑‍🏫What you can do in the emaildelivery.com backend
    • 👩‍💻Getting ready to send
    • 🔗Understanding the 'White Label Tracking Link'
    • ⚡Connect SMTP Relay
    • 🔌Connect Mailgun API
    • 🔌Connect Sparkpost API
    • 🔌Connect Amazon SES API
    • 📮Postal Routes
    • 📬Send a test message
  • Common email setup issues
    • 🎭"Unconfigured sending domain" during test message
    • 😶Campaign stats are blank
  • Solutions and guides
    • 🌴Getting approved for Amazon SES production access
    • 🔍Google Postmaster Tools
  • Backend Administration
    • ™️Change your logo and favicon
    • 🖍️Change your colors and theme using Custom CSS
    • 🔓Password reset configuration
    • 🖥️Creating Customer Accounts
    • 💻Creating User accounts
    • 🖼️Create default email templates
    • 📋Create default subscriber form templates
    • 🧹Purging mail queues
    • 👥Logging in to the email marketing frontend
    • ⚙️Frontend Settings
      • Profile tab
      • Broadcast alert thresholds
      • Default send limits
      • Header template
    • 📰Customer broadcast report
    • 🆕Changelog
  • Integrations
    • 🟢Pabbly Connect
    • 🟥Zapier
    • 🪝Event webhooks
    • 🅰️API
    • 🖼️Integrating Pixabay into your email campaigns
    • 🏋️WordPress
  • Advanced postal route configuration
    • 🤹‍♂️Contact list domain routing
    • ⚖️Load balancing
  • Control your sending speed
    • 🚦Domain throttles
  • Transactional
    • 🧾Transactional API
    • 📮Transactional SMTP Relay
    • ✅Transactional SMTP Relay: steps to start sending
    • 📁Transactional templates
    • 🏷️Transactional tags
    • 🧀Use SWAKS for testing and troubleshooting
  • What you need to know before you install Velocity MTA
    • 🚫The ESP Platform IP can't be used with the MTA
    • ☝️PTR Records and Reverse DNS
    • 🧬Sending Domain and PTR must match
    • 🔍Google Postmaster Tools
    • 🔗MTA link domain points to the sending IP, not the ESP IP
    • 🤝How to use Velocity MTA as an SMTP Relay
  • 🚀Velocity MTA BASICS
    • 👨‍💻Getting ready to send
    • 🪵Velocity.log is vital to your success
    • 💽Installing Velocity MTA
    • ⚠️Common installation issues
    • ⭕Oracle Cloud and Amazon Lightsail issues
      • 🧑‍🏫What you can do with an MTA Delivery Policy
    • 🦾Adding a server in the backend UI
      • 🔌Server Connect MTA Tab
    • 🆔Configure DKIM
    • 🧙Creating an MTA Delivery Policy
      • Domains Page
      • Settings Page
      • Deferrals Page
      • Servers Page
      • Pushing MTA Policy Changes
    • 📮Create a Postal Route
    • 📬Sending your first test message
    • 🤖IP Warmup automation
    • 🥺Asking major mailbox providers for a reprieve
  • Velocity MTA Solutions
    • 🔐Adding HTTPS to Velocity MTA email message links
    • 👨‍🏫Adding a new dedicated IP to a customer account
    • 🌡️How to warm up a new IP
    • 🕊️Using Dovecot for IMAP
  • 📚Velocity MTA Continuing Education
    • 😡Complaint Feedback Loops
    • 📊IP Delivery Reports
    • 🚦Mail queue management
    • 📥Incoming email MX server
    • ⚔️Customizing delivery for large mailbox providers
    • 🐳Docker information
    • 🧀Troubleshooting with SWAKS
    • 📋Comprehensive CFL / FBL list
  • Troubleshooting MTA related errors in the email marketing interface
    • ⁉️HTTPConnectionPool Max retries exceeded with url: /settings
  • Troubleshooting common issues in the email marketing interface
    • ⁉️Campaign stats are blank
    • ⁉️Pabbly connection errors
    • ⁉️API connections are failing
    • ⁉️The API docs page is blank
    • ⁉️Form submission says Error
    • ⁉️Images are not displaying
  • What to know before using the email marketing platform
    • 📇Contact lists use a flexible architecture
    • 📋Properties are created dynamically
    • 🆔You can personalize on all properties and in URLs
    • 🚮Unsubscribes, complaints, and bounces are account-wide
    • 🎨Drag and drop, WYSIWYG, raw HTML, and reusing templates
    • 🚦You can throttle your sending for each postal route
  • Contact list management
    • ➕Create a contact list
    • ♻️Resubscribe after an unsubscribe
    • 👓List X-Ray
    • 🏷️Contact Tags Manager
    • ⬇️Export your contact list
    • 🚫Uploading a suppression list
    • ⚠️Large suppression files
    • ⛔Exclusion Lists
    • 🇪🇺GDPR Delete & Export
  • Segmenting
    • 🧑‍🏫What you can do with segments
    • ➕Create a segment
    • 🧱Designing your segment
    • 🏷️Tag contacts in a segment
    • ⬇️Export a Segment's Contacts
    • 🆎A/B test using segments
  • Broadcasts
    • 🧑‍🏫What you can do with broadcasts
    • ➕Create a Broadcast
    • ⚙️Broadcast Settings
    • ⌨️Choosing your email composer
    • 🗣️Augment your subject line with a preheader
    • 📬Adding your recipients
    • ⏲️Schedule your Broadcast
    • 🔂Resend to non-openers automation
    • 📰Broadcast Reporting
    • 👯‍♀️Duplicate a broadcast
    • 🏷️Tag contacts who Open your broadcast
    • 💫Resume an incomplete broadcast
    • ⬇️Export Broadcast Openers & Unsubscribes
    • 🛑Cancel a broadcast
    • 🔗Cancel a broadcast funnel trigger
    • 🔧Revise tagging and funnel triggers for sent broadcasts
  • Using the integrated beefree.io email composer
    • 🦶Editing the sticky footer
  • Using the legacy drag & drop email composer
    • ⌨️The Basics
    • 🛠️Component Section Toolbar
    • 🏛️Designing your email - Using Columns
    • 🦶Footer
    • 🐦Social Media Component
  • Funnels
    • 🧑‍🏫What you can do with funnels
    • ➕Create a funnel
    • 🪆Choosing your funnel type
    • 🆔From Name & From Email - editing
    • ⚡Activating your funnel
    • 🔗Trigger an email funnel from a broadcast
    • 🏷️Tag contacts who open your funnel messages
    • ⌨️Choosing your email composer
    • 🗣️Augment your subject line with a preheader
    • 🤖Design your automated email sequence
    • 🚫Contact Suppression and Exclusion
    • 🖇️Adding a funnel to an opt-in subscriber form
  • Subscriber opt-in forms
    • 🧑‍🏫What you can do with forms
    • ➕Create an opt-in form
    • 2️⃣2⃣ Sending to double opt-in contacts
    • 📋Choosing your form type: floating bars, lightboxes,inline naked embedded, slide outs
    • 🔙Exit intent and display rules
    • 📋Adding email and name input boxes to your form
    • Setting the size of your form
    • 📱Configuring how your form displays on mobile devices
    • 📲Configuring your mobile width
    • ✖️Add a close window X to your form
    • ⛔Adding a "No" button that closes your form
    • 🏷️Tag subscribers who opt-in to your form
    • 🙅‍♀️Adding "no thanks" text which closes your form
    • 🔣View your form conversion rate
    • 🔗Connect an existing form to your account
    • 🕸️Adding your form to your website
    • 🤖Add opt-in subscribers to an automated email sequence
  • Reply to ElMejor
  • Reply to ba9607f2e
  • Reply to ricardo108
  • Reply to dasGuteDaran
Powered by GitBook
On this page

Was this helpful?

  1. FAQ

Amazon SES production access

PreviousVelocity MTA FAQNextFrom the founder

Last updated 1 year ago

Was this helpful?

Amazon SES has the best pricing of any delivery service that allows email marketing.

Amazon SES is 10 cents per 1000 messages sent, pay-as-you-go, with no minimums or commitments; that's $100 per million messages, only pay for what you send.

This bargain basement discount pricing comes with a higher barrier to entry than with other email delivery API or SMTP Relay services which charge more.

Unlike other vendors, you can't just sign up and start sending.

First, you have to and complete your integration by verifying a domain and connecting it to your ESP platform; then you're placed into "the sandbox."

You can only send mail to email addresses that you own while in the Amazon SES sandbox.

To test your Amazon SES integration while in the sandbox, you have to add and verify each of your personal email addresses one at a time, and that becomes your contact list.

To get out of the sandbox and send mail to your real contact list, you need .

You must have a verified domain and have completed and tested your SES integration with your ESP platform before you request production access.

If approved to get out of the sandbox, your sending limit will start out at 50,000 messages per day, and you can have the cap lifted once you've established yourself as a reasonable sender.

Amazon will initially throttle your production sending to 14 messages per second, which will automatically increase over time.

We have customers who Amazon allows to send hundreds of messages per second.

Getting approved for Amazon SES production access

The first thing that Amazon SES is screening for is that many applicants who apply for new email marketing accounts are liars.

Fake sites, fake blogs, fake products, fake companies.

Example: When Mailchimp made drastic changes to Mandril and rolled it into their main product, they said they were canceling 2000 Mandril accounts per day for spam.

When the Trust & Safety team evaluates your site and your production access application, this is what they're looking at:

  • Does this site, service, or product seem real, professional, and reputable?

  • Is there a footer on the site with a privacy policy?

  • Would this site, service, or product need Amazon SES? Is there a plausible legitimate use case here?

  • How will this applicant build their contact list and where did their existing contacts come from?

  • If all of the above adds up, will this entity be sending emails that people want to read and that don't upset the reader?

Important Make sure your site has the expected footer with a privacy policy.

Important Only make your application for one site, one brand. Your application must be crystal clear and super easy to understand at a glance for the busy Amazon reviewer.

Do not apply for multiple websites/brands or mention other customers and clients. Since Amazon only has the ability to vet your site, product, brand, or service, and no ability to vet your current or future customers or clients, this will cause a denial. As a general rule if your production access application states you intend to act as an agency for managing the mailing lists of others, you will be denied.

If you are a responsible sender, you will have no problem adding additional domains to your Amazon SES account once you've been approved. However, during the production access approval process, any ambiguity will cause a denial.

This is an example of the type of content Amazon SES isn't going to approve:

We had a customer who ticked every box, but the front page of their website was covered in articles about burning in hell, causing their application and all appeals to be denied.

And finally:

  • Is this otherwise legitimate applicant a competent sender? What are their hygiene practices?

  • How will they manage bounces, unsubs, and complaints, ensuring they will help maintain or improve Amazon's sender reputation instead of harm it?

I've spoken to Amazon about what the trust and safety team wants to see to be reassured a sender knows what they're doing, and isn't going to wildly spam and blow their account up out of negligence.

Here's their answer...

Include technical details.

Explain how you plan to use Amazon SES to send email:

How can recipients opt out of receiving emails from you?

How do you plan to handle bounces and complaints?

Bounces, unsubs, and complaints are suppressed account-wide automatically the first time they're seen. ✅

Amazon recommends you familiarize yourself with these links in order to speak the same language as the Amazon SES trust and safety team.

In summation, heed this direct quote from Amazon:

The idea would be to include as much specific details on the SES features they will be leveraging so that the AWS Trust and Safety Team are assured that they are aware and will implement best practices

Softball: 🥎

You'll be asked by Amazon SES to non-specifically state your "Use case".

Just answer general questions like these as comprehensively as possible:

  • What does your site do?

  • How do you plan to build or acquire your mailing list?

  • What will you use Amazon SES for?

Provide supporting evidence if possible. This has worked for getting rejected applicants approved on appeal:

If you're switching from another ESP, attach recent invoices proving you're a valid sender with a regular business relationship with another service.

Provide links to social media accounts associated with your verified domain that have a following and organic engagement.

Attach examples of emails you plan on sending - these better be good and show an unsubscribe footer with a full name and address for the sender and "you have received this email because you...." memo.

All of this may sound formidable but it's actually not hard to get approved.

Bottom line:

Just don't look like a spammer. 👍

Through an integration with the ESP platform. ✅

has a one-click unsubscribe in the footer and a one-click list-unsubscribe header is attached as a backup in case the integrated email delivery service doesn't include its own ✅

The ESP platform integration uses Amazon SNS and event publishing. ✅

Real-time reputation metrics are shown prominently in the platform UI reporting as webhooks come back in live from Amazon. ✅

We will also be using the in the Amazon SES console as a sanity check and backup to monitor our bounce and complaint rates and verify the information we're seeing in the platform is accurate on an ongoing basis. ✅

🌴
create an account
EmailDelivery.com
to request production access
EmailDelivery.com
EmailDelivery.com
EmailDelivery.com
EmailDelivery.com
EmailDelivery.com
reputation metrics dashboard
EmailDelivery.com
Using reputation metrics to track bounce and complaint rates - Amazon Simple Email ServiceAmazon Simple Email Service
Handle a high bounce rate with emails that you send using Amazon SESAmazon Web Services, Inc.
Using subscription management - Amazon Simple Email ServiceAmazon Simple Email Service
Logo
Logo
Logo