What is SMTP (and why your site needs it)?
A plain-English explanation of SMTP — the protocol that sends email — and why your website needs it configured correctly.
- Difficulty
- Beginner
SMTP is a behind-the-scenes technical standard — you never see it directly, but it's what makes email work. Understanding the basics helps you know why website emails sometimes fail and what to do about it.
Quick summary
SMTP (Simple Mail Transfer Protocol) is the system that carries email from sender to recipient. Your website uses SMTP to send automatic emails. Without a properly configured SMTP setup, website emails go to spam or don't arrive at all. Chykalophia configures this when we build your site.
What is SMTP?
SMTP stands for Simple Mail Transfer Protocol. It's the set of rules (a "protocol") that email servers use to send and receive messages.
Think of it like the postal service — SMTP is the delivery network that carries an email from the sender's mail server to the recipient's mail server.
Every email you send — whether from Gmail, Outlook, or your website — passes through SMTP at some point.
Why does my website need SMTP?
Your website sends emails automatically: contact form notifications, order confirmations, password resets. For these to arrive reliably, your website needs to connect to a proper mail server using SMTP.
Without SMTP configured, most websites fall back to a basic server function called PHP mail. This works in theory but:
- Nothing signs the message with DKIM unless someone has set that up, and Google says every sender to personal Gmail accounts must have SPF or DKIM in place for mail to be delivered as expected
- Is shared with all other sites on the same server — if any of them send spam, your deliverability suffers
- Provides no tracking or delivery logs
- Is disabled or restricted by some hosting providers
Proper SMTP configuration connects your website to a trusted email service and solves all these problems.
How SMTP works (the simple version)
Your website generates an email — e.g., an order confirmation after a purchase.
The website connects to an SMTP server using credentials (a username, password, and server address). This is like logging into a mail service.
The SMTP server sends the email to the recipient's mail server.
The recipient's server delivers it to their inbox (or spam folder, depending on authentication and reputation).
Both paths reach the same mail server. The difference is what the email is carrying when it gets there — and that is what decides which folder it lands in.
Read this as text
Your website sends email on its own: contact form notifications, order confirmations, password resets. Where that email goes next depends on one setting.
With SMTP configured, the site logs in to a real mail service using a username, password and server address. That service signs the message and keeps delivery logs, then passes it to the recipient’s mail server. Because the message is authenticated and the sending service has its own reputation, it normally lands in the inbox.
Without it, the site falls back to a basic server function called PHP mail. The message goes to the same recipient server, but with no authentication signature, no delivery log, and a sending reputation shared with every other site on that server — so if any of them sends spam, yours is doubted too. Some hosts block it outright.
Same sender, same recipient, same destination server. The only difference is what the email can prove about itself on arrival, and that is what decides the folder.
SMTP credentials
To connect your website to an SMTP server, you need four pieces of information:
| Setting | Example | What it means |
|---|---|---|
| SMTP host | smtp.postmarkapp.com | The address of the mail server |
| SMTP port | 587 or 465 | The connection port. On 587 the connection starts in the clear and switches to TLS (STARTTLS); on 465 it is encrypted from the moment it opens, which mail apps often label SSL |
| Username | Your account email or API key | Authenticates your website |
| Password | Your account password or API secret | Authenticates your website |
These credentials come from whichever SMTP service you're using. Chykalophia stores and manages these for the sites we build.
Which SMTP service should my site use?
| Service | Best for |
|---|---|
| Postmark | Reliable transactional email; detailed message logs |
| SendGrid | Higher volumes; check its pricing page for current plans and limits |
| Mailgun | Developer-focused; good for mixed use |
| Google Workspace (via Gmail SMTP) | Very small sites; Google caps how much a mailbox can send per day |
| Microsoft 365 (via Outlook SMTP) | Small sites already on Microsoft 365. Microsoft turns SMTP AUTH off by default for organizations created after January 2020, so an admin has to enable it per mailbox |
For most small business websites, a dedicated transactional service like Postmark or SendGrid is the better choice. They're built for this, and they give you delivery tracking you can actually read. Prices change, so check the provider's own pricing page before you commit.
SMTP on WordPress
WordPress has a default email system that often doesn't work well. The most common fix is to install an SMTP plugin that replaces the default system with a proper SMTP connection.
Popular WordPress SMTP plugins include WP Mail SMTP and FluentSMTP. Chykalophia installs and configures these as part of building your site.
Common questions
My website was working fine and now emails have stopped. What happened?
SMTP credentials can expire or be revoked — especially if a password was changed, an API key was regenerated, or an account was upgraded. Contact Chykalophia to check and update the SMTP configuration.
What port should SMTP use?
Port 587 and port 465 are both standard for sending, and the IETF standard on using TLS for email submission (RFC 8314) says clients and servers should support both. Neither is more secure than the other when both ends are set up correctly. Port 25 is the older option: Microsoft's own guidance notes that some network firewalls and internet providers block it, because that port is what mail servers use to pass messages between themselves. Your SMTP provider will specify the correct port — Postmark, for example, lists 25, 2525, and 587.
Can I use my own Gmail address as the SMTP server?
Yes, but with important caveats. Google caps how many messages an account can send per day, and says those limits can change without notice — so check Google's own sending-limits page rather than relying on a number you read somewhere. Since 14 March 2025 Google has switched off plain username-and-password access for SMTP, IMAP and POP, so the connection has to use OAuth or an app password. For most business sites, a dedicated SMTP service is more reliable.
How do I test whether SMTP is working?
The simplest test is to submit your own contact form and see if you receive the notification. For WooCommerce, place a test order. Many SMTP plugins also have a built-in "send test email" feature. If you're not sure, ask Chykalophia to run a diagnostic.
Related guides
- Email sent from your website explained
- Transactional vs marketing email
- SPF, DKIM & DMARC for email senders
- Why your emails land in spam
- Troubleshooting email problems
Need a hand?
Learn more
Last updated
Why email & your website are separate
Your email and your website don't have to live on the same platform — and for most businesses, they shouldn't.
Transactional vs marketing email
The difference between transactional emails (order confirmations, password resets) and marketing emails (newsletters, promotions) — and why they need different tools.