Transactional Email

SMTP Setup

Set up transactional email sending through Leadpush SMTP by verifying your sender identity, generating credentials, and testing from your application.

Leadpush transactional email setup has three required parts:

  1. a verified sending domain
  2. a verified sending address under that domain
  3. an SMTP credential your application can use to authenticate

Until those pieces are ready, your application may not be able to send live mail successfully through Leadpush.

SMTP connection settings

Use these SMTP connection values when configuring your application or integration:

  • SMTP host: smtp.leadpush.net
  • Port: 587

Use the username and password from your workspace SMTP credential for authentication.

Before you start

  • Work in the correct workspace, since domains, sending addresses, and SMTP credentials are all workspace-specific.
  • Decide which transactional use cases this workspace will send, such as password resets, receipts, one-time codes, or account alerts.
  • Make sure you can update DNS for the domain you plan to send from.
  • Have a monitored inbox ready for the sending address and a secure place to store SMTP secrets.
  • If you are unsure whether the mail should be transactional or marketing, read Transactional vs Marketing Emails.

Open the correct workspace

Switch into the workspace that will own the transactional email traffic.

Verify the sending domain and sender identity

Use Domain Setup for the setup sequence and Workspaces -> Email -> Sending Domains for the exact dashboard flow.

Create an SMTP credential

Generate the username and password your application will use. The transactional framing is documented in SMTP Credentials, and the exact dashboard flow is documented in Workspaces -> Email -> SMTP Credentials.

Configure and test your application

Add the Leadpush SMTP credential to your application or secret store, then run a test send through the same code path you expect to use in production.

What to verify before live sending

Before your team points real transactional traffic at Leadpush, confirm that:

  • at least one sending domain is verified
  • the exact sending address your app will use is verified
  • the SMTP credential is stored in the application or secret manager that will send mail
  • the workspace is ready for live delivery, not just Sandbox testing
  • a monitored inbox successfully receives a test email from the application path you plan to use in production
  • Use Domain Setup if your next blocker is DNS, sender identity verification, or sender-address setup.
  • Use SMTP Credentials if your next blocker is authentication for the application or integration.
  • Use Sending an Email when you want a concrete SMTP example to test from your application.
  • Use Add a Sending Domain if you want the broader onboarding version of the domain workflow.

Best practices

  • Create a separate SMTP credential for each application or environment so rotation is easier later.
  • Use a sender address your team actually monitors, especially for replies and operational follow-up.
  • Run a real end-to-end test from the app after every credential rotation or sender-address change.
  • Keep the transactional sender stable so operational mail remains predictable for users and internal teams.

Troubleshooting

Transactional Email

Learn how to set up transactional email sending through Leadpush SMTP with verified domains, sender identities, domain setup, and SMTP credentials.

SMTP Credentials

Learn how SMTP credentials fit into transactional email sending in Leadpush and where to create, rotate, and remove them in the dashboard.