SMTP Integration
Arsel provides a standard SMTP server that lets you send transactional emails using any SMTP client. This is ideal when your application already sends emails through SMTP and you want to route them through Arsel without changing your code.
When to Use SMTP vs API
| SMTP | REST API | |
|---|---|---|
| Best for | Existing apps with SMTP code, legacy systems, platforms that only support SMTP | New integrations, full control over request/response, programmatic workflows |
| Authentication | Username + password per connection | API key per request |
| Features | Send emails with HTML, text, attachments | Send emails + list status + per-recipient tracking + SMS |
| Rate limiting | Per-organization, same as API | Per-organization with response headers |
| Tracking | Full delivery tracking via the API status endpoints | Full delivery tracking built-in |
Emails sent via SMTP are processed through the same pipeline as API emails. You get the same delivery infrastructure, tracking, and analytics regardless of which method you use.
Connection Details
| Setting | Value |
|---|---|
| Host | smtp.arsel.sa |
| Port | 465 (implicit TLS) |
| Security | TLS required |
| Authentication | PLAIN or LOGIN |
| Max message size | 25 MB |
Quick Start
-
Create SMTP credentials from your Arsel Dashboard under Settings > SMTP Credentials. See Managing Credentials.
-
Configure your SMTP client with the connection details above and your generated username and password.
-
Send an email through your application's existing email flow.
See Sending Emails via SMTP for detailed setup examples across languages and frameworks.
Requirements
Before sending via SMTP, ensure:
- Your sender domain is verified in the Arsel dashboard
- Your SMTP credentials are active (not revoked)
- Your organization's sending quota has not been exceeded
- Your organization is not suspended due to bounce/complaint rates