Migrate from Mailgun

• An app that already sends through Mailgun’s SMTP changes its SMTP settings, and nothing else.
• An app that calls Mailgun’s HTTP API replaces those calls with an SMTP client, as in the examples below. It can also call Hiveku’s REST API instead.

​

Before you switch

​

Change your SMTP settings

​

Examples

import fs from "node:fs";
import nodemailer from "nodemailer";

const transporter = nodemailer.createTransport({
  host: "smtp.hiveku.com",
  port: 465,
  secure: true,
  auth: { user: "apikey", pass: process.env.HIVEKU_EMAIL_API_KEY },
});

const info = await transporter.sendMail({
  from: "Acme <billing@mail.acme.com>",
  to: "customer@example.com",
  replyTo: "support@acme.com",
  subject: "Your invoice #1024",
  text: "Your invoice is attached.",
  html: "<p>Your invoice is attached.</p>",
  attachments: [
    { filename: "invoice-1024.pdf", content: fs.readFileSync("invoice-1024.pdf") },
  ],
});

console.log(info.response); // 250 Message queued: <the email's id>

import os
import smtplib
from email.message import EmailMessage

msg = EmailMessage()
msg["From"] = "Acme <billing@mail.acme.com>"
msg["To"] = "customer@example.com"
msg["Reply-To"] = "support@acme.com"
msg["Subject"] = "Your invoice #1024"
msg.set_content("Your invoice is attached.")
msg.add_alternative("<p>Your invoice is attached.</p>", subtype="html")

with open("invoice-1024.pdf", "rb") as f:
    msg.add_attachment(f.read(), maintype="application", subtype="pdf", filename="invoice-1024.pdf")

with smtplib.SMTP_SSL("smtp.hiveku.com", 465) as smtp:
    smtp.login("apikey", os.environ["HIVEKU_EMAIL_API_KEY"])
    smtp.send_message(msg)

​

What changes

• Provider headers. If your messages carry X-Mailgun- headers, remove them. Hiveku does not read them, and it passes X- headers on to recipients as they are.
• Tags. SMTP messages carry no tags. If you filter events by tag, send those emails through the REST API.
• Scheduling. Hiveku cannot hold a message for later. Send it when it should go.
• Templates. Build the message in your app, or send a Hiveku template through the REST API.
• Recipients. At most 50 per message. Recipients not named in the To or Cc header get a hidden copy, as Bcc.
• Size. At most 25 MB per message.
• Test keys. A test key’s messages are accepted and simulated: the reply says nothing was delivered.

​

Suppressions

curl -X POST https://app.hiveku.com/api/v1/email/suppressions \
  -H "Authorization: Bearer $HIVEKU_SUPPRESSIONS_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "email": "bounced@example.com", "reason": "Bounced at Mailgun" }'

​

After the switch

• Watch Settings > Email Service > Email Logs, in the App sends (API and SMTP) view, as your app’s email moves over.
• Test with a test key, not a trickle of real sends. Simulated sends are not counted, so they do not set a small usual day for the daily volume check. If your account already sends API mail on most days, moving a large app over in one go can pass 5 times that usual day and hold API and SMTP mail until 00:00 UTC.
• Once nothing sends through Mailgun, remove its DNS records for sending and its include: from your SPF record. Keep its MX records if it still receives mail for you.