Bobcares

Vultr Blocks SMTP | About

by | Dec 22, 2023

Learn how to block SMTP traffic in Vultr. Our Vultr Support team is here to help you with your questions and concerns.

Vultr blocks SMTP

In the world of server security, blocking outbound SMTP traffic stops instances from helping with spam distribution.

Vultr blocks SMTP

Today, we will look at blocking SMTP traffic and offering practical solutions for users managing Vultr servers, including considerations for SMTP relay services, alternative ports, TLS usage, and configuring Reverse DNS (rDNS).

Blocking Outbound SMTP Traffic

Spammers often exploit cloud services to set up temporary instances for mass spam distribution, using the resources and global reach of cloud platforms. Blocking outbound SMTP traffic acts as a proactive defense against these malicious activities.

Solution 1. SMTP Relay Services

We can use reputable SMTP relay services to handle outbound email delivery. These services are often more leniently regulated by cloud providers, offering an alternative to direct email transmission from our Vultr instance.

Solution 2: Use Port 587 or TLS

Some cloud providers restrict SMTP port 25 but allow alternative ports like 587. Utilizing Transport Layer Security (TLS) for SMTP connections boosts security and is often permitted for email communication.

Solution 3: Configure Reverse DNS (rDNS)

We have to make sure our Vultr instance has a valid Reverse DNS (rDNS) record. Some email servers use rDNS to verify the sending server, adding an extra layer of security.

Opening Ports in Vultr Servers

By default, certain ports, including mail port 25, are not open on Vultr servers. Hence, we have to manually open the port if we want to make our email server work on port 25.

We can do this via one of the following methods:

 

  • Using iptables:

    First, modify iptables rules on the Vultr server to open ports. Then, run this command to allow a specific port, e.g., port 25:

    # iptables -A INPUT -p tcp --dport 25 -j ACCEPT

  • Via Vultr Firewall Service:

    We can use Vultr’s website-based firewall solution. This involves creating a firewall group via the control panel, adding desired rules, and managing packet filtering at a higher network level.

  • Using Firewall Utilities (UFW, CSF):

    For users who need additional security and refined rule customization, we can use firewall utility tools like UFW and CSF. UFW, installed by default on Vultr servers, lets us open ports with this command:

    $ sudo ufw allow 25/tcp

    Please note that we have to disable the default firewall application (firewalld) for the proper functioning of CSF in CentOS 7 instances.

[Need assistance with a different issue? Our team is available 24/7.]

Conclusion

Today, our Support Engineers demonstrated how to block SMTP traffic in Vultr.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF