Skip to main content

Send Your First Transactional Email

Transactional email is the email your own application sends to one person at a time: order confirmations, password resets, sign-in links, invoices and account notifications. In Mumara ONE it goes through a Bridge. This quick start gets your first message out, over SMTP or the HTTP API.

Before you start

You need an Active sending domain for the From address. If you haven't set one up yet, see Sending Domains.

1. Check your sending domain​

Go to Setup → Sending Domains and make sure the domain you'll send from shows as Active. The From address of every transactional email must be on one of your verified sending domains, and the match is exact: to send from alerts@mail.example.com, verify mail.example.com itself.

2. Create a Bridge​

  1. Go to Transactional → Bridges and click Create a Bridge.
  2. Enter a Name you'll recognise, such as Order emails.
  3. Choose a Pool. On plans with dedicated infrastructure, pick the pool you set aside for transactional email, so it never shares a reputation with your marketing campaigns. See Dedicated Pools.
  4. Click Create.

The credentials appear straight away, under Method 1: Send via SMTP and Method 2: Send via API. You can come back to them at any time by clicking the Bridge's name. See Bridges for everything a Bridge can do.

Keep the credentials secret

Anyone with a Bridge's credentials can send email as you. Keep them in environment variables or your platform's secrets store, never in source code or browser JavaScript.

3. Send a message​

Pick whichever suits your application. Both go through the same Bridge.

Over SMTP​

Most frameworks, e-commerce platforms and CMS plugins have SMTP settings. Enter:

SettingValue
HostThe Host shown on the Bridge
Port587
EncryptionSTARTTLS (shown on the Bridge as TLS)
UsernameThe Bridge's Username
PasswordThe Bridge's Password

Then send a test email from your application, with a From address on your verified domain. SMTP Settings has the other ports, the rules each message follows, and PHPMailer and Nodemailer examples.

Over the HTTP API​

Copy the One Connect Key from the Bridge's Method 2: Send via API panel, then send one request:

curl -X POST https://api.mumara.com/sendEmail \
  -H "Authorization: Bearer YOUR_ONE_CONNECT_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "from": "Example Store <orders@example.com>",
    "to": "you@example.com",
    "subject": "Hello from Mumara ONE",
    "html": "<html><body><p>It works.</p></body></html>"
  }'

A response with "status": "success" means Mumara ONE accepted the message for delivery. Sending API covers every field, attachments and errors.

4. Check the result​

  • On Transactional → Bridges, click the chart icon in the Bridge's Sending Stats column to see its sent, delivered, bounced and complaint totals.
  • Analytics shows each message in the delivery logs, with what the receiving server said.

If the message didn't arrive, check your spam folder first, then the delivery logs.

If the message is refused​

The error mentionsWhat to do
is not authorized to relay emailsThe From domain isn't one of your verified sending domains. Verify it, or change the From address.
535, or Invalid loginThe username, password or key wasn't copied exactly. Copy it again from the Bridge.
The server doesn't offer authenticationYour SMTP client isn't encrypting the connection. Set it to STARTTLS on port 587.
Insufficient transactional creditsYour transactional allowance has run out. See Plan and Usage.

Next steps​

Last updated on