Skip to content

Elastic Email

You add Elastic Email to Mailway as Any SMTP server. Mailway signs in to Elastic Email’s SMTP server with an Elastic Email SMTP credential and hands each mail over.

  • An Elastic Email account with your sender domain verified. See Deliverability for what each record proves.
  • An Elastic Email SMTP credential, created in Elastic Email’s SMTP settings. Its username defaults to the email address you sign in to Elastic Email with. Elastic Email shows the password once, when the credential is created, so copy it then.
  1. Add the provider.

    In the console, open Providers → New provider and pick Any SMTP server. Fill in:

    Field Value
    Server smtp.elasticemail.com
    Port 2525 or 587, or 465
    Encryption STARTTLS for 2525 and 587, SSL/TLS (implicit) for 465
    Username the Elastic Email SMTP credential’s username
    Password the Elastic Email SMTP credential’s password
    TLS verification leave it on

    Secrets are encrypted at rest.

  2. Attach it to a project.

    Open the project, attach the provider, and position it in the failover order.

Mailway doesn’t read delivery reports from Elastic Email, so the last state a mail can reach is accepted, when Elastic Email takes it. Bounces and complaints that Elastic Email learns about later don’t reach Mailway, and they aren’t added to the project’s suppression list.

The provider page’s connection check signs in to Elastic Email’s SMTP server and closes the connection without sending anything. It tells you if the server, port, encryption, or credentials are wrong.

If open or click tracking is on in your Elastic Email account, the delivered copy carries a tracking pixel and rewritten links. Mailway’s own archive always keeps the message as your app sent it.

Your Elastic Email plan’s own sending limits apply.