Send with SMTP

Anything that can send email over SMTP can send from your inboxes: a framework’s mailer, a CRM, a printer, smtplib. Log in with an API key as the password. The message goes through exactly the same checks and delivery as POST /v1/inboxes/:id/messages/send, and shows up in the API and the dashboard like any other sent message.

#Settings

import nodemailer from 'nodemailer';

const smtp = nodemailer.createTransport({
  host: 'smtp.agentboxd.com',
  port: 587, // STARTTLS; or port: 465, secure: true
  auth: { user: 'support-bot@homingbox.net', pass: process.env.AGENTBOXD_API_KEY },
});

const info = await smtp.sendMail({
  from: 'support-bot@homingbox.net',
  to: 'dana@example.com',
  subject: 'Your refund',
  text: 'Hi Dana, the refund is on its way.',
});
console.log(info.response); // 250 2.0.0 Queued as <message id>

import os
import smtplib
from email.message import EmailMessage

msg = EmailMessage()
msg["From"] = "support-bot@homingbox.net"
msg["To"] = "dana@example.com"
msg["Subject"] = "Your refund"
msg.set_content("Hi Dana, the refund is on its way.")

with smtplib.SMTP("smtp.agentboxd.com", 587) as smtp:
    smtp.starttls()
    smtp.login("support-bot@homingbox.net", os.environ["AGENTBOXD_API_KEY"])
    smtp.send_message(msg)

#Who you can send as

The envelope sender (MAIL FROM) must be one of the key’s inboxes: any inbox of the workspace for a workspace key, only its inbox for an inbox-scoped key. The From: header must be the same address. Temporary inboxes are receive-only, and inboxes on a custom domain need the domain verified, as with the API. Otherwise the server answers 550 5.7.1.

#What happens to the message

• The recipients are the SMTP envelope recipients (up to 50). Each one appears as To or Cc if the header lists it, otherwise it is sent as Bcc.
• Subject, text, HTML and attachments are kept. From is set to the inbox address and display name, and the message gets our own Message-ID, as every API send does. Other headers are not carried over, and inline cid: images are sent as ordinary attachments.
• In-Reply-To and References are kept. When they point at a message in the same inbox, the new message joins that thread, and your reply allow/block lists apply as with POST …/reply.
• Suppression, allow/block lists, the monthly email quota, the 5-minute burst limit, daily sending caps, size limits (MAX_MESSAGE_BYTES) and DKIM signing all apply. The message counts toward usage exactly like an API send, and fires message.sent (then delivery events) on webhooks and the event stream.
• The reply is 250 2.0.0 Queued as <message id>: fetch it with GET /v1/messages/:id.
• Resubmitting a message with the same Message-ID within 24 hours (a client retrying after a timeout) doesn’t send it twice.

#Errors