Skip to content
Splashify Pro
Email docsEmail

SMTP Relay

For frameworks and platforms that can't easily call our REST API, use the SMTP relay. Same DKIM signing, suppression, billing, and webhook delivery — your app just speaks plain SMTP.

Connection

TLS is required. Plain-text auth is rejected.

Settings, API key section with the SMTP credentials card: host smtp.splashifypro.com, port 587 (STARTTLS) or 465 (TLS), username emailapikey, password your pk_live_ key, and a note that the From address must match a verified identity
The same settings are in Settings, API key

Test with swaks

bash
swaks --to [email protected] \
      --from [email protected] \
      --server smtp.splashifypro.com \
      --port 587 -tls \
      --auth-user emailapikey \
      --auth-password "$SPLASHIFY_API_KEY" \
      --header "Subject: Test from swaks" \
      --body "Hello"

WordPress (WP Mail SMTP)

  1. Plugin → WP Mail SMTP → install
  2. Mailer → Other SMTP
  3. Host: smtp.splashifypro.com · Port: 587 · Encryption: TLS
  4. Auth: ON · Username: emailapikey · Password: your API key
  5. Save & send a test email

Django

python
# settings.py
EMAIL_BACKEND = "django.core.mail.backends.smtp.EmailBackend"
EMAIL_HOST = "smtp.splashifypro.com"
EMAIL_PORT = 587
EMAIL_USE_TLS = True
EMAIL_HOST_USER = "emailapikey"
EMAIL_HOST_PASSWORD = os.environ["SPLASHIFY_API_KEY"]
DEFAULT_FROM_EMAIL = "[email protected]"

Laravel

env
MAIL_MAILER=smtp
MAIL_HOST=smtp.splashifypro.com
MAIL_PORT=587
MAIL_USERNAME=emailapikey
MAIL_PASSWORD=${SPLASHIFY_API_KEY}
MAIL_ENCRYPTION=tls
[email protected]

Node (nodemailer)

javascript
import nodemailer from "nodemailer";

const transport = nodemailer.createTransport({
  host: "smtp.splashifypro.com",
  port: 587,
  secure: false,                    // STARTTLS
  auth: {
    user: "emailapikey",
    pass: process.env.SPLASHIFY_API_KEY,
  },
});

await transport.sendMail({
  from: "[email protected]",
  to: "[email protected]",
  subject: "Hello",
  html: "<p>Welcome</p>",
});

Postfix

In /etc/postfix/main.cf:

text
relayhost = [smtp.splashifypro.com]:587
smtp_sasl_auth_enable = yes
smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd
smtp_sasl_security_options = noanonymous
smtp_use_tls = yes
smtp_tls_security_level = encrypt

In /etc/postfix/sasl_passwd:

text
[smtp.splashifypro.com]:587 emailapikey:pk_live_...
bash
postmap /etc/postfix/sasl_passwd
chmod 600 /etc/postfix/sasl_passwd*
postfix reload

Supabase Auth (transactional email for signups, OTPs, password reset)

Supabase ships a "Custom SMTP" panel that you can point at the relay so signup confirmation, magic-link, and password-recovery emails come from your verified sender instead of the Supabase default.

Project → Project Settings → Auth → SMTP Settings:

Then save & hit Send test email. If you get 535 5.0.0 5.7.0 invalid api key format it means you pasted something other than a pk_live_… (or sk_live_… for app-developer accounts) key — copy the key from Settings → API key in Splashify Pro Email.

Things to know

  • Sender must be on a verified identity. Sends from an unverified email/domain are rejected with 550 5.7.1 sender '<addr>' is not on a verified identity for this account. Add the domain or email at Settings → Identities before testing.
  • One From address. A From header that is missing or is not one address is refused with 553, text 5.1.7 missing or invalid From header. A name with a comma must be quoted.
  • Suppression list applies. Recipients on your account suppression list are rejected at RCPT TO with 550 5.7.1 recipient on suppression list.
  • Free sandbox: 200 emails/day. New accounts are sandboxed. Once you exceed the 200/day quota you'll get 452 4.7.0 Sandbox daily limit of 200 emails reached. Request production access from the dashboard to lift it.
  • Daily limit on live accounts. A message that does not fit in today's limit is refused whole, nothing charged, with 452 4.7.0 Daily limit of N emails reached. It resets at midnight UTC. The code is temporary: your mail server can try again and the message goes through after midnight UTC.
  • Paused accounts. While sending is paused on your account a message is refused, nothing charged, with 554 5.7.1 Sending is paused on this account. Contact support.
  • Billing. ₹0.03/email for paid sends (post-sandbox); sandbox sends are free. SMTP and REST sends bill identically.
  • Webhooks fire normally. SMTP and REST sends produce the same event stream into your configured destinations.
  • TLS is required. Plain-text AUTH is rejected; the relay only advertises AUTH after STARTTLS (port 587) or on the implicit-TLS port (465).
  • Configuration set via a header. Set X-Configuration-Set: <name> on the outbound message to send it through a config set of your account. An unknown name is refused with 550 5.7.1 Configuration set <name> not found., and a set with sending_enabled: false with 554 5.7.1 Sending is off for configuration set <name>., both before any charge. The header is not in the mail we send.
  • SMTP mail is always transactional. Every message counts as transactional, for its price and for the suppression list: an unsubscribe does not stop it, but a bounce, complaint or manual entry does.