Bobcares

Postfix disable TLS – How we do it easily?

by | Sep 26, 2019

Have you ever wondered why and how to disable TLS in postfix?

Postfix, one of the oldest mail servers need special care while enabling email security protocols.

Many times legacy or poorly configured servers only accept mails after disabling TLS.

As insecure TLS version cause security threats, we assist customers to effectively disable TLS in Postfix as part of our Server Management Services.

Today, let’s check why we disable TLS and how our Support Engineers do it for our customers.

Why Postfix disable TLS?

The Transport Layer Security protocol aka TLS provides end-to-end security of data sent via the Internet. So, it is widely used to protect websites.

By default, the Postfix SMTP server disable TLS in its configuration. However, many customers explicitly switch it on with the code smtpd_tls_security_level = encrypt in the configuration.

Again, the older versions of TLS are vulnerable to various security attacks. For instance, older versions of TLS can cause a BEAST attack, POODLE attack, etc.
Also, this creates problems when sending email to a specific host, which do not agree to the TLS standards.

Therefore, for better server security, we try to avoid older TLS versions.

 

How we disable TLS in Postfix?

So now, let’s get into some methods that our Support Engineers use to disable TLS.

Recently, one of our customers contacted us to help him disable TLS in Postfix.

For that, our Support Engineers updated the below setting in the Postfix config file at /etc/postfix/main.cf.

smtpd_tls_security_level = none

Setting the above value to none helps not to use TLS unless enabled for specific destinations.

As we have already said, older versions of SSL/TLS has many flaws. And, SSL v2/3 and TLS v1.0 are major insecure TLS protocol. The attackers use these versions to exploit vulnerabilities like beast and poodle.

Therefore, we also disable these insecure versions of SSL and TLS by editing the main.cf file.

smtpd_tls_mandatory_protocols = !SSLv2,!SSLv3,!TLSv1
smtp_tls_mandatory_protocols  = !SSLv2,!SSLv3,!TLSv1
smtpd_tls_protocols           = !SSLv2,!SSLv3,!TLSv1
smtp_tls_protocols            = !SSLv2,!SSLv3,!TLSv1

This helps to deactivate all the vulnerable versions of SSL and TLS and improves security.

Finally, we make the configuration changes active by restarting Postfix on the server. For this we use the commands:

service postfix stop
service postfix start

 

[Need more assistance to disable TLS in Postfix?- We’ll help you.]

 

Conclusion

In short, we can disable TLS in Postfix by adjusting the smtpd_tls_security_level in the Postfix configuration file. Today’s write up discussed the insecurities of older TLS versions and saw how our Support Engineers disable it for customers.

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

var google_conversion_label = "owonCMyG5nEQ0aD71QM";

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