Setting up Amazon SES as SMTP in QRACCESS
Connection details, how to get the credentials and exactly what to enter in the dashboard. Not sure which provider to pick? Start with the general SMTP guide.
Connection details
| Server (host) | email-smtp.eu-west-1.amazonaws.com (Ireland; one host per region worldwide) |
| Ports | 587 (STARTTLS) · 465 (SSL) · 2525 |
| Username | the “SMTP username” generated in the SES console |
| Password | the “SMTP password” generated with it |
How to get the credentials
- In the AWS console → Amazon SES, verify your domain (it gives you the DKIM DNS records).
- Under “SMTP settings” click “Create SMTP credentials”: it generates SMTP-SPECIFIC username and password (not your regular AWS keys).
- Request production access to leave the “sandbox”: until then you can only send to verified addresses.
- Pick your region’s host: eu-west-1 (Ireland), us-east-1 (USA)… always email-smtp.REGION.amazonaws.com.
What to enter in QRACCESS
In the dashboard: Settings → SMTP. Fill in Host and Port from the table above, pick the encryption to match the port (TLS for 587, SSL for 465), and enter Username and Password exactly as the table says — with some providers the “username” is a fixed word or an API key, not your email. Use a sender address on your verified domain and a recognisable sender name. Save, then use the test button with one of your own contacts before any bulk send.
Note: By far the cheapest at volume (~$0.10 per 1,000 emails) with regions worldwide. In exchange, the most technical setup of the list: verified domain and sandbox exit are mandatory.
Deliverability: SPF and DKIM
Whatever the provider, verify your domain and publish the SPF and DKIM records it gives you: that is the difference between the inbox and the spam folder. Always run a single test before a bulk send.
Would you like to try QRACCESS at your next event?
Create an account and start setting up your first event from the web control panel.
Control panel: https://control.qraccess.com