Support

How to Open Outbound Port 25 (SMTP) on a VPS or Dedicated Server

  • 0

Why Is Port 25 Blocked by Default?

To protect our network infrastructure and prevent unsolicited bulk email (spam), ForceVPS blocks outbound TCP connections on port 25 (SMTP) by default.

This restriction applies to virtual private servers (VPS/VDS) and may also apply to dedicated servers hosted within our infrastructure.

Blocking outbound port 25 is a standard security practice among hosting providers and data centers. It helps prevent server IP addresses from being listed on international spam blocklists (DNSBL/RBL), reduces the risk of abuse, and maintains reliable email delivery for all customers.

Important: Blocking port 25 does not mean that email servers or outgoing email are prohibited. The restriction can be removed upon request by contacting our technical support team.

What Is Port 25 Used For?

TCP port 25 is used by the Simple Mail Transfer Protocol (SMTP), primarily for transferring email messages between mail servers.

For example, if you run your own mail server on a VPS and want to deliver email directly to Gmail, Outlook, Yahoo, or other email providers, outbound connectivity on port 25 may be required.

Common use cases include:

  • Hosting your own mail server using Postfix, Exim, Sendmail, or Microsoft Exchange.

  • Delivering email directly to recipients' MX servers.

  • Operating a corporate email infrastructure.

  • Configuring an SMTP server for automated system notifications.

  • Using a VPS as an email gateway.

  • Transferring email between independent mail servers.

If outbound port 25 is blocked, your mail server cannot establish direct SMTP connections to remote MX servers through that port.

However, receiving incoming email and sending messages through external SMTP services may still work when alternative ports are used and no additional restrictions apply.

Which SMTP Ports Are Available?

Opening port 25 is not always necessary for sending email. Depending on your email software and provider, alternative SMTP ports may be used.

Port Purpose Details
25 (SMTP) Server-to-server email delivery Outbound connections are blocked by default
465 (SMTPS) Encrypted SMTP submission Used for secure SMTP connections with implicit TLS
587 (Submission) Email submission through an SMTP server Recommended for authenticated email submission with STARTTLS
2525 (Alternative SMTP) Alternative email submission Supported by some third-party SMTP providers

Note: Port 2525 is not a universally standardized SMTP port. Its availability depends on the email service provider.

If you send email through an external SMTP service or your domain's mail provider, ports 465 or 587 are usually sufficient.

Port 25 is primarily required for direct server-to-server email delivery.

How to Open Outbound Port 25

To unblock outbound SMTP connections, you must contact ForceVPS technical support.

You cannot remove this restriction through your server's operating system, VPS control panel, or local firewall settings because the block is enforced at the hosting provider's network level.

Step 1. Log In to Your Client Area

Visit the ForceVPS website and sign in to your client account.

Step 2. Submit a Support Ticket

Navigate to the technical support section and create a new ticket requesting that outbound port 25 be unblocked.

We recommend including the following information:

  1. The IP address of the server requiring port 25 access.

  2. The name or identifier of your VPS/VDS or dedicated server service.

  3. The intended purpose of SMTP connectivity.

  4. The mail server software you plan to use.

  5. The expected type of email traffic, such as business correspondence, system notifications, or transactional emails.

Providing detailed information will help our technical support team review your request more efficiently.

Step 3. Wait for Your Request to Be Reviewed

Once your support ticket has been received, our technical support specialists will review whether the restriction can be removed.

In some cases, additional information about your mail server configuration and intended SMTP usage may be required.

Port 25 unblocking is subject to review and is not performed automatically.

Example Support Ticket

Subject: Request to Unblock Outbound TCP Port 25

Hello,

I would like to request that outbound TCP port 25 be unblocked on my server.

Server IP address: XXX.XXX.XXX.XXX

Purpose: Running a private mail server for corporate email communication.

Mail server software: Postfix.

The server will not be used for spam or unsolicited bulk email campaigns.

Thank you.

How to Check Whether Outbound Port 25 Is Open

After receiving confirmation from technical support, you can test outbound SMTP connectivity.

Checking Port 25 on Linux

Connect to your server via SSH and execute:

nc -vz -w 5 gmail-smtp-in.l.google.com 25

If the connection is successful, you should see output similar to:

Connection to gmail-smtp-in.l.google.com 25 port [tcp/smtp] succeeded!

This indicates that a TCP connection to the remote SMTP server has been established.

If the connection fails or times out, check your network configuration and the availability of the remote server.

You can also test connectivity using telnet:

telnet gmail-smtp-in.l.google.com 25

A successful connection may return an SMTP greeting similar to:

220 mx.google.com ESMTP

To close the connection, enter:

QUIT

Checking Port 25 on Windows Server

Open PowerShell and execute:

Test-NetConnection gmail-smtp-in.l.google.com -Port 25

If the connection is successful, the output will include:

TcpTestSucceeded : True

If you see:

TcpTestSucceeded : False

The TCP connection could not be established.

Important: A failed connection does not necessarily mean that ForceVPS is blocking the port. Other possible causes include local firewall rules, incorrect routing, remote server restrictions, or general network connectivity issues.

For accurate troubleshooting, we recommend testing connectivity to multiple independent SMTP servers.

What Should Be Configured After Opening Port 25?

Unblocking outbound SMTP traffic allows your server to establish connections to remote mail servers, but it does not guarantee successful email delivery.

For a reliable mail server setup, we recommend configuring the following components.

1. PTR (Reverse DNS)

Your mail server's IP address should have a properly configured reverse DNS (PTR) record.

For example:

IP: 192.0.2.10
PTR: mail.example.com

The hostname mail.example.com should also resolve back to the corresponding IP address.

Missing or incorrect reverse DNS records can cause email messages to be rejected or classified as spam.

If you cannot configure PTR records yourself, please contact technical support.

2. SPF

SPF (Sender Policy Framework) specifies which servers are authorized to send email on behalf of your domain.

Example DNS TXT record:

v=spf1 ip4:192.0.2.10 -all

In this example, only the specified IPv4 address is authorized to send email for the domain.

3. DKIM

DKIM (DomainKeys Identified Mail) provides a cryptographic signature for outgoing email messages.

Your mail server signs messages with a private key, while receiving servers verify the signature using a public key published in DNS.

Proper DKIM configuration helps establish trust in your outgoing email.

4. DMARC

DMARC defines how receiving servers should handle messages that fail SPF and DKIM authentication with domain alignment taken into account.

Example initial DMARC record:

v=DMARC1; p=none; rua=mailto:dmarc@example.com

The p=none policy is suitable for initial monitoring. After validating your authentication configuration, you may consider stricter policies.

5. Protection Against Open SMTP Relays

Make sure that your SMTP server does not allow unauthorized users to relay email through it.

An incorrectly configured open SMTP relay can be exploited by attackers to distribute large amounts of spam.

This may result in IP blacklisting, damage to your domain's email reputation, and renewed SMTP restrictions.

6. Checking Your IP Address Reputation

Before launching a mail server, we recommend checking whether your IP address appears on common DNSBL/RBL blocklists.

You can use:

Even with port 25 open, some email providers may reject messages originating from IP addresses with poor reputations.

Why Does ForceVPS Restrict Outbound Port 25?

Restricting outbound SMTP traffic is a preventive network security measure.

Virtual and dedicated servers may become sources of unsolicited email for several reasons:

  • Compromised websites, content management systems, or email applications.

  • Stolen or compromised user credentials.

  • Vulnerable SMTP server configurations.

  • Malware infections.

  • Servers intentionally deployed for spam distribution.

Even a single compromised server can generate significant amounts of spam within a short period.

As a result, the server's IP address may be added to international email blocklists. In some cases, abuse can also negatively affect the reputation of neighboring IP addresses or entire network ranges.

Blocking outbound port 25 by default helps prevent these incidents and protects the ForceVPS network infrastructure.

Frequently Asked Questions (FAQ)

Can I Open Port 25 Myself?

No. The restriction is enforced at the hosting provider's network level. Changing iptables, nftables, UFW, or Windows Firewall rules will not remove the ForceVPS network restriction.

You must submit a support ticket to request unblocking.

Can I Host My Own Mail Server?

Yes. You can deploy Postfix, Exim, Microsoft Exchange, or other email server software on your VPS or dedicated server.

If you need to deliver messages directly to remote MX servers over TCP port 25, outbound access must be enabled.

Do I Need Port 25 to Send Email From My Website?

Not necessarily.

If your website uses an external SMTP provider over port 465 or 587, opening outbound port 25 is usually unnecessary.

For example, OpenCart, WordPress, WHMCS, and other applications can send email through an authenticated SMTP service.

However, if the application uses a local mail server that delivers email directly to recipients' MX servers, outbound port 25 may be required.

Does Blocking Outbound Port 25 Affect Incoming Email?

Blocking outbound connections does not itself prevent incoming connections to TCP port 25.

However, to operate a fully functional mail server, you should separately verify incoming SMTP connectivity, DNS settings, and firewall rules.

Will Opening Port 25 Prevent My Emails From Going to Spam?

No.

Opening port 25 only enables SMTP network connectivity.

Email deliverability depends on factors such as IP and domain reputation, SPF, DKIM, DMARC, PTR records, mail server configuration, and message content.

Can Port 25 Be Blocked Again?

Yes. If spam activity, server compromise, or other security violations are detected, outbound SMTP connectivity may be restricted again.

Can I Request Port 25 Access for Multiple Servers?

Yes. Include the IP addresses of all relevant servers and explain the intended purpose of each one in your support ticket.

Each unblocking request is subject to review by technical support.

Conclusion

At ForceVPS, outbound TCP port 25 is blocked by default to prevent spam and protect our network infrastructure.

If you need to operate your own SMTP server with direct email delivery, you can request that this restriction be removed.

To open outbound port 25, submit a support ticket through your ForceVPS client area.

Include your server's IP address and describe how you intend to use SMTP.

Our technical support specialists will review your request and inform you whether the restriction can be removed.

If you use a third-party SMTP provider, we recommend checking whether ports 465 or 587 are supported before requesting port 25 access. In most cases, opening port 25 is unnecessary when using an external SMTP relay.

Was this answer helpful?