SMTP guide

Gmail, Outlook, IONOS and Hostinger SMTP: settings and limits

The server, port, authentication and sending limit for each provider, linked to its official help, and why website emails usually need a transactional SMTP.

Your mailbox's SMTP has limits designed for people

Gmail, Outlook, IONOS and Hostinger let you send over SMTP with the mailbox you already use, and it's the quickest way to get a plugin, an ERP or a printer sending emails. But those servers are built for email written by people: they limit how many messages go out per hour or per day and how you authenticate.

This guide brings together the settings and limits each provider publishes in its official help, so you know how far each one goes and when it's worth moving to a transactional SMTP.

Short answer

A mailbox's SMTP is meant for low volume: 500 emails a day on a personal Gmail account, 2,000 on Google Workspace, 10,000 recipients a day on Microsoft 365, between 50 and 500 an hour on IONOS and 1,000 or 3,000 a day per mailbox on Hostinger. If your website sends orders, sign-ups or customer notifications, a transactional SMTP with your authenticated domain avoids being blocked when you hit the limit and gives you a log of every email.

Summary

Server, port and limit for each provider

ProviderServer and portAuthenticationSending limit
Gmail (personal account)smtp.gmail.com · 587 (STARTTLS) or 465 (SSL)Sign in with Google (OAuth) or an app password with 2-Step Verification500 emails a day and 500 recipients per message
Google Workspacesmtp.gmail.com · 587 or 465. Relay: smtp-relay.gmail.com · 25, 465 or 587OAuth or app password. The relay authenticates by source IP2,000 messages a day per user and 100 recipients per message over SMTP. Relay: 10,000 recipients a day per user
Microsoft 365smtp.office365.com · 587 (STARTTLS)SMTP AUTH enabled on the mailbox; Microsoft recommends OAuth10,000 recipients a day and 30 messages per minute
Outlook.comsmtp-mail.outlook.com · 587 (STARTTLS)OAuth2 (Modern Auth)Microsoft's settings help doesn't publish a limit
IONOS (Mail Basic and Mail Business)smtp.ionos.com · 465 (SSL/TLS) or 587 (STARTTLS)Mailbox address and password; the sender must use the account's domainFrom 50 emails an hour for accounts up to 7 days old to 500 an hour after 30 days
Hostinger (Hostinger Mail)smtp.hostinger.com · 465 (SSL) or 587 (STARTTLS)Mailbox address and password1,000 emails a day per mailbox on Business Starter and 3,000 on Business Standard and Premium; 100 recipients per message

Figures checked on November 2, 2026 in each provider's official help, linked in each section. Providers can change them without notice.

Gmail

Gmail and Google Workspace SMTP

Gmail no longer supports third-party apps that connect with the account's username and password. To send through smtp.gmail.com (port 587 with STARTTLS or 465 with SSL), the app has to support Sign in with Google or use an app password, which requires 2-Step Verification and which Google doesn't recommend. On Google Workspace, apps and devices must use OAuth since May 1, 2025.

A personal account can send up to 500 emails a day; past that, Gmail blocks sending for 1 to 24 hours. On Google Workspace the limit is 2,000 messages a day per user, with at most 100 recipients per message when sending over SMTP, and once the limit is reached the user can't send new messages for up to 24 hours.

Workspace also offers the SMTP relay service (smtp-relay.gmail.com), which allows up to 10,000 recipients a day per user. It's set up in the Admin console and authenticates by source IP, so you usually need a static IP.

Outlook and Microsoft 365

Outlook.com and Microsoft 365 SMTP

Outlook.com (personal Microsoft accounts, Hotmail included) sends through smtp-mail.outlook.com, port 587 with STARTTLS, and requires modern authentication (OAuth2). Many plugins, ERPs and older devices only support a username and password, so they can't use it.

On Microsoft 365, authenticated sending (SMTP AUTH) goes through smtp.office365.com, port 587 with STARTTLS and TLS 1.2 or later; port 465 isn't supported. SMTP AUTH is disabled in organizations created after January 2020 and has to be enabled per mailbox. The limits are 10,000 recipients a day and 30 messages per minute, and Microsoft says bulk email should go through specialized providers.

Microsoft is retiring Basic authentication (username and password) for SMTP AUTH. Under its timeline updated in January 2026, nothing changes until the end of December 2026. It will then be disabled by default for existing tenants, though admins will be able to turn it back on, and tenants created afterwards won't have it by default. The final removal date will be announced in the second half of 2027.

IONOS

IONOS SMTP

IONOS mailboxes (Mail Basic and Mail Business) send through smtp.ionos.com (smtp.ionos.es in the IONOS Spain guides), on port 465 with SSL/TLS or, if your network blocks it, on 587 with STARTTLS. The username is the full email address.

The limit depends on how old the email account is: 50 emails an hour for the first 7 days, 100 up to 14 days, 400 up to 30 days and 500 an hour after that. Past the limit, the server replies with the error 450 Mail send limit exceeded.

Since January 29, 2024, IONOS rejects emails whose sender uses a different domain from the account's. That's what happens with contact forms that set the visitor's address as the sender: the sender has to be an address on your domain, with the visitor's address in Reply-To.

Hostinger

Hostinger SMTP

Hostinger Mail mailboxes send through smtp.hostinger.com, port 465 with SSL or, if that causes encryption problems, port 587 with STARTTLS, using the mailbox address and password.

Each mailbox can send 1,000 emails a day on Business Starter and 3,000 on Business Standard and Business Premium, with at most 100 recipients per message. Limits use a rolling 24-hour window and apply to each mailbox separately; trial mailboxes get 100 a day. An outgoing email can be up to 35 MB including attachments.

If your website sends with the hosting's PHP mail() function, without SMTP, the limit is much lower: 10 emails per minute and 100 a day. Hostinger recommends sending over authenticated SMTP, with PHPMailer or a plugin such as WP Mail SMTP.

Your website

Why a website needs a transactional SMTP

A website's emails (order confirmations, sign-ups, passwords, notifications) aren't written by anyone: they go out on their own, at any hour and in bursts. With a mailbox's SMTP, the day a spike in orders or sign-ups goes over the limit, the provider stops sending for hours and those emails never arrive.

A transactional SMTP is built for that job: it sends with your authenticated domain and tells you what happened to every email.

  • Limits sized for an application's volume, not for one person.
  • A sender on your domain, authenticated with SPF and DKIM, not tied to a specific mailbox.
  • Separate credentials for each website or app, apart from anyone's password.
  • A log of every email: delivered, bounced or rejected, and why.
  • No dependence on a mailbox provider's authentication changes, such as the retirement of Basic authentication.
  • Bounce handling, so you stop sending to addresses that don't exist.
FAQ

Frequently asked questions

Can I use my Gmail account for my WordPress emails?

Yes, if the plugin supports Sign in with Google or an app password, but with a personal account's limit of 500 emails a day and the sender tied to your Gmail address. For a store's emails or a service with customers, it falls short.

What happens if I go over the Gmail or Google Workspace limit?

Google blocks sending new messages: for 1 to 24 hours on a personal account and for up to 24 hours on Workspace. You keep receiving email in the meantime, but your website's emails don't go out.

Will my plugin stop working with Microsoft 365?

If it connects to smtp.office365.com with a username and password (Basic authentication), it keeps working as it does today until the end of December 2026. After that, Basic authentication will be disabled by default for existing tenants, though admins will be able to turn it back on until the final removal, whose date Microsoft will announce in the second half of 2027.

Why does IONOS reject my contact form emails?

Since January 29, 2024, IONOS rejects emails with a sender on a different domain. Set an address on your domain as the sender and put the visitor's address in Reply-To.

Is the hosting's PHP mail() function good enough?

For testing, yes; for production it isn't recommended. At Hostinger it's limited to 10 emails per minute and 100 a day, and it sends without authenticating your domain, which makes landing in spam more likely.

Mailiqo

A transactional SMTP for your website

Mailiqo sends your website's emails with your authenticated domain, over SMTP or API, and logs the status of every email in the dashboard. Start free, no card required.

Create a free account
Mailiqo Labs

Put the guide into practice

The tools let you check SPF, DMARC, headers, bounces and HTML with your own data, without registering.