An SMTP server (Simple Mail Transfer Protocol) is the dedicated server that handles outgoing email. When your application, CRM or website sends a message, it talks to an SMTP server, which authenticates the request, queues the message and delivers it to the recipient’s mailbox provider. An SMTP relay is a managed SMTP service designed to send transactional and marketing emails reliably at scale — without the headaches of running your own mail server.

In short: Plain SMTP = the protocol email uses. SMTP relay = a managed service that takes your message, authenticates it (SPF/DKIM), boosts deliverability and sends it from a trusted IP.

How an SMTP relay works in 4 steps

1. Your app connects to the relay server (e.g. smtp.mailpro.com:587) over TLS. 2. It authenticates with username and password (or API token). 3. It hands the message to the relay. 4. The relay signs it (DKIM), routes it through a high-reputation IP and tracks delivery, opens and clicks.

SMTP relay vs other sending options

OptionBest forLimits
Personal SMTP (Gmail, Outlook)A few personal emails per day~500/day, no transactional, low deliverability
Self-hosted PostfixFull technical controlYou manage IP reputation, blacklists, queues yourself
SMTP relay (Mailpro)Transactional + marketing at any volumePay per email or monthly plan
Email API (REST)Tightly integrated appsRequires SDK or HTTP code

The right SMTP port

PortProtocolRecommended use
25Plain SMTPServer-to-server only — usually blocked by ISPs
465SMTPS (implicit TLS)Legacy compatibility
587Submission with STARTTLSRecommended for client-to-relay
2525Submission alternativeFallback if 587 is blocked

Mailpro accepts ports 587 (recommended), 465 and 2525.

Important: Never put your SMTP password in client-side code. Store it on the server, use environment variables, and rotate it if exposed.

Why use a managed SMTP relay

Managed relays handle the four hardest parts of sending email at scale: maintaining IP reputation, configuring SPF/DKIM/DMARC, dealing with bounce-back loops and following ISP rate limits. They typically achieve 98%+ inbox placement out of the box, which is unrealistic for a self-hosted server without a dedicated team. Read more in our blog post on what is SMTP relay and SMTP vs email API.

Setting up Mailpro’s SMTP relay

1. Open Account → SMTP credentials. 2. Generate a username and password. 3. Use them in your application’s SMTP settings. 4. Authenticate your domain with SMTP authentication for higher deliverability. Detailed steps: how to send emails with SMTP server.

Send transactional email at scale

Mailpro’s SMTP relay handles authentication, deliverability and tracking out of the box. Read the full SMTP relay FAQ or visit the SMTP page.

Related: how to integrate Mailpro with WordPress.

Previous question

   

Next question

You might also be interested in:

What Are the Differences Between Texting and Email?

Texting and email both deliver written messages, but they target very different moments. SMS goes straight to the phone in...

Read more

MSISDN: Definition and Format (CC+NDC+SN)

MSISDN stands for Mobile Station International Subscriber Directory Number. It is the worldwide format your SMS gateway uses to identify...

Read more

How to Fix Error 5.7.1 (Relay Access Denied)

Code 5.7.1 « Relay access denied » means the SMTP server you connected to refuses to forward your message to...

Read more

What Does Emailing Mean?

Emailing refers to the practice of sending email at scale — usually to a list of contacts — for marketing,...

Read more

What Is SMTP Error 554 and How to Fix It?

SMTP error 554 is a permanent rejection: the recipient server refused to accept your email. The good news? Once you...

Read more

Unleash the Power of Professional Email Marketing

Secure, scalable, and built for impact. Join Mailpro™ today and enjoy 500 free credits to send your first campaign.
Start Sending for Free