SMTP service for bulk email: choose and set up
SMTP vs API, ports 587 and 465, STARTTLS, selection criteria and a five-minute relay setup.
SMTP service for bulk email: how to choose
An SMTP service (SMTP relay) is an external sending server your app connects to over SMTP on port 587 or 465, authenticates with a username and password, and hands off a message; the service then signs it with DKIM, guards IP reputation and delivers it. Choose one on deliverability, domain authentication, limits, logs and price. Here are the criteria and the setup.
SMTP or HTTP API — which to pick
Both result in the same send but suit different jobs.
| Criterion | SMTP relay | HTTP API |
|---|---|---|
| Integration | Built-in mail libraries in any language/CMS | Needs an HTTP client or SDK |
| Compatibility | WordPress, ERPs, printers, legacy software | Modern applications |
| Speed & metadata | One message per connection | Batches, tags, webhooks, templates |
| Feedback | SMTP codes (250/550/554) | JSON statuses + open/click events |
Rule of thumb: WordPress, a CRM or off-the-shelf product — use SMTP; writing code and want templates, tags and webhooks — use the API. YourTrend offers both on one infrastructure.
Ports and encryption: 587, 465 and why not 25
- 587 (Submission + STARTTLS) — the recommended port for sending from applications. The connection starts in the clear,
STARTTLSupgrades it to TLS, then authentication follows. This is the modern standard (RFC 6409). - 465 (SMTPS, implicit TLS) — TLS is established immediately on connect. Fully valid and convenient when a library expects "SSL from the first byte".
- 25 — this is the server-to-server delivery port (MTA→MTA), not application submission. Providers and clouds block it outbound en masse. Never use 25 for your own sending.
On both working ports, keep certificate verification on (except when debugging on localhost). Authentication is AUTH LOGIN or PLAIN over TLS; credentials always travel inside the encrypted channel.
When you need a relay, not your own Postfix
You can run your own MTA, but deliverability is decided by IP reputation, a valid PTR record, warm-up and complaint handling — not by the software. A relay absorbs all of that: warmed IP pools, transactional/bulk stream separation, FBL, RFC 8058 one-click unsubscribe, DMARC reports. Running your own server makes sense mainly under strict data-sovereignty needs — then look toward secure mail on your own perimeter.
How to choose an SMTP service
- Domain authentication. The service must DKIM-sign your mail and work with your SPF and DMARC. Without it, Gmail and Outlook will bin you.
- Stream separation. Transactional mail (passwords, receipts) must not share an IP with promotions.
- Logs and events. A send log, rejection reasons, opens and clicks, CSV export.
- Limits and pricing. Daily and monthly quotas, behaviour on overage, cost per volume.
- Diagnostic tools. Address validation, spam score, blocklist check before you send.
YourTrend builds all of this in: an SMTP relay and an API, automatic DKIM on a verified domain, transactional/bulk streams, a log with opens, and a free deliverability lab (validator, spam test, blocklist check).
Quick SMTP setup in YourTrend
Add a domain and publish SPF/DKIM/DMARC, create a mailbox and grab its parameters under "Mailboxes". Typical client settings:
Host: mail.yourtrend.online
Port: 587 (STARTTLS) or 465 (SSL/TLS)
User: noreply@yourdomain.com
Pass: <mailbox password>
Crypto: STARTTLS for 587, implicit TLS for 465
Verify the connection with a single swaks command:
swaks --server mail.yourtrend.online:587 --tls \
--auth LOGIN --auth-user noreply@yourdomain.com \
--from noreply@yourdomain.com --to you@gmail.com
A 250 OK means the message was accepted for delivery. A step-by-step walkthrough of setup, tests and common errors (535/550/554) is in the separate article on configuring an SMTP relay, and volume tiers are on the pricing page.
Bottom line: pick an SMTP service on deliverability and domain authentication, not on how pretty the panel looks. Port 587 or 465, TLS mandatory, transactional split from promo, and logs plus diagnostics within reach. YourTrend covers those and leaves only the email content to you.
Warm-up and sender reputation
Even a perfectly configured SMTP service won't guarantee the inbox from day one: providers judge the reputation of the sending domain and IP. A new sender must warm up — ramp volume gradually over 2–4 weeks, starting with the most active, loyal recipients. The metrics Gmail, Outlook and Yahoo watch: complaint rate (keep it below 0.1%), bounce rate, engagement (opens, replies) and volume stability. A sudden jump from zero to tens of thousands of messages is a classic route to the spam folder. What helps: segmenting by activity, pruning inactive addresses, mandatory one-click unsubscribe (RFC 8058) and registering with postmaster tools for monitoring. YourTrend separates transactional and bulk streams and keeps a complaint-and-bounce log so warm-up stays controlled. For a step-by-step relay setup, see the article on configuring an SMTP relay.
What it costs and how to size volume
SMTP-service pricing is usually tied to volume — messages per day and per month, not the number of connections. Size your peak: how many transactional emails the product generates (sign-ups, receipts, password resets) plus headroom for promotions. Mind the overage behaviour: some services hard-cut sending, others charge for overage — this affects the reliability of transactional mail. YourTrend offers a free tier for starting out and diagnostics, plus paid levels with separate daily and monthly limits so a campaign spike never starves critical mail; see current volumes and prices on the pricing page.
On this page
← All articlesOne click. It tells us what to write next.
No ratings yet — yours would be the first.
Comments
Comments are read before they appear.