Linode Outbound Email Blocked: Ports 25, 465 and 587

How to fix it

Try these in order — the most common fix is first.

1. 1. Ask support to lift the SMTP block

   Copy steps
   1. Open a support ticket from Cloud Manager and explain what mail you send and how you prevent spam
   2. Support reviews the whole account and decides case by case, regardless of billing history
   3. Linode staff say they remove the restriction if the account looks fine; the account's billing history is not the only factor
   Did this fix it? Yes No

2. 2. Use an SMTP relay instead

   Copy steps
   1. Send through a transactional email service over an allowed port or an HTTPS API
   2. Configure your app to use the relay credentials rather than direct delivery
   Did this fix it? Yes No

Symptoms

Mail never leaves the server, telnet to an SMTP server on port 25 hangs, or your mail app reports it cannot connect to the SMTP server.

Why it happens

• Default restriction on outbound SMTP for accounts created after November 2019
• Account not yet reviewed by support

This guide also covers

• linode port 25 blocked
• linode can't send email
• linode smtp blocked
• linode port 587 blocked

The same problem in other apps

All plan limits, paywalls & watermarks guides →

• DigitalOcean Account Locked or Verification Required (DigitalOcean)
• Vultr SMTP Port 25 Blocked (Vultr)

Other Linode errors

• Can't SSH Into Linode: Connection Refused or Timed Out
• Linode SSH Permission Denied (publickey)
• Linode Unreachable After Reboot, Maintenance or Firewall Change
• Linode Lish Console Not Working or Login Fails
• Linode Out of Memory: OOM Killer Kills MySQL, Apache or Node
• Linode Account Pending, Verification Required or Limit Reached
• Linode Still Charging After Powering Off: You Must Delete It
• How to Cancel Linode (Akamai Cloud) Account and Stop Billing