SMTP submission (wp_mail)
Use this when your app only supports SMTP (e.g. WP Mail SMTP or Easy WP SMTP), not the HTTP API.
What happens
You enter host, port, username, and password in the plugin. Kirisan accepts the message over SMTP, then enqueues it on the raw lane (same as free-form content on the Send API). Delivery to the recipient’s inbox runs one at a time after the queue, with a 2 requests per second per domain accept cap and up to 200 pending messages per domain.
This is not the instant transactional template path (OTP/receipt). For OTP use transactional templates via the Send API or dashboard Send.
Prerequisites
- Verified, paid email domain.
- At least one sender on Channel → Email → Emails — copy the sender token.
- Correct SPF and DMARC on the domain (same as other Kirisan email sending).
SMTP settings
| Plugin field | Value |
|---|---|
| SMTP Host | smtp.kirisan.com |
| Encryption | TLS (STARTTLS) |
| SMTP Port | 587 |
| Authentication | On |
| SMTP Username | The sender From address (e.g. noreply@yourdomain.com) |
| SMTP Password | Sender token from Emails (not your Kirisan account password) |
The message From must match the authenticated address. Kirisan rejects spoofed From headers.
WordPress (WP Mail SMTP)
- Install WP Mail SMTP (or similar).
- Choose Other SMTP / Generic SMTP.
- Fill in the table above.
- Send a test email from WordPress (contact form or the plugin’s Email Test).
On success the server accepts and queues the message; check Channel → Email → Log after the queue worker sends it.
Important limits
- Raw lane: no marketing email pool; cold sends are allowed but rate-limited and queued.
- One recipient per SMTP message.
- Message size follows Kirisan outbound limits (10 MB).
- Port 465 (SMTPS) is not supported in this phase — use 587 + TLS.