SMTP Relay
Works with CRMs, commerce platforms and existing applications using standard SMTP.
- STARTTLS on ports 587 and 2525
- Per-credential traffic controls
- Standard SMTP response codes
EMAIL DELIVERY
One platform.
Two ways to send.
Use SMTP for instant compatibility or integrate the Email API for deeper control. Both routes share the same delivery engine, suppression layer and event stream.
SMTP RELAYConnect once.
Connect once.
Send with confidence.
- Use standard SMTP credentials
- Route traffic by recipient provider
- Protect reputation with suppression checks
- Monitor every recipient outcome
smtp.vuelamail.com
Message accepted250 2.0.0 queued as VM-8F2A91- 01 Authenticate
- 02 Suppression check
- 03 Provider route
ACCEPTANCE99.98%
EMAIL APIA focused API.
A focused API.
Clear delivery events.
- Submit single or batch requests
- Attach metadata and custom headers
- Receive signed webhooks
- Build replay-safe event processing
POST /v1/email
{
"from": "team@example.com",
"to": ["user@example.net"],
"subject": "Hello",
"metadata": {"order": "8412"}
}RESPONSE202
DEDICATED INFRASTRUCTUREYour reputation.
Your reputation.
Your sending lane.
- Dedicated IP allocation
- Custom PTR and rDNS
- Managed warm-up schedules
- Provider-specific traffic controls
DEDICATED POOL3 active IPs
Reputation healthy
Gmail Ready
Microsoft Managed
Other providers Ready
POOL STATUSLive
Connect your stack
in minutes.
VuelaMail keeps the integration surface small. Authenticate your domain, create a credential and send. Routing, provider throttling, bounce handling and retries run behind the same interface.
Email API
A focused JSON API for transactional and campaign sends with clear acceptance results.
- Single and batch submission
- Metadata and custom headers
- Idempotent request handling
Event Webhooks
Stream delivery, bounce, complaint and unsubscribe events back to your application.
- Signed event payloads
- Replay-safe processing
- Recipient-level outcomes
01 · SUBMITYour applicationSMTP or HTTPS API
→
02 · PROCESSVuelaMail queuePolicy, suppression and routing
→
03 · DELIVERRecipient providerControlled delivery and feedback
Reliable by
default.
Every accepted request enters a durable queue. Temporary provider responses are retried with backoff; permanent recipient failures are classified and suppressed.
Restarts do not erase work.
Queued recipients and progress checkpoints survive service restarts and infrastructure maintenance.
state: queued → accepted → deliveredEvery provider is different.
Domain-specific rate limits and retry schedules keep one provider from slowing the whole campaign.
route: provider-aware / adaptiveBad addresses stop once.
Hard bounces, complaints and unsubscribes are removed before future sends reach the delivery queue.
suppression: global / immediateKnow what happened.
Recipient-level outcomes keep accepted, delivered, deferred and failed states separate.
events: signed / replay-safe BUILD WITH VUELAMAIL
Send your first
request.
Choose SMTP or API and keep the same delivery infrastructure as you scale.