Tutorial

How to Install and Configure Postfix as a Send-Only SMTP Server on Ubuntu 16.04

Published on April 30, 2016
How to Install and Configure Postfix as a Send-Only SMTP Server on Ubuntu 16.04
Not using Ubuntu 16.04?Choose a different version or distribution.
Ubuntu 16.04

Introduction

Postfix is a mail transfer agent (MTA), an application used to send and receive email. In this tutorial, we will install and configure Postfix so that it can be used to send emails by local applications only — that is, those installed on the same server that Postfix is installed on.

Why would you want to do that?

If you’re already using a third-party email provider for sending and receiving emails, you do not need to run your own mail server. However, if you manage a cloud server on which you have installed applications that need to send email notifications, running a local, send-only SMTP server is a good alternative to using a 3rd party email service provider or running a full-blown SMTP server.

In this tutorial, you’ll learn how to install and configure Postfix as a send-only SMTP server.

Note: As of June 22, 2022, DigitalOcean is blocking SMTP for all new accounts. As a part of this new policy, we have partnered with SendGrid so our customers can still send emails with ease. You can learn more about this partnership and get started using SendGrid by checking out our DigitalOcean’s SendGrid Marketplace App.

Prerequisites

To follow this tutorial, you will need:

Note that your server’s hostname should match this domain or subdomain. You can verify the server’s hostname by typing hostname at the command prompt. The output should match the name you gave the Droplet when it was being created.

Step 1 — Installing Postfix

In this step, you’ll learn how to install Postfix. The most efficient way to install Postfix and other programs needed for testing email is to install the mailutils package.

First, update the package database:

  1. sudo apt-get update

Finally, install Postfix. Installing mailtuils will install Postfix as well as a few other programs needed for Postfix to function.

  1. sudo apt install mailutils

Near the end of the installation process, you will be presented with a window that looks exactly like the one in the image below. The default option is Internet Site. That’s the recommended option for this tutorial, so press TAB, then ENTER.

Select Internet Site from the menu, then press TAB to select <Ok>, then ENTER

After that, you’ll get another window just like the one in the next image. The System mail name should be the same as the name you assigned to the server when you were creating it. If it shows a subdomain like subdomain.example.com, change it to just example.com. When you’ve finished, press TAB, then ENTER.

Enter your domain name, then press TAB to select <Ok>, ENTER

After installation has completed successfully, proceed to step two.

Step 2 — Configuring Postfix

In this step, you’ll read how to configure Postfix to process requests to send emails only from the server on which it is running, that is, from localhost.

For that to happen, Postfix needs to be configured to listen only on the loopback interface, the virtual network interface that the server uses to communicate internally. To make the change, open the main Postfix configuration file using nano or your favorite text editor.

  1. sudo nano /etc/postfix/main.cf

With the file open, scroll down until you see the following section.

/etc/postfix/main.cf
. . .
mailbox_size_limit = 0
recipient_delimiter = +
inet_interfaces = all
. . .

Change the line that reads inet_interfaces = all to inet_interfaces = loopback-only.

/etc/postfix/main.cf
. . .
mailbox_size_limit = 0
recipient_delimiter = +
inet_interfaces = loopback-only
. . .

Another directive you’ll need to modify is mydestination, which is used to specify the list of domains that are delivered via the local_transport mail delivery transport. By default, the values are similar to these:

/etc/postfix/main.cf
. . . mydestination = $myhostname, example.com, localhost.com, , localhost . . .

The recommended defaults for that scenario are given in the code block below, so modify yours to match:

/etc/postfix/main.cf
. . . mydestination = $myhostname, localhost.$mydomain, $mydomain . . .

Save and close the file.

If you’re hosting multiple domains on a single server, the other domains can also be passed to Postfix using the mydestination directive. However, to configure Postfix in a manner that scales and that does not present issues for such a setup involves additional configurations that are beyond the scope of this article.

Finally, restart Postfix.

  1. sudo systemctl restart postfix

Step 3 — Testing the SMTP Server

In this step, you’ll test whether Postfix can send emails to an external email account using the mail command, which is part of the mailutils package that was installed in Step 1.

To send a test email, type:

  1. echo "This is the body of the email" | mail -s "This is the subject line" your_email_address

In performing your own test(s), you may use the body and subject line text as-is, or change them to your liking. However, in place of your_email_address, use a valid email address. The domain part can be gmail.com, fastmail.com, yahoo.com, or any other email service provider that you use.

Now check the email address where you sent the test message. You should see the message in your inbox. If not, check your spam folder.

Note that with this configuration, the address in the From field for the test emails you send will be sammy@example.com, where sammy is your Linux username and the domain part is the server’s hostname. If you change your username, the From address will also change.

Step 4 — Forwarding System Mail

The last thing we want to set up is forwarding, so you’ll get emails sent to root on the system at your personal, external email address.

To configure Postfix so that system-generated emails will be sent to your email address, you need to edit the /etc/aliases file.

  1. sudo nano /etc/aliases

The full contents of the file on a default installation of Ubuntu 16.04 are as follows:

/etc/aliases
# See man 5 aliases for format
postmaster:    root

With that setting, system generated emails are sent to the root user. What you want to do is edit it so that those emails are rerouted to your email address. To accomplish that, edit the file so that it reads:

/etc/aliases
# See man 5 aliases for format postmaster: root root: your_email_address

Replace your_email_address with your personal email address. When finished, save and close the file. For the change to take effect, run the following command:

  1. sudo newaliases

You may now test that it works by sending an email to the root account using:

  1. echo "This is the body of the email" | mail -s "This is the subject line" root

You should receive the email at your email address. If not, check your spam folder.

Conclusion

That’s all it takes to set up a send-only email server using Postfix. You may want to take some additional steps to protect your domain from spammers.

If your use case is to receive notifications from your server at a single address, emails being marked as spam is a major issue because you can whitelist them. However, if your use case is to send emails to potential site users (such as confirmation emails for a message board sign-up), you should definitely set up SPF records and DKIM so your server’s emails are more likely to be seen as legitimate.

If configured correctly, this makes it difficult to send spam with an address that appears to originate from your domain. Doing these additional configuration steps will also make it more likely for common mail providers to see emails from your server as legitimate.

Thanks for learning with the DigitalOcean Community. Check out our offerings for compute, storage, networking, and managed databases.

Learn more about our products

About the author(s)

Category:
Tutorial

Still looking for an answer?

Ask a questionSearch for more help

Was this helpful?
 
30 Comments
Leave a comment...

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Excelent!

the best gan

Many thanks for this very useful tutorial!

This guide works too for Debian 8 Jessie, with one difference:

The package mailutils does not contain postfix, so the postfix package has to be installed too:

sudo apt-get install postfix

Two remarks:

  • I changed the droplet name of the system into my domain name, otherwise postfix will send mail from the original droplet name, which in most cases will be a non-existent domain. So the mydestination = line in /etc/postfix/main.cf will look like

mydestination = $mydomain, localhost.$mydomain, $mydomain

  • I found out that

sudo less /var/log/mail.log

gave me valuable information for troubleshooting.

This comment has been deleted

    I cant test postfix my nail log shows

    ubuntu postfix/cleanup[11972]: E026142C90: message-id=<20160510195553.E026142C90@ubuntu-xenial.Home>
    ubuntu postfix/qmgr[11964]: E026142C90: from=<ubuntu@ubuntu-xenial>, size=393, nrcpt=1 (queue active)
    ubuntu postfix/smtp[11966]: connect to mx00.gmx.net[212.227.15.10]:25: Connection timed out
    ubuntu postfix/smtp[11967]: connect to mail-tester.com[94.23.206.89]:25: Connection timed out
    ubuntu postfix/smtp[11967]: EECFF42C8D: to=<web-ScX3Ah@mail-tester.com>, relay=none, delay=994, delays=964/0.24/30/0, dsn=4.4.1, status=deferred (connect to mail-tester.com[94.23.206.89]:25: Connection timed out)
    ubuntu postfix/smtp[11973]: connect to mail.mailinator.com[23.239.11.30]:25: Connection timed out
    ubuntu postfix/smtp[11966]: connect to mx01.gmx.net[212.227.17.4]:25: Connection timed out
    ubuntu postfix/smtp[11966]: B8EF642C91: to=<elh@gmx.us>, relay=none, delay=879, delays=819/0.12/60/0, dsn=4.4.1, status=deferred (connect to mx01.gmx.net[212.227.17.4]:25: Connection timed out)
    ubuntu postfix/smtp[11973]: connect to mail2.mailinator.com[45.79.147.26]:25: Connection timed out
    ubuntu postfix/smtp[11973]: E026142C90: to=<goff@mailinator.com>, relay=none, delay=61, delays=0.01/0.12/61/0, dsn=4.4.1, status=deferred (connect to mail2.mailinator.com[45.79.147.26]:25: Connection timed out)
    

    I cant test postfix my mail log shows this error : Connection timed out

    It could be that your fw blocking smtp port - in this case it’s 25.

    is there a vay to fix this problem i have the same problem

    This comment has been deleted

      Exits with non-zero status.

      Followed this tutorial to the tee but no matter what postfix always attempts to send the mail out as user@hostname (i.e. someone@machine rather than someone@domain.com). As a result, all mail is bounced with “Sender address rejected: need fully-qualified address”.

      /etc/mailname has the correct domain. Droplet was renamed from just a hostname to a FQDN

      Still did not solve the problem, even after purging and reinstalling mailutils and postfix.

      Any ideas where I may have gone wrong or what I can do to solve this?

      Have you configured the smtp_generic_maps directive in the /etc/postfix/main.cf and set it to use the filepath correctly?

      I have a problem when you have a server domain.com and a mail.domain.com and you try to install a send only postfix installation on domain.com.

      When u set up, even when i set up as system.domain.com for postfix destination, and I try to send a email to somethingoruser@domain.com (which has a MX record pointing to mail.domain.com), it will say it doesn’t have a user.

      No idea how to fix this.

      I found that even on Ubuntu 16.04 postfix was not installed with mailutils and I had to install that separately.

      I also had some trouble with sendmail being on port25 even though I thought I had stopped it, uninstalled it and reinstalled postfix.

      fatal: bind 0.0.0.0 port 25: Address already in use
      

      doing a sudo reboot on the server helped solve that. now I need to resolve the “from” address as it’s saying it’s from the droplet name and not from my domain. baby steps.

      In the second to last paragraph you say:

      If your use case is to receive notifications from your server at a single address, emails being marked as spam is a major issue because you can whitelist them. However, if your use case is to send emails to potential site users (such as confirmation emails for a message board sign-up), you should definitely set up SPF records and DKIM so your server’s emails are more likely to be seen as legitimate.

      But I think you meant

      If your use case is to receive notifications from your server at a single address, emails being marked as spam isn’t a major issue because you can whitelist them. However, if your use case is to send emails to potential site users (such as confirmation emails for a message board sign-up), you should definitely set up SPF records and DKIM so your server’s emails are more likely to be seen as legitimate.

      Can anybody guide me about the postfix configuration on Ubuntu 16.04 (Apache2)…? I have 2 domains in 1 DO droplet. Domain1: instamust.com & domain2: sociomust.com. Domain1 points to Gsuite mail server (through MX) and domain2 points to Zoho (through their MX). I have set these values correctly in respective DNS section. But still now can’t able to send/receive emails in domain based email a/c (for both domains) from both of my website’s contact form. Any help will be highly appreciated. Thanks

      But i am getting emails to my Yahoo/Gmail address when set as Cc in those Contact Form. But in Spam folder- Very worried!

      Error: relay=local, delay=0.09, delays=0.04/0.01/0/0.04, dsn=5.1.1, status=bounced (unknown user: “webmaster”

      I followed this tutorial to the letter on Ubuntu 16 but emails are being sent from user@www.domain.com instead of what should be user@domain.com

      what to do ?

      Add this to /etc/postfix/mail.cf

      masquerade_domains = domain.com
      

      That will strip any of the domain part before domain.com.

      Then run sudo systemctl reload postfix.service

      There’s one real problem with this walk-through, otherwise I’d be using this configuration for server notification and monitoring emails:

      Every single email is sent unencrypted, which is part of why many email services kick the emails as spam.

      Off the top of my head, I’m not even certain they can be encrypted using this configuration. I’m currently trying out different possible configurations on a VM. I’ll let everyone know how it goes.

      In addition to the instructions above, create your own self-signed certs, use LetsEncrypt, or use purchased certificates/keys (make sure you use wildcard or certificates specific to your hostname/FQDN), and edit main.cf to include:

      # TLS parameters
      smtpd_tls_cert_file=/etc/ssl/certs/fullchain.pem (change to suit your system)
      smtpd_tls_key_file=/etc/ssl/private/privkey.pem (change to suit your system)
      smtp_use_tls=yes
      smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache
      smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache
      
      smtpd_tls_CAfile=(if your cert and CAfile aren't rolled into a single file)
      

      It cleared the warnings from the emails for me, and shows TLS was used.

      Edit: Corrected to show smtp_use_tls=yes, not smtpd_use_tls=yes

      Perfect, thanks for this.

      I am using Postfix with more domains on one droplet and I added the certificate of the main domain. Works without any problem for the rest of the domains too.

      Brilliant, works like a charm, thanks Kevinruffus!

      I see this for mydestination: $myhostname, severname, localhost.localdomain, , localhost

      What do I do?

      I’m having some issues following this tutorial. I’ve followed the tutorial successfully through Step 3. But Step 4 doesn’t seem to work. I’m new to Postfix and not an admin so completely possible I am doing this completely wrong.

      This works for me. I get an email from doing the following. echo “This is the body of the email” | mail -s “This is the subject line” myemail@gmail.com

      This doesn’t work: echo “This is the body of the email” | mail -s “This is the subject line” root

      Any clues?

      This is a month late, but why are you trying to send mail to ‘root’?

      I followed this tutorial completely, but still my emails are not going to my email address.

      Although emails are being saved to local Maildir directory.

      Can you please help me sending emails to any email address from my server. I am using php to send emails.

      If there is any other tutorial to follow to do what I want?

      I have a LEMP 16.04 installed with virtual hosts. There are several wordpress websites on this droplet.

      Will this setup work for each seperate wordpress installation to send emails successfully? If so, which domain should I choose as System mail name? Does it matter which one I use?

      On my installation of Ubuntu 16.04 (not on your servers), the installation of mailutils didn’t produce a postfix configuration screen.

      I had the same, fixed it by removing postfix and mailutils first:

      sudo apt-get purge --auto-remove postfix sudo apt-get purge --auto-remove mailutils

      To run the postfix configuration program, run the command:

      dpkg-reconfigure postfix
      

      Excellent guide, thank you.

      Minor note, I think there was an error in this sentence

      If your use case is to receive notifications from your server at a single address, emails being marked as spam is a major issue because you can whitelist them.

      I’m assuming you meant “not a major issue”.

      Thanks for the great article.

      I followed this tutorial to the letter on Ubuntu 16 but emails are being sent from user@www.domain.com instead of what should be user@domain.com

      what to do ?

      From the comments it seems several people are having problems routing mail sent to their domain to an external mail service rather than locally. Perhaps the tutorial could be updated to show how to do this?

      I think the problem is Postfix tries to use the local_transport delivery method, and delivers the mail to the local mail directory instead of resolving the domain to the remote email service.

      To fix this, I changed mydestination in /etc/postfix/main.cf to:

      mydestination = localhost.$mydomain, localhost
      

      Hello ! I am searching to configure postfix on a machine hosting gitlab for mail notification, forwarding them on an external smtp server (xx.mail.ovh.net, but our mail are in the format xxxxx@oursociety.fr ) . At first I set the standard postfix configuration null client. But it set the external server as a relay host. It does not work with the external smtp server, as they do not allow it. They say we can send directly with postfix, without anymore details. Your solution seems to be the right one. But It is not clear how the mail is forwarded to your external SMTP server ? Don’t you have to set it somewhere ?

      My machine is not part of a domain, we have an entry in our DNS to point to it “gitlabmachine”. The hostname is set to the same entry name : gitlabmachine.

      So, how do I set postfix to allow gitlab (executed under identity git) to send mail to the external server ?

      You say “A valid domain name, like example.com, pointing to your server.” => which one? gitlabmachine or xx.mail.ovh.net ? I set it to “oursociety.fr” System mail name : oursociety.fr mydestination = oursociety.fr

      aliases : root: intranet@oursociety.fr admin: intranet@oursociety.fr

      But on the test the result is :

      Jan 10 18:36:07 intranet postfix/pickup[4396]: F1683EA0E0: uid=1001 from=<admin>
      Jan 10 18:36:07 intranet postfix/cleanup[5678]: F1683EA0E0: message-id=<20170110173607.F1683EA0E0@gitlabmachine>
      Jan 10 18:36:08 intranet postfix/qmgr[4397]: F1683EA0E0: from=<admin@oursociety.fr>, size=300, nrcpt=1 (queue active)
      Jan 10 18:36:08 intranet postfix/local[5680]: F1683EA0E0: to=<selso.liberado@oursociety.fr>, relay=local, delay=0.11, delays=0.07/0/0/0.04, dsn=5.1.1, status=bounced (unknown user: "selso.liberado")
      Jan 10 18:36:08 intranet postfix/cleanup[5678]: 11F77EA105: message-id=<20170110173608.11F77EA105@gitlabmachine>
      Jan 10 18:36:08 intranet postfix/bounce[5681]: F1683EA0E0: sender non-delivery notification: 11F77EA105
      Jan 10 18:36:08 intranet postfix/qmgr[4397]: 11F77EA105: from=<>, size=1989, nrcpt=1 (queue active)
      Jan 10 18:36:08 intranet postfix/qmgr[4397]: F1683EA0E0: removed
      Jan 10 18:36:08 intranet postfix/local[5680]: 11F77EA105: to=<intranet@oursociety.fr>, orig_to=<admin@oursociety.fr>, relay=local, delay=0.08, delays=0.04/0/0/0.04, dsn=5.1.1, status=bounced (unknown user: "intranet")
      Jan 10 18:36:08 intranet postfix/qmgr[4397]: 11F77EA105: removed
      

      Hi guys,

      Just want to ask if there is a way to encrypt the email? What do I need to configure or what to install? Thanks.

      For send-only MTA, Is there any advantages to using postfix over say nullmailer or ssmtp with Google Apps? Any input will be much appreciated.

      First, thank you very much for this wonderful tutorial.

      I have a question. Let me try to explain my question through a example: NGINX Server Blocks in available three different live websites:

      1. Test-one.com
      2. Test-two.com
      3. Test-three.com

      Droplet name is also different: Test-Dad

      How should I install and configure Postfix as a Send-Only SMTP Server?

      Thank you!

      i followed this but there is only 1 problem. it doesnt forward the emails to my personal email “XXXX@outlook.com” any idea?

      Of course I copied the only mispelled command: mailtuils should be mailutils.

      Super helpful!

      Try DigitalOcean for free

      Click below to sign up and get $200 of credit to try our products over 60 days!

      Sign up

      Join the Tech Talk
      Success! Thank you! Please check your email for further details.

      Please complete your information!

      Become a contributor for community

      Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.

      DigitalOcean Documentation

      Full documentation for every DigitalOcean product.

      Resources for startups and SMBs

      The Wave has everything you need to know about building a business, from raising funding to marketing your product.

      Get our newsletter

      Stay up to date by signing up for DigitalOcean’s Infrastructure as a Newsletter.

      New accounts only. By submitting your email you agree to our Privacy Policy

      The developer cloud

      Scale up as you grow — whether you're running one virtual machine or ten thousand.

      Get started for free

      Sign up and get $200 in credit for your first 60 days with DigitalOcean.*

      *This promotional offer applies to new accounts only.