How to enable inbound TLS(starttls) in Postfix with Signed Certificate from CA(LetsEncrypt)

-
article1
Most of the time Postfix is configured with self signed certificate which works well because mostly certificate validation is not required by MTAs. Though it can be useful for applications or mailbox users connecting to central MTA to delivery of emails.
You can either buy SSL certificate from your provider or use letscrypt.org free certificates(needs to be renewed every 3 months). In this guide, i will use letencrypt certificate for my mx host console.postfix.io.
I use letsencrypt utility to manage certificate for my domains, below command will generate standalone certificate for my host.
letsencrypt certonly --standalone -d console.postfix.io
The output…
Congratulations! Your certificate and chain have been saved at:/etc/letsencrypt/live/console.postfix.io/fullchain.pem Your key file has been saved at:/etc/letsencrypt/live/console.postfix.io/privkey.pem…
Edit main.cf
vim /etc/postfix/main.cf
Replace the following lines :
smtpd_tls_cert_file=/etc/ssl/certs/ssl-cert-snakeoil.pem
smtpd_tls_key_file=/etc/ssl/private/ssl-cert-snakeoil.key
to the following letsencrypt certificates path :
smtpd_tls_cert_file=/etc/letsencrypt/live/console.postfix.io/fullchain.pem
smtpd_tls_key_file=/etc/letsencrypt/live/console.postfix.io/privkey.pem
Reload postfix
systemctl reload postfix.service
You can verify certificate validation using http://checktls.com/perl/TestService.pl. See below test results after configuring for console.postfix.io
Postfix inbound TLS with letsencrypt

Comments

Post a Comment

Popular posts from this blog

StatusDnsQueryFailed resolving domain

-
Welcome file If you are seeing the following error in PowerMTA or Postfix logs : StatusDnsQueryFailed resolving domain It’s likely caused by 3 reasons : The requested domain does not exist. It doesn’t have neither MX nor A record. The upstream DNS provider is throttling excessive queries from your mail server. You are hitting bandwidth limits on either WAN(if the dns resolver request is going out via internet interface). As always, i highly recommend to use dedicated recursive DNS server on LAN for your mailing infrastructure or use unthrottled upstream DNS resolver.
Read more

How to include Gmail's Feedback-ID header in DKIM signature

-
article1 Feedback-ID is an additional header required by Gmail Feedback Loop to see aggregated data in Google Postmaster tools . Gmail requires it to include in DKIM-Signature. The following guide explains how it can be configured in OpenDKIM : Edit opendkim.conf vim /etc/opendkim.conf Add the following line : SignHeaders Feedback-ID Reload openkdim : systemctl reload opendkim.service Reload postfix : systemctl reload postfix.service Send a test email with swaks to gmail : swaks --from postmaster@postfix.io --to xxxx@gmail.com --h-Feedback-ID 123:asd:123 --server 127.0.0.1:25 My test mail results : Authentication-Results: mx.google.com;dkim=pass header.i=@postfix.io header.s=key1 header.b=oY1NVInb;spf=pass (google.com: domain of postmaster@postfix.io designates 45.55.57.182 as permitted sender) smtp.mailfrom=postmaster@postfix.io;dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=postfix.io Date: Sun, 12 Nov 2017 11:04:42 +0000 DKIM-Signature: v=1
Read more

How to send emails over IPv4 with Postfix

-
article1 “inet_protocols” directive is used to configure what Protocols Postfix should use to accept or make network connections. It also controls what DNS lookups Postfix will use. On Ubuntu 16.10, we found Postfix(3.1.0) was configured to use both IPv6 and IPv4. See below : inet_protocols = all (enable IPv4, and IPv6 if supported) IPv6 is always tried first and when it fails, it would try to deliver emails over IPv4. You can reconfigure it to listen on ipv4 IPs only : vim /etc/postfix/main.cf Replace “ all ” with “ ipv4 ” inet_protocols = ipv4 Restart postfix systemctl restart postfix.service
Read more