Skip to main content
Use the turboSMTP SMTP relay with an email client, CMS, or application that supports authenticated SMTP. The relay accepts and queues your outbound messages, then handles delivery attempts. Your plan determines sending allowances and access to features such as dedicated IPs and analytics retention.

​
Connection settings

Both hosts support the same ports. turboSMTP is an Italian company with European sending infrastructure; use pro.eu.turbo-smtp.com for the EU route. See data residency for contractual considerations.

​
Choose encryption

  • On 587, 2525, or 25, connect with SMTP and require a STARTTLS upgrade before authentication.
  • On 465 or 25025, start the connection with TLS enabled (implicit TLS).
  • Use 2525 when your network blocks 587. Hosting providers often block 25.
For libraries such as Nodemailer, secure: true means implicit TLS and belongs with ports 465 or 25025. On port 587, use secure: false together with requireTLS: true to require STARTTLS.

​
Configure and verify

1

Create credentials

In the dashboard, open Settings → Integrations → API Keys → Edit. Create a key with SMTP Sending enabled. Copy the Consumer Secret when it is shown and store it securely.
2

Set your client's outgoing mail server

Enter a host, port, and matching encryption mode from the table. Enter the Consumer Key as the username and Consumer Secret as the password. Your dashboard login password is not the SMTP password.
3

Send a message

Send to an address you control. Open Analytics in the dashboard to inspect the delivery record. Successful SMTP authentication confirms your credentials; a queued message is not yet proof of delivery to the recipient’s server or inbox.
See SMTP setup for client instructions and common errors for connection and authentication troubleshooting.

​
Plans and limits

The Free plan allows up to 200 emails per day. Paid sending allowances depend on your chosen plan. Dedicated IPs are a Pro feature rather than part of every relay account. Check the pricing comparison for current plan limits, trials, and support channels. Both SMTP and the HTTP send API support email bodies and attachments. Choose the protocol that fits your application.