Skip to content

Search documentation

Search pages and sections

Sending

SMTP relay

Send through Hulaki from any app, CMS or device that speaks SMTP, with the same logs, suppression and tracking as the API.

The SMTP relay accepts mail from your applications and hands it to the same pipeline as the REST API: DKIM signing, suppression checks, tracking, logs and webhooks all apply. Use it when an app already supports SMTP and you don’t want to write code.

Connection settings

SettingValue
Hostsmtp.hulakimail.com
Port 587STARTTLS (recommended)
Port 465Implicit TLS (SSL)
Port 2525STARTTLS — use when your host blocks 587
AuthenticationPLAIN or LOGIN
UsernameYour SMTP credential username (hm_…)
PasswordThe credential’s password
EncryptionTLS 1.2 or newer, required before AUTH
The relay never accepts unauthenticated mail, and authentication is only allowed after TLS is established. Port 25 is not offered.

Credentials

Create credentials in Credentials → SMTP. Each one has its own username and a generated password that is shown once — store it in your app’s secret settings. Create a separate credential per application so you can rotate or revoke one without affecting others.

  • Allowed From domains: optionally restrict a credential to specific verified domains. Both the envelope sender and the From: header must match.
  • Rotate: generate a new password at any time; the old one stops working immediately.

Examples

import nodemailer from 'nodemailer';

const transport = nodemailer.createTransport({
  host: 'smtp.hulakimail.com',
  port: 587,
  secure: false,      // STARTTLS is negotiated automatically
  requireTLS: true,
  auth: { user: process.env.SMTP_USERNAME, pass: process.env.SMTP_PASSWORD },
});

await transport.sendMail({
  from: 'Acme <[email protected]>',
  to: '[email protected]',
  subject: 'Welcome to Acme',
  html: '<p>Thanks for signing up!</p>',
});

Limits

LimitValue
Message size30 MB including attachments (advertised via SIZE)
Recipients per message50 (To + Cc + Bcc)
Authentication failures5 per IP before a temporary 15-minute block
Monthly volumeShared with the API — see Limits & quotas

Messages per minute, per credential

PlanMessages / minuteEmails / month
Free603,000
Starter60050,000
Pro1,500250,000
Business3,0001,000,000

Reply codes

Temporary (4xx) replies mean “try again later” — well-behaved SMTP clients retry automatically. Permanent (5xx) replies won’t succeed on retry.

ReplyMeaning
250 2.0.0Accepted — the reply includes the message ID
451 4.7.1Rate limit reached — slow down
452 4.5.3Too many recipients, or monthly quota reached
454 4.7.0Authentication temporarily unavailable
530 5.7.0Authentication required
535 5.7.8Username or password incorrect
550 5.1.1Recipient suppressed or invalid
552 5.3.4Message too large
553 5.7.1From address not allowed — domain not verified or not permitted for this credential

Troubleshooting

  • Connection times out: many hosting providers block outbound port 587 or 465. Try port 2525.
  • “Must issue a STARTTLS command first”: enable TLS/STARTTLS in your client before authenticating.
  • 553 sender rejected: send from an address on a verified domain, and check the credential’s allowed domains.
Test the TLS handshake
openssl s_client -starttls smtp -connect smtp.hulakimail.com:587 -crlf -quiet

Something unclear or missing? Tell us.