Low-cost relay whose SMTP username is your account email and password is generated.
Search for your email provider
Outgoing mail (SMTP)
SMTP server
smtp.elasticemail.com
Port. STARTTLS
2525
Port. SSL/TLS
465
Security
STARTTLS on 2525 (recommended) or 587, or SSL/TLS on 465.
Incoming mail (IMAP)
IMAP
Not supported. This is a send-only service.
Incoming mail (POP3)
POP3
Not supported by this provider.
Sending limits & login
Daily send limit
Set by your Elastic Email plan.
Authentication
Use your Elastic Email account email address as the SMTP username and an API key as the password.
App password
Create the API key under Settings > SMTP/API.
Elastic Email is a send-only relay: there is no IMAP or POP inbox. Port 2525 is its documented default.
Sending cold email? EmailChaser manages inboxes, warmup and deliverability for you.
Try EmailChaser freeFind the SMTP, IMAP and POP3 server settings for any email provider. Free, with no signup, every field copies with one click.
Elastic Email is a low-cost sending service with an unusually old-fashioned login: your SMTP username starts out as the same email address you sign in with, rather than an API key or a fixed literal. The password is a credential you generate in the dashboard and can never read again once you close the window, and one account can hold at most 15 of them. The relay takes ports 25, 2525, 587 and 465.
Elastic Email is a send-only relay, so there's no IMAP or POP3 inbox. You only configure the SMTP server above. Use the tool to copy each value into your app or script.
Checked against Elastic Email's own documentation: help.elasticemail.com, elasticemail.com. Ports and limits change, so check there too if something will not connect.
One card with every server and port on it. Right click to save it, or share the page and this is the preview people see.

Wrong credentials, not a wrong port, are the usual reason a Elastic Email connection fails. These are the exact values to type.
Your Elastic Email account email address, the one you use to log in, unless you set a different unique address on the credential
The generated SMTP credential password, shown to you once at creation
Get your smtp credentialsThe exact path through Elastic Email's own settings, in order.
Create SMTP credentials
Open Account Settings > SMTP in the dashboard (https://app.elasticemail.com/marketing/settings/new/manage-smtp) and press Create SMTP Credentials. New accounts have none until you do this.
Copy the password before closing the window
Elastic Email shows the generated password once. After you close that window the dashboard obfuscates it and only ever shows the last five characters.
Enter the relay details
Server smtp.elasticemail.com. Elastic Email supports ports 25, 2525, 587 and 465, over TLS 1.2 or SSL. Check the port you pick is actually open outbound on your own server.
Use your account email as the username
The SMTP username defaults to the email address you sign in to Elastic Email with. You can set a different address when creating the credential, but it has to be unique across the whole system.
Authenticate your sending domain
Add the SPF and DKIM records for your domain under the Domains page (https://app.elasticemail.com/marketing/settings/new/manage-domains) so your mail is signed.
Every mail client asks for the same handful of fields. Here they are with Elastic Email's values already in place.
Account settings: Elastic Email
Server
smtp.elasticemail.comPort
2525Encryption
STARTTLSAuthentication
RequiredUsername
Your Elastic Email account email address, the one you use to log in, unless you set a different unique address on the credentialPassword
The generated SMTP credential password, shown to you once at creationIMAP / POP3
Not applicable. Elastic Email sends only, so there is no inbox to configure.An illustration of the fields, not a screenshot of any one app. Field names differ slightly between Outlook, Apple Mail and Thunderbird; the values do not.
The outgoing server dialog with Elastic Email's details entered. Outlook and Apple Mail ask for the same four things under slightly different names.

STARTTLS on 2525 (recommended) or 587, or SSL/TLS on 465.
STARTTLS
Starts as a plain connection, then upgrades to an encrypted one. The modern standard for sending.
SSL/TLS
Encrypted from the first byte. Widely supported and a good choice when 587 is blocked.
Plain SMTP
Meant for server-to-server relay. Home networks and cloud hosts block it, so do not use it to send from a client.
The failures people actually hit with Elastic Email, and what fixes each one.
There is no way to reveal it again. Delete that credential, create a new one, and update every application that was using the old one.
The free plan is capped at 100 emails a day and 1,000 contacts. Moving to a paid plan raises the daily figure according to the plan you pick.
Your account has been put Under Review, which Elastic Email describes as a temporary status. Delivery is paused and credit cannot be purchased, but mail you submit is queued and released if the account is reactivated. Clear it with their Customer Success team.
Elastic Email allows 20 concurrent requests from a single IP and times a single SMTP command out after 2 minutes. Reduce your worker count or reuse connections, since multiple emails can go down one session.
Each account can store up to 15 unique SMTP credentials. Delete one you no longer use before creating another.
Paid plans set their own daily figure; concurrency is capped at 20 requests from one IP and a single SMTP command times out after 2 minutes
Per day
100 emails a day on the free plan
Max attachment
10 MB for the whole email; any number of files as long as they fit inside that
Set by your Elastic Email plan. Use your Elastic Email account email address as the SMTP username and an API key as the password.
Those caps make single-mailbox sending fine for personal mail but a poor fit for cold outreach at volume. Emailchaser spreads sending across warmed inboxes and manages deliverability, so you can scale without burning Elastic Email accounts.
Setting up more than one mailbox? These sit in the same category as Elastic Email.
What are Elastic Email's SMTP settings?
Elastic Email's outgoing (SMTP) server is smtp.elasticemail.com. Use port 2525 (STARTTLS) or 465 (SSL/TLS). STARTTLS on 2525 (recommended) or 587, or SSL/TLS on 465. Sign in with the SMTP credentials Elastic Email issues you, not a mailbox address and password.
What is Elastic Email's IMAP or POP3 server?
Elastic Email is a send-only service, so it has no IMAP or POP3 inbox. You configure it as an outgoing SMTP server only.
Which port should I use for Elastic Email?
Use port 587 with STARTTLS wherever it's offered, it's the modern standard for authenticated sending. Port 465 with SSL/TLS is a solid alternative. Avoid port 25, which most networks block for client sending. Elastic Email's recommended value is above.
Why won't my Elastic Email SMTP connection work?
Check authentication first: Use your Elastic Email account email address as the SMTP username and an API key as the password. Create the API key under Settings > SMTP/API. Then confirm the host, port and security method match exactly, a 587/SSL or 465/STARTTLS mismatch will fail to connect.
Can I send bulk or cold email through Elastic Email?
Not at scale. Set by your Elastic Email plan. Providers throttle bursts to fight spam, so pushing cold email through one mailbox hits limits and wrecks deliverability. High-volume outreach belongs on dedicated infrastructure that spreads sending across warmed inboxes, which is what Emailchaser does.
What is my Elastic Email SMTP username?
By default it is the email address you use to log in to Elastic Email. This trips people up because most transactional relays want an API key or a fixed literal there. You can substitute another email address when you create the credential, as long as it is unique across Elastic Email's whole system. The password is not your login password: it is a separate credential you generate on the SMTP settings page.
Can I recover an SMTP password I did not write down?
No. Elastic Email displays the generated password once and then obfuscates everything except the last five characters. Your only option is to delete that credential and generate a fresh one, then update whatever was using it.
How many SMTP credentials can one account have?
Fifteen. That is enough to give each application its own credential, which is worth doing because you can then revoke one without disturbing the rest. Once you hit fifteen you have to delete an old one before adding another.
Ready to 10x your pipeline?
Send your first cold email campaign today.
Start my free trialAddress: 151 Calle de San Francisco San Juan, Puerto Rico
Email: support@emailchaser.com
Product
Cold Email SoftwareAutopilotEmail FinderCampaignsSales CRMLead FinderEmail AccountsEmail WarmupEmail VerifierCold Email APIMCP ServerAPI documentationWho it's for
FreelancersFoundersSales teamsMarketing agenciesRecruitment agenciesLead generation agenciesComparisons
Best cold email softwareInstantly alternativesSmartlead alternativesInstantly vs EmailchaserSmartlead vs EmailchaserHunter vs EmailchaserFree tools
All free toolsBulk Email VerifierDeliverability TestEmail Header AnalyzerSMTP Settings FinderCold Email TemplatesBoolean Search BuilderAudience Size CalculatorName SplitterCompany Email FormatSpam Word CheckerInternational
Cold email (ES)Cold email (FR)Cold email (DE)Cold email (IT)Cold email (PT)Verifica email (IT)© Copyright 2026 Emailchaser