Developer SMTP API Documentation
Welcome to the SMTP.MOM integration manual. Connect your client applications, billing software, custom backends, or email clients seamlessly via our global offshore mail pool.
SMTP Connection Parameters
To connect your software, point it to the global endpoint and use your dynamic credentials. Ensure your firewall allows outgoing traffic on your chosen port.
| Parameter | Value | Description |
|---|---|---|
| SMTP Host | api.smtp.mom | Unified offshore relay endpoint |
| SMTP Username | mom_xxxxxxxxxx | Generated randomly upon registration |
| SMTP Password | your_secure_api_key | Generated API key accessible in Dashboard |
| Encryption | STARTTLS / SSL | Explicit security protocols highly recommended |
Offshore Relay Ports
We host multiple communication ports to maximize compatibility across blocked networks and local ISP constraints:
| Port | Protocol | Use Case / Description |
|---|---|---|
| 2525 | STARTTLS / Plain | Default fallback port. Bypasses domestic ISP filters that block port 25. High speed. |
| 587 | STARTTLS | Standard SMTP client connection port. Supported by default in WHMCS and WordPress. |
| 465 | SSL / SMTPS | Implicitly encrypted connection port. Secure handshake immediately on connect. |
| 25 | STARTTLS / Plain | Standard mail transfer protocol port. Useful if outbound firewall restriction is absent. |
SMTP Authentication
All relays require explicit authentication using standard SMTP Auth (PLAIN or LOGIN). Outbound mail is billed to your balance per-message based on your pricing tier rates.
mom_f023a1) instead of using your personal account email. Keep your API keys confidential.
Code Integration Examples
Use these complete code blocks to drop SMTP relay capabilities directly into your projects.
PHPMailer (PHP)
WordPress Config (phpmailer_init)
Paste this code snippet at the end of your WordPress theme's active functions.php file to hook global outbound emails through SMTP.MOM:
Nodemailer (Node.js)
smtplib (Python)
SMTP swaks Diagnostics
You can perform end-to-end connection testing directly from your server command line using the swaks utility:
Troubleshooting Errors
If your message bounces or delivery fails, cross-reference these common SMTP error responses returned by our servers:
| Error Response | Cause | Resolution |
|---|---|---|
535 Authentication failed | Invalid SMTP username or API key | Check your SMTP user & password details inside the credentials panel. |
554 Insufficient balance | Your account balance is too low to relay the message | Top up your balance in the Billing or Deposit tab. |
421 Relaying temporarily denied | Outbound nodes are temporarily throttling | The proxy will automatically redirect to a backup node. Retry in a few seconds. |