iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
To send AcelleMail campaigns through Amazon SES, you verify a sender identity in one SES region, confirm the account can reach ordinary recipients, create credentials that match that same region, and then add the sending server in AcelleMail and run a test before any campaign goes out. Most setup failures come from a mismatch between those pieces, so the steps below are arranged to keep them aligned.
What you need before you start
- An AWS account with access to Amazon SES in the region you plan to use.
- An AcelleMail installation and an administrator login that can open Sending → Sending servers.
- A sender email address you control, or a domain whose DNS records you can edit.
- A decision on which integration to use: the SES API or the SES SMTP interface. Step 3 explains the difference.
Step 1: Verify the sender identity in the region you will use
Amazon SES treats a domain or an email address as an identity. AWS’s official SES documentation states: “Before you can send an email using Amazon SES, you must create and verify each identity that you’re going to use as a "From", "Source", "Sender", or "Return-Path" address.” Verification is recorded per region, so an identity verified in one region does not automatically exist in another. Choose the region you intend to use first, and keep it selected for every step that follows.
Verify a single email address
- Open the Amazon SES console and select your region from the region selector in the navigation bar.
- Go to Identities and choose Create identity.
- Select Email address, enter the sender address, and submit.
- Open the verification email sent to that address and follow the link. The identity status changes to verified when the link is confirmed.
Verify a domain
- In the same region, go to Identities and choose Create identity, then select Domain.
- Copy the DNS records SES generates for that identity. These normally include a verification record and DKIM records. Use the values SES displays for the selected region; records copied from another region will not verify this identity.
- Publish the records at your DNS provider and wait for the identity status to show verified. DNS propagation time varies by provider, so allow time before retrying.
Step 2: Check sandbox status and request production access
New SES accounts start in the sandbox. In the sandbox, SES accepts messages only to recipients whose addresses are verified, with one exception: the SES mailbox simulator addresses, such as success@simulator.amazonses.com, which AWS provides for testing. Sandbox status is tracked per region, so check it in the region you selected in Step 1.
Free tools Windows power users keep installed
One-click scans. No signup required.
If your campaigns must reach ordinary unverified subscribers, open the SES account dashboard in that region and request production access. AWS does not promise approval or a specific timeframe, and sending quotas are set per account and per region. Do not treat the quota shown in the console as a guarantee of future volume.
#1 Best Overall
- Fortinet FortiMail-VM virtual appliance for all supported platforms. 8 x vCPU cores
- Fortinet SW FML-VM08
- Manufacturer Part: FML-VM08
Step 3: Choose the SES integration and create matching credentials
AcelleMail’s SES setup article, dated June 1, 2026, describes two sending-server types: Amazon SES API and Amazon SES SMTP. Both are valid configuration options, and the article labels the API choice as recommended. That label is the vendor’s guidance; neither option has been independently benchmarked here for speed or reliability, so choose based on your hosting setup and on which credentials you are able to manage.
| Item | SES API | SES SMTP |
|---|---|---|
| Credentials entered in AcelleMail | AWS access key ID and secret access key for an identity permitted to send through SES | SES SMTP username and SES SMTP password |
| Region setting | The SES region, which must match the verified identity | The region embedded in the SMTP endpoint hostname, which must match the verified identity |
| Transport security | Handled by the API integration | TLS is required; choose STARTTLS or TLS Wrapper (see the port table below) |
Creating SES SMTP credentials
SES SMTP credentials are separate from your AWS console login and from your access keys. AWS states that SES SMTP credentials are unique to each region, so create them in the same region as your identity. In the SES console for that region, open SMTP settings and choose the option to create SMTP credentials. SES displays the username and password for that set; save them immediately in a password manager or your secrets store, and limit who can read the AcelleMail configuration that holds them. Console labels change from time to time, so match the wording you see on screen.
Step 4: Add the sending server in AcelleMail
- Sign in to AcelleMail as an administrator and go to Sending → Sending servers.
- Create a new sending server and select the Amazon SES integration type that matches your choice in Step 3 (SES API or SES SMTP).
- For the API type, enter the AWS access key ID, the secret access key, and the SES region.
- For the SMTP type, enter the regional SES SMTP endpoint hostname, the SES SMTP username and password, the port, and the TLS mode. Copy the exact hostname shown for your region in the SES SMTP settings page.
- Set the default sender address. It must be an identity verified in the same region as the server.
- Save the server. Field names can differ between AcelleMail versions, so use the labels in your installed release.
SMTP transport: ports and TLS modes
AWS requires TLS for connections to the SES SMTP endpoint. It documents two modes, each paired with specific ports:
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →| Connection mode | Ports AWS documents | How the connection starts |
|---|---|---|
| STARTTLS | 25, 587, 2587 | The client opens a plain SMTP session and upgrades it to TLS before authentication. |
| TLS Wrapper (SMTPS) | 465, 2465 | TLS is negotiated as soon as the connection opens. |
Pair the mode with the matching port family; a STARTTLS setting on port 465 or a TLS Wrapper setting on port 587 will fail. If AcelleMail runs on an Amazon EC2 instance, AWS throttles outbound traffic on port 25 by default, so use 587 or 2587 unless AWS has removed that restriction for your account.
Rank #3
- Model: RHTx-IoT1; SMS(4G/LTE Version) + Email + Cloud hosting to User End | Measuring Parameters: Temperature, Relative Humidity | Temperature Range: 0 to 50°C; Accuracy: ± 0.5°C; Resolution: 0.1°C | Relative Humidity: 0 to 100% RH; Accuracy: ± 2% RH; Resolution: 0.1 %RH |
- Display: 128 X 64 Dot Matrix Graphical Large LCD Display with White Backlight | Operating Temperature: Safe operating temperature of instrument is 0°C to 70°C | Cable Length: Connecting Cable, pre-wired 3 mtrs. Extension between display monitor & sensor.
- Buzzer: Standard In-Built Buzzer for Alarm (External Buzzer also available - Contact Store) | Alarm Type: In built buzzer for Low & High Limit upon temperature set point violation, approx. 50 Decibel | Alarm Limit: User Configurable, freely programmable from 4 front keypad |
- Acknowledgement Key: Provided for user to acknowledge the alarm manually, thus avoiding continuous buzzer alarm sound & user attention | Sensor Type: 1. Polymer sensing for Temperature 2. Capacity polymer sensing for Relative humidity 3. Option of Extending Audio Visual Buzzer to 24/7 Surveillance/Security Rooms | Power Supply: 12 VDC Input with minimum of 2-amp current rating. Adaptor provided alongwith | Enclosure: Wall mounting type ABS
- Supply Scope: 1 Unit of RHTx-IoT Temperature Humidity Monitor, Antenna, Power Adaptor, Instruction Manual and Factory Calibration Certificate | Applications: Server Rooms, Datacenters, Cold Chains, Pharmaceuticals, Bio-Medical, Warehouse, Hospitals, Seed Storages.
Step 5: Test the connection and a test message
- In the sending server form, run the connection test if your AcelleMail version provides one.
- Send a test message to an address you control. If the account is still in the sandbox, use a verified address or a mailbox simulator address.
- Confirm that the message arrived, then check the outcome in AcelleMail’s sending logs and in the SES console for the same region.
- Assign the server to a campaign only after both checks succeed. Start with a small, controlled send to a known list before a full campaign.
A passing test confirms that the connection, credentials, and sender identity work for that message. It does not measure inbox placement, and AWS does not publish a delivery rate or a universal volume limit for SES accounts.
When a test fails
Work through the checks in this order. Each one corresponds to a documented requirement, but a failure can have more than one cause.
| Symptom | What to check |
|---|---|
| Sender is rejected | The sender address or domain is verified in the SES region selected in AcelleMail, not in a different region. |
| Only some recipients are rejected | The account is still in the sandbox in that region, so the recipient address must be verified or be a mailbox simulator address. |
| SMTP authentication fails | The server uses SES SMTP credentials, not the AWS console password or the access key pair. Create a new SMTP credential in the correct region if needed. |
| Connection times out on port 25 | An EC2 instance may be throttled on port 25. Switch to 587 or 2587 with STARTTLS, or request removal of the restriction. |
| TLS handshake fails | The TLS mode does not match the port: STARTTLS with 25, 587, or 2587, and TLS Wrapper with 465 or 2465. |
| Connection works but the region looks wrong | The SMTP endpoint hostname, the region setting, and the identity region must all refer to the same region. |
| Outbound mail never leaves the server | The host’s outbound network rules allow the chosen SMTP port to AWS. |
Keeping the setup stable after launch
Keep the sender identity, the SES region, the sandbox status, and the credentials in one place in your records. If you ever change regions, treat the move as a new setup: verify the identity, request production access there if needed, create new SMTP credentials, and update the AcelleMail server. Recheck the AcelleMail menu labels after an upgrade, because the setup article is dated June 1, 2026 and the interface may have changed since then.
Quick Recap
Best Value
- 【Processor & OS】Firewall Mini PC with Intel J4105 CPU up to 2.5GHz, 4Cores4threads 4MB L2 Cache, TDP 10w, supports AES-NI. It tested with pf-sense linux ubuntu and other popular open source OS. ("DEL" key to enter BIOS)
- 【Interfaces】The firewall pc has 4 * Intel 2.5GbE I226 lan ports, 2 * USB3.0 ports, 1 * VGA port, 1 * HD port, 1 * DC port. Equipped with VESA mount, you can install the micro pc behind the monitor to save space.
- 【DDR4 RAM & mSATA SSD】The firewall router equipped with 8G DDR4 RAM, max support 16GB; 240GB mSATA SSD equipped, can be up to 512GB. Not support HDD.
- 【Fanless Design】The small firewall box is only small but powerful. Low power consumption, only 10W; fanless heat dissipation design, aluminum alloy shell, efficient and fast heat dissipation, support 24/7 hours working, no noise. Fanless mini PC, silent, with heat dissipation through the casing, which can withstand temperatures up to 60°C
- 【12 Months Service】You will get 1*mini pc，size:5.27 * 4.98 * 1.43 in weigh:500g. If you encounter any problems during the use, please contact us through Amazon, we have a professional and efficient team dedicated to serving you.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
