How To Install and Configure Postfix on Ubuntu 18.04

Published on July 6, 2018
How To Install and Configure Postfix on Ubuntu 18.04
Not using Ubuntu 18.04?Choose a different version or distribution.
Ubuntu 18.04


Postfix is a popular open-source Mail Transfer Agent (MTA) that can be used to route and deliver email on a Linux system. It is estimated that around 25% of public mail servers on the internet run Postfix.

In this guide, we’ll teach you how to get up and running quickly with Postfix on an Ubuntu 18.04 server.


In order to follow this guide, you should have access to a non-root user with sudo privileges. You can follow our Ubuntu 18.04 initial server setup guide to create the necessary user.

In order to properly configure Postfix, you will need a Fully Qualified Domain Name pointed at your Ubuntu 18.04 server. You can find help on setting up your domain name with DigitalOcean by following this guide. If you plan on accepting mail, you will need to make sure you have an MX record pointing to your mail server as well.

For the purposes of this tutorial, we will assume that you are configuring a host that has the FQDN of mail.example.com.

Step 1 — Install Postfix

Postfix is included in Ubuntu’s default repositories, so installation is simple.

To begin, update your local apt package cache and then install the software. We will be passing in the DEBIAN_PRIORITY=low environmental variable into our installation command in order to answer some additional prompts:

  1. sudo apt update
  2. sudo DEBIAN_PRIORITY=low apt install postfix

Use the following information to fill in your prompts correctly for your environment:

  • General type of mail configuration?: For this, we will choose Internet Site since this matches our infrastructure needs.
  • System mail name: This is the base domain used to construct a valid email address when only the account portion of the address is given. For instance, the hostname of our server is mail.example.com, but we probably want to set the system mail name to example.com so that given the username user1, Postfix will use the address user1@example.com.
  • Root and postmaster mail recipient: This is the Linux account that will be forwarded mail addressed to root@ and postmaster@. Use your primary account for this. In our case, sammy.
  • Other destinations to accept mail for: This defines the mail destinations that this Postfix instance will accept. If you need to add any other domains that this server will be responsible for receiving, add those here, otherwise, the default should work fine.
  • Force synchronous updates on mail queue?: Since you are likely using a journaled filesystem, accept No here.
  • Local networks: This is a list of the networks that your mail server is configured to relay messages for. The default should work for most scenarios. If you choose to modify it, make sure to be very restrictive in regards to the network range.
  • Mailbox size limit: This can be used to limit the size of messages. Setting it to “0” disables any size restriction.
  • Local address extension character: This is the character that can be used to separate the regular portion of the address from an extension (used to create dynamic aliases).
  • Internet protocols to use: Choose whether to restrict the IP version that Postfix supports. We’ll pick “all” for our purposes.

To be explicit, these are the settings we’ll use for this guide:

  • General type of mail configuration?: Internet Site
  • System mail name: example.com (not mail.example.com)
  • Root and postmaster mail recipient: sammy
  • Other destinations to accept mail for: $myhostname, example.com, mail.example.com, localhost.example.com, localhost
  • Force synchronous updates on mail queue?: No
  • Local networks: [::ffff:]/104 [::1]/128
  • Mailbox size limit: 0
  • Local address extension character: +
  • Internet protocols to use: all

If you need to ever return to re-adjust these settings, you can do so by typing:

  1. sudo dpkg-reconfigure postfix

The prompts will be pre-populated with your previous responses.

When you are finished, we can now do a bit more configuration to set up our system how we’d like it.

Step 2 — Tweak the Postfix Configuration

Next, we can adjust some settings that the package did not prompt us for.

To begin, we can set the mailbox. We will use the Maildir format, which separates messages into individual files that are then moved between directories based on user action. The other option is the mbox format (which we won’t cover here) which stores all messages within a single file.

We will set the home_mailbox variable to Maildir/ which will create a directory structure under that name within the user’s home directory. The postconf command can be used to query or set configuration settings. Configure home_mailbox by typing:

  1. sudo postconf -e 'home_mailbox= Maildir/'

Next, we can set the location of the virtual_alias_maps table. This table maps arbitrary email accounts to Linux system accounts. We will create this table at /etc/postfix/virtual. Again, we can use the postconf command:

  1. sudo postconf -e 'virtual_alias_maps= hash:/etc/postfix/virtual'

Step 3 — Map Mail Addresses to Linux Accounts

Next, we can set up the virtual maps file. Open the file in your text editor:

  1. sudo nano /etc/postfix/virtual

The virtual alias map table uses a very simple format. On the left, you can list any addresses that you wish to accept email for. Afterwards, separated by whitespace, enter the Linux user you’d like that mail delivered to.

For example, if you would like to accept email at contact@example.com and admin@example.com and would like to have those emails delivered to the sammy Linux user, you could set up your file like this:

contact@example.com sammy
admin@example.com sammy

After you’ve mapped all of the addresses to the appropriate server accounts, save and close the file.

We can apply the mapping by typing:

  1. sudo postmap /etc/postfix/virtual

Restart the Postfix process to be sure that all of our changes have been applied:

  1. sudo systemctl restart postfix

Step 4 — Adjust the Firewall

If you are running the UFW firewall, as configured in the initial server setup guide, we’ll have to allow an exception for Postfix.

You can allow connections to the service by typing:

  1. sudo ufw allow Postfix

The Postfix server component is installed and ready. Next, we will set up a client that can handle the mail that Postfix will process.

Step 5 — Setting up the Environment to Match the Mail Location

Before we install a client, we should make sure our MAIL environmental variable is set correctly. The client will inspect this variable to figure out where to look for user’s mail.

In order for the variable to be set regardless of how you access your account (through ssh, su, su -, sudo, etc.) we need to set the variable in a few different locations. We’ll add it to /etc/bash.bashrc and a file within /etc/profile.d to make sure each user has this configured.

To add the variable to these files, type:

  1. echo 'export MAIL=~/Maildir' | sudo tee -a /etc/bash.bashrc | sudo tee -a /etc/profile.d/mail.sh

To read the variable into your current session, you can source the /etc/profile.d/mail.sh file:

  1. source /etc/profile.d/mail.sh

Step 6 — Install and Configure the Mail Client

In order to interact with the mail being delivered, we will install the s-nail package. This is a variant of the BSD xmail client, which is feature-rich, can handle the Maildir format correctly, and is mostly backwards compatible. The GNU version of mail has some limitations, such as always saving read mail to the mbox format regardless of the source format.

To install the s-nail package, type:

  1. sudo apt install s-nail

We should adjust a few settings. Open the /etc/s-nail.rc file in your editor:

  1. sudo nano /etc/s-nail.rc

Towards the bottom of the file, add the following options:

. . .
set emptystart
set folder=Maildir
set record=+sent

This will allow the client to open even with an empty inbox. It will also set the Maildir directory to the internal folder variable and then use this to create a sent mbox file within that, for storing sent mail.

Save and close the file when you are finished.

Step 7 — Initialize the Maildir and Test the Client

Now, we can test the client out.

Initializing the Directory Structure

The easiest way to create the Maildir structure within our home directory is to send ourselves an email. We can do this with the s-nail command. Because the sent file will only be available once the Maildir is created, we should disable writing to that for our initial email. We can do this by passing the -Snorecord option.

Send the email by piping a string to the s-nail command. Adjust the command to mark your Linux user as the recipient:

  1. echo 'init' | s-nail -s 'init' -Snorecord sammy

You may get the following response:

Can't canonicalize "/home/sammy/Maildir"

This is normal and may only appear when sending this first message. We can check to make sure the directory was created by looking for our ~/Maildir directory:

  1. ls -R ~/Maildir

You should see the directory structure has been created and that a new message file is in the ~/Maildir/new directory:

/home/sammy/Maildir/: cur new tmp /home/sammy/Maildir/cur: /home/sammy/Maildir/new: 1463177269.Vfd01I40e4dM691221.mail.example.com /home/sammy/Maildir/tmp:

It looks like our mail has been delivered.

Managing Mail with the Client

Use the client to check your mail:

  1. s-nail

You should see your new message waiting:

s-nail version v14.8.6. Type ? for help. "/home/sammy/Maildir": 1 message 1 new >N 1 sammy@example.com Wed Dec 31 19:00 14/369 init

Just hitting ENTER should display your message:

[-- Message 1 -- 14 lines, 369 bytes --]: From sammy@example.com Wed Dec 31 19:00:00 1969 Date: Fri, 13 May 2016 18:07:49 -0400 To: sammy@example.com Subject: init Message-Id: <20160513220749.A278F228D9@mail.example.com> From: sammy@example.com init

You can get back to your message list by typing h, and then ENTER:

  1. h
s-nail version v14.8.6. Type ? for help. "/home/sammy/Maildir": 1 message 1 new >R 1 sammy@example.com Wed Dec 31 19:00 14/369 init

Since this message isn’t very useful, we can delete it with d, and then ENTER:

  1. d

Quit to get back to the terminal by typing q and then ENTER:

  1. q

Sending Mail with the Client

You can test sending mail by typing a message in a text editor:

  1. nano ~/test_message

Inside, enter some text you’d like to email:


This is a test.  Please confirm receipt!

Using the cat command, we can pipe the message to the s-nail process. This will send the message as your Linux user by default. You can adjust the “From” field with the -r flag if you want to modify that value to something else:

  1. cat ~/test_message | s-nail -s 'Test email subject line' -r from_field_account user@email.com

The options above are:

  • -s: The subject line of the email
  • -r: An optional change to the “From:” field of the email. By default, the Linux user you are logged in as will be used to populate this field. The -r option allows you to override this.
  • user@email.com: The account to send the email to. Change this to be a valid account you have access to.

You can view your sent messages within your s-nail client. Start the interactive client again by typing:

  1. s-nail

Afterwards, view your sent messages by typing:

  1. file +sent

You can manage sent mail using the same commands you use for incoming mail.


You should now have Postfix configured on your Ubuntu 18.04 server. Managing email servers can be a tough task for beginning administrators, but with this configuration, you should have basic MTA email functionality to get you started.

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 authors

Still looking for an answer?

Ask a questionSearch for more help

Was this helpful?

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!

No dice for me. Followed along as instructed. Got to: echo 'init' | s-nail -s 'init' -Snorecord MYUSER and there was no output at all. Using ls -R ~/Maildir showed me that the dir wasn’t getting made. I made it myself using mkdir -p ~/Maildir/{cur,new,tmp}.

That got things sort of working, but the s-nail thing still isn’t successful sending mail to the inbox.

Just chiming in to say that yeah, this tutorial didn’t work. Maybe it should be edited to include some of the suggestions in the comment stream?

Spent an hour trying to figure out why this wasn’t delivering mail to ~/Maildir after following along. Turns out that a line in /etc/postfix/main.cf executes a command that takes precedence over the home_mailbox= Maildir/ setting… If you added a snippet about it above I’m sure it would save people some trouble.

To fix my issue I had to comment out mailbox_command = procmail -a "$EXTENSION" in /etc/postfix/main.cf. After restarting postfix with sudo /etc/init.d/postfix restart everything worked and ~/Maildir was created.

I Have followed the tutorial and everything worked. However, I want to use another mail exchange like outlook so i can get an interface to send and receive emails. The problem is i didn’t see a section where i can configure my password to login to an email exchange.

The link to ‘how to set up a host name in DigitalOcean’ is broken.

after manyhours of trying to get postfix working on ubuntu both here and linode I finally learned abou the effect of chroot implementation on postfix the postfix sorce distribution contains a set of scripts under examples/chroot-setup that creates a /etc/under the chroot filesystem at /var/spool/postfix and then copies /etc/resources there like my ssl certificates etc /passwd file the general complaint is that the ubuntu package maintainers forgot this step it is documented in the o’rilry book difinative guide to postfix basically the processes in master.cf that are chinrooted cannot see the rest of the server filesystem which is the purpose of chroot so some existing resources need to be copied there /var/spool/postfix/etc I ended up building my own script using the examplescripts as a guide then I added an rsync script to coppy my passwd file after i had a user not found that was added after the initial copy. hope I helped someone:(

Good day! I did everything according to the instructions from this link https://www.digitalocean.com/communi...buntu-18-04-ru. I’ll clarify, installed the postfix, then created two new users and added them to the mail group as root (the root was also added to the mail group). Next, I did everything according to the instructions (I tried it twice from scratch, once I followed the instruction on behalf of the root, the other from just the main account), when I start to do the Maildir initialization item, if I send a letter from the root or the main account to myself , then the cur, new and tmp folders are created, and if I do initialization from the created users, then these folders are not created, even Maildir is not created and letters do not come anywhere. I also tried to issue full rights to the folders of created users and added them to the list of admins (sudoers), nothing changes. If I write ls -R ~ / Maildir (when I am in the account of the created user), I get a message: “ls: cannot access ‘/home/mailNDO/Maildir’: No such file or directory”. Help, please, I’ve already tried a bunch of different instructions and the same thing every time. Even in the main.cf file, My destinations left only localhost, local.domain and the same thing. Things I have tried:

  1. I copied the Maildir folder from root to the new user folder, gave it all the rights. When I logged in as a new user, these folders were visible, but no mail was sent or received either.
  2. I tried to give all the rights to the postfix folder, but there is a dynamicmaps.cf file that prevents this from being done, then an error appears.
  3. I do not have SELinux installed, and I disabled AppArmor, but this did not affect anything.
  4. I even did a clean install of ubuntu, and did it all from scratch, but the error still remains. The same problem with mailutils.

Thanks for this. Followed to the letter and worked like a charm. Problem though, is I’m getting “Undelivered Mail Returned to Sender” from all the external addresses I’ve been sending test emails to.

The error in the response is: Access denied - Invalid HELO name

I’m guessing this has got to be a next level of configuration somewhere, but can you please direct me to a reference perhaps? hopefully a similar well-written guide. Thanks

I’ve done up to this stage: $echo ‘init’ | s-nail -s ‘init’ -Snorecord sammy

But I get the following: ls: cannot access ‘/home/sammy/Maildir’: No such file or directory

Please note that when I created a new user I literally used the same name “Sammy” (as in the tutorial)

I have done this at least 3 times and it works. I receive a lot of spam but I get messages. Then down the road, it stops working. Today I found this message in the mail directory on the server: host gmail-smtp-in.l.google.com[] said: 550-5.7.28 [xxx.xx.xxx.xx 1] Our system has detected an unusual rate of 550-5.7.28 unsolicited mail originating from your IP address. To protect our 550-5.7.28 users from spam, mail sent from your IP address has been blocked. 550-5.7.28 Please visit 550-5.7.28 https://support.google.com/mail/?p=UnsolicitedIPError...has anyone else experienced this?

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!

Featured on Community

Get our biweekly newsletter

Sign up for Infrastructure as a Newsletter.

Hollie's Hub for Good

Working on improving health and education, reducing inequality, and spurring economic growth? We'd like to help.

Become a contributor

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

Welcome to the developer cloud

DigitalOcean makes it simple to launch in the cloud and scale up as you grow — whether you're running one virtual machine or ten thousand.

Learn more
DigitalOcean Cloud Control Panel