A 20,000-message month can cost $20 on Volanea Growth, while the total for another provider depends on its current plan and billing rules. Choosing an SMTP relay service means more than copying a host name: you need a workable deployment path, a cost model for your volume, and a way to trace a message after your application submits it.
An SMTP relay service accepts mail from your application and forwards it toward recipient mail systems. Choose one by mapping your integration, monthly volume, sender-domain setup, event visibility, and operational ownership. For a 20,000-email workload, Volanea Growth is $20 per month; compare other providers using their applicable current plans rather than assuming their totals from an unverified per-message rate.
Start with the sending system, not the provider shortlist
List the applications that will send email before comparing services. A SaaS product might send password resets from its backend, a CMS plugin might send contact-form notifications, and a printer might send scan alerts. Each integration has different requirements: a modern application may support an API, while a device may only expose fields for an SMTP server, port, username, and password.
For each sender, record four details:
- Which application or device sends the message, and who maintains it?
- Does it support SMTP, an email API, or both?
- Which From address and domain should recipients see?
- What should the application do if the relay rejects a connection or message?
This inventory prevents a common migration problem: choosing a provider that fits the main application but leaves a legacy plugin or internal tool without a supported connection method. It also shows whether one platform needs to serve both transactional messages and campaign workflows.
SMTP is a mail-transfer interface. An API is a provider-specific HTTP interface that can expose structured request fields and application controls. Neither choice decides your message policy or sender-domain configuration; those remain part of the system you build and operate.
SMTP relay service selection as an implementation plan
Treat provider selection as a sequence of implementation checks, not as a feature-score exercise. First confirm that the software can connect using an interface the provider supports. Then identify who can make the required DNS changes, who will own credentials, and where engineers will look when a message is rejected.
A practical selection sequence looks like this:
- Confirm interface compatibility. Check the actual application’s SMTP or API settings, including its authentication and TLS options.
- Map sender identities. Decide which From addresses and domains belong to receipts, alerts, and marketing mail.
- Plan credentials. Assign a credential to each application or environment where the provider permits it, and define how you will rotate it.
- Run representative tests. Send a password reset, invoice email, and any other message type that matters to the product.
- Review operations. Find the message event or error details that an engineer would use to investigate a failed send.
The original Postmark comparison guide identifies setup, documentation, support, price, tracking, retention, and security as considerations when weighing email services. For a development team, the practical extension is to test those requirements against a real sender and a real failure path. A checklist becomes useful when each item has an owner and a test, rather than a green check based only on a product page.
For a wider look at API-based sending and configuration choices, see our guide to email API services.
Compare the cost of a 20,000-email month
A useful cost comparison starts with one defined workload. Suppose your application sends 20,000 emails in a month, with no assumptions about attachments, add-ons, or separate campaign tools. Volanea Growth is listed at $20 per month for 50,000 emails, so that volume fits within the stated plan and the monthly plan total is $20.
| Provider or plan | 20,000-email example | What the figure establishes |
|---|---|---|
| Volanea Growth | $20 per month | The listed plan includes 50,000 emails, so 20,000 is within its stated monthly volume. |
| Amazon SES | No total stated here | Calculate from the applicable AWS pricing model and any charges relevant to the planned sending configuration. |
| Postmark | No total stated here | Use the applicable current plan and its included volume or additional-message rules. |
The exact SES and Postmark totals cannot be established from the verified figures used for this article. Rather than reuse a rate or tier that may not apply, take the same 20,000-message assumption to each provider’s current pricing page and include any additional products your architecture requires. The comparison is only meaningful when you use the same volume and message mix for each option.
For Volanea, the listed Starter plan is $5 per month for 7,500 emails, and Growth is $20 per month for 50,000 emails. The product site lists 1,000 free emails or credits every month. Plans differ by monthly volume and domain count, and every feature ships on every plan; the domain counts for Starter and Growth are not stated in the product facts available here, so do not infer them from the volume tiers.
Volanea pauses sending when the monthly limit is reached, with no overage billing. That makes the volume limit an operational consideration as well as a price detail: if a billing run or launch can take usage past the plan’s allowance, choose an appropriate tier or plan how to handle the pause.
Configure SMTP without guessing the endpoint
SMTP settings are provider-specific. For Volanea, the verified login details are username volanea and a password equal to the project’s secret API key. The exact SMTP host and port are not included in the product facts available here, so use the endpoint and TLS mode supplied for your project rather than substituting a guessed server name.
A conventional STARTTLS configuration template looks like this; replace the host with the endpoint given by your provider and confirm the port and security mode match its instructions:
SMTP_HOST=your-provider-smtp-host
SMTP_PORT=587
SMTP_TLS=STARTTLS
SMTP_USERNAME=volanea
SMTP_PASSWORD=your-project-secret-api-key
Port 587 and STARTTLS are shown as a standard configuration example, not as a Volanea endpoint specification. Keep the key in environment variables or a secret manager, not in source code or frontend JavaScript. The From field for Volanea accepts either a bare address such as alerts@example.com or a display name and address such as Acme Alerts <alerts@example.com>.
For a command-line smoke test with swaks, set the host and credentials to the values provided for your project. This example requests STARTTLS and attempts SMTP LOGIN authentication:
swaks --server "$SMTP_HOST" --port "$SMTP_PORT" --tls \
--auth LOGIN --auth-user "$SMTP_USERNAME" \
--auth-password "$SMTP_PASSWORD" \
--from "alerts@example.com" --to "you@example.net"
A successful SMTP conversation shows that the client connected and the relay accepted the submission. It does not by itself tell you that the destination mailbox accepted the message. Check the provider’s message status or event view after sending, and make sure the test address is one you can inspect.
Volanea sk_test_ keys render and log messages but never deliver them. Use a live project key when testing actual delivery, and keep test credentials separate from production configuration so a successful render cannot be mistaken for a delivered message.
Decide which operational events you need
A useful email incident timeline separates three stages: the application tried to submit, the relay accepted or rejected the submission, and the receiving system accepted or bounced the message. Logging only “send succeeded” at the first stage hides later failures. Record a message identifier, recipient, timestamp, and the outcome your integration receives, while limiting access to sensitive message data.
Before choosing a platform, determine where your team can see these facts and how far back the records remain available. Volanea’s verified product facts do not state an event or log-retention period, so we do not use a retention figure in the comparison. If support investigations need a defined history window, make that a requirement to establish during provider evaluation.
Build a simple failure-handling policy into the application:
- Retry transient connection failures with a bounded delay and a maximum number of attempts.
- Do not repeatedly retry a permanent rejection or an address that has bounced.
- Give users a clear recovery path for critical messages such as password resets.
- Keep credentials and full message bodies out of routine application logs.
For example, if a password-reset submission times out, the application can retry within a controlled window and preserve a request identifier for support. If the provider later reports a permanent rejection, repeating the same submission does not correct the recipient address. Clear event handling makes that difference visible to the engineering team.
Separate message purpose when systems share a relay
Transactional email and campaigns can use the same provider, but they have different triggers and recipient expectations. A receipt follows a purchase; a newsletter goes to an audience that has opted in. Your system still needs to manage consent, suppression, and the reason each message is sent, even when both message types use one account.
A unified platform can be useful when the same team owns account notifications, product updates, and campaign automation. Volanea combines transactional email, campaigns, and automations in one API, with segments available alongside transactional sending. We send through Amazon SES, so teams can consider both the product layer and the underlying sending infrastructure when evaluating fit.
We do not list a dedicated IP option in our comparison with Amazon SES. Teams with a dedicated-IP requirement should treat that as a selection criterion before choosing a provider, rather than expecting a shared sending setup to satisfy it. A shared infrastructure model also means teams should focus on the domain, sending practices, and message types they control.
If an AI coding agent is part of your setup process, our email MCP server setup guide describes connecting Gmail, SMTP, and Volanea. Our email deliverability and sending guides cover related implementation topics.
Decide who owns the relay after launch
A production relay needs an operational owner, even when the provider handles the outbound infrastructure. Name the person or team responsible for domain records, credential rotation, volume monitoring, and investigating delivery events. This is especially important for agencies managing separate client domains or SaaS teams where several services send from the same product.
Write down a small runbook before enabling production traffic. It should state which system owns each credential, where the configured SMTP endpoint comes from, how to test a send, and where the team checks an event after submission. Include a path for rotating a key without leaving a scheduled job or staging environment with stale credentials.
A change in traffic is a useful review trigger. If a new product feature adds a large batch of notifications, or a campaign workflow moves into the same account, revisit expected monthly volume and who handles the resulting support questions. That review connects provider selection to the system you actually operate, rather than treating signup as the end of the work.
FAQ
When should a SaaS team move from direct Amazon SES setup to a managed email platform?
Move when the AWS configuration and ongoing coordination take more engineering time than your team wants to own, or when you need campaigns and automations alongside transactional messages. For example, a team that currently maintains one SES integration but is adding audience segments can compare the cost of a combined platform with its actual maintenance work and required features.
Why does my SMTP test connect but the recipient still not receive the email?
A successful SMTP submission confirms that the client reached the relay and the relay accepted the message for processing. Later, the recipient system can reject it or return a bounce. Check the message’s downstream status and the recipient address, then distinguish that outcome from a TLS, authentication, or network error in the application log.
What should I do if a monthly sending limit pauses email?
First identify which application or workflow consumed the remaining volume, then prioritize messages that affect account access or essential product actions. Volanea pauses sending at the plan limit rather than billing overages, so review expected monthly usage and choose a suitable volume tier before a predictable peak such as billing notifications or a planned campaign.
Can an AI coding agent configure SMTP credentials safely?
An agent can edit configuration and generate test commands, but provide secrets through an approved secret store or environment variables rather than embedding them in generated source. For Volanea, the SMTP password is the project’s secret API key. Keep test and live credentials distinct, and review the host and TLS values against your project’s provider settings before deployment.
Start free with 1,000 emails a month → https://app.volanea.com/signup