Configure your account, choose a sending method, and start sending emails with Direct Mail.
Direct Mail supports triggered emails and batch emails sent through the console, API, or SMTP. Complete the setup below, then choose the sending method that fits your use case.
Region-specific resources
Email domains and sender addresses are region-specific. A sender address created in one region can only send emails from the console, API, or SMTP service in that same region.
Preparations
Complete the following steps in the Direct Mail console before sending emails. Steps 1 and 2 are required for all sending methods. Steps 3–5 are required for batch sending only. Steps 6 and 7 are optional.
-
Set an email domain — Required for all methods.
An email domain identifies your organization on outgoing emails. Every account must have an email domain.
-
Set a sender address — Required for all methods.
A sender address is the From address that appears on outgoing emails. To use SMTP, set an SMTP password on the sender address to enable SMTP sending.
-
Set an email tag — Required for batch sending.
Email tags classify batch emails for tracking and filtering in data statistics.
-
Create a recipient list — Required for batch sending via the console or BatchSendMail API.
Recipient lists store the addresses you send batch emails to. Reference a list when sending from the console or calling BatchSendMail.
-
Create an email template — Required for batch sending via the console or BatchSendMail API.
Email templates define the content and layout of batch emails sent from the console or through BatchSendMail.
-
Set up asynchronous notifications — Optional.
Asynchronous notifications report email delivery results. Enable this if you need delivery receipts for triggered or batch sends.
-
Enable IP protection — Optional.
IP protection restricts SMTP and API sending to authorized IP addresses, reducing the risk of unauthorized use.
Sending emails
Direct Mail supports three sending methods. Choose based on your use case:
Console: Send batch emails manually or test your setup. No code required.
API: Send triggered emails from your application, or call BatchSendMail for programmatic batch sending.
-
SMTP: Use SMTP if your application already integrates with an SMTP client or you want to send through an existing mail server.
Data and security
After you start sending, use the following resources to monitor performance and review delivery activity:
What's next
After completing setup and sending your first email, common next steps include:
Already sending from the console? Try the API or SMTP to automate sending from your application.
Need delivery receipts? Set up asynchronous notifications to receive callbacks for each delivery event.
Need to secure your SMTP integration? Enable IP protection to restrict sending to authorized IP addresses.
Ready to analyze results? View data statistics for sent emails to track delivery rates and engagement.