Install and Configure SMTP Server on Windows Server 2016

The steps to setup and configure an SMTP Server or mail relay on Windows Server 2016 are almost exactly the same as those for Windows Server 2012 except for a few differences. Confusion has arisen due to slight GUI changes in Server 2016, which has led me to create this post to help anyone that requires explicit step-by-step instructions.

Note: The exact steps for installing SMTP Server on Windows Server 2012 can be found in this previous post of mine.

Installing the SMTP feature

1. Click on the Windows button and click on the Server Manager icon in the menu to load the Server Manager Dashboard:


Alternatively, open it via Powershell by entering servermanager.exe at the prompt to load the Server Manager Dashboard:

PS C:\> servermanager.exe

2. When the Server Manager Dashboard loads, click on Add roles and features in the center pane as highlighted below:


The Add Roles and Features Wizard will load, click Next to go past the initial Before You Begin Page:


3. In the Select installation type section, select Role-based or feature-based installation and click Next:


4. In the Select destination server section, select your server, in my example below, my server is called vs11app003, then click Next to proceed:


5. In the Select Server Roles section do not select anything and click Next to proceed:


6. In the Select features check SMTP Server:


Doing so will initiate a prompt to install the required roles services and features. Ensure you check the Include management tools (if applicable) box per the below and click Add Features to proceed:


7. Back at the Select features section, with SMTP Server selected click Next to proceed:


8. In the Web Server Role (IIS) section click Next to proceed:


9. Check Web Server then click Next to proceed:


10. The Confirm installation selections section will show all the role and feature configuration options you previously selected:


Checking Restart the destination server automatically if required is not necessary, if you do you will see the following warning:


Click Yes and the installation will begin:


11. Once the installation completes click Close:


The installation should complete shortly. You nay need to reboot your server to fully complete the installation.

Configuring the SMTP Server

The next step is to configure SMTP. To do so we will need to open Internet Information Services (IIS) Manager 6.

12. Click on the Windows button per step 1 to load the Server Manager Dashboard. Then click Tools and then click on Internet Information Services (IIS) 6.0 Manager to load IIS Manager 6:


13. In IIS 6 Manager, expand the server name, in my example below it is VS11APP003, then right-click on [SMTP Virtual Server #1] and select Properties:


14. In the General tab, unless you want the SMTP Server to use a specific IP address,  leave the settings as they are so that the IP address is set to (All Unassigned):


15. To proceed, click on the Access tab:


16. Click on the Authentication button and ensure Anonymous access is checked and then click OK:


17. Once back in the Access tab, click on the Connection button. Select Only the list below and then click Add. Enter as the IP address and then click OK:


The Connection setting controls which computers can connect to the SMTP server and send mail. By granting only localhost ( access, limits only the server itself the ability to connect to the SMTP server. This is a requirement for security. Click OK to return to the Access tab and then click on the Relay button. Enter as the IP address and then click OK:


The Relay section determines which computers can relay mail through this SMTP server. By only allowing the localhost IP address ( relay permissions it means that only the server itself can relay mail. Conversely, it prevents the SMTP server from being an open relay and being used to send unsolicited spam email by other computers on the internet, which could lead to the SMTP server being blacklisted.

18. Next, go to the Messages tab. Here you can enter an email address where copies of non-delivery reports are sent to. You can also configure the location of the Badmail director, however, the default setting should suffice:


19. Next, go to the Delivery tab:


20. Click on the Outbound Security button and ensure Anonymous access is selected. As the only server that can connect and relay mail through the SMTP server is localhost this security settings is fine:


21. Click OK to return to the Delivery tab and then click on Outbound Connections. Leave the defaults as they are:


22. Click OK to return to the Delivery tab and then click on the Advanced button:


Here you will need to enter the fully-qualified domain name of the SMTP server. This will be the host name or A record that has been created in your DNS zone file. This is straight-forward to do but you will have to confirm how you do this with the party that manages DNS for your domain. I have entered as this is fully-qualified. If you click on the Check DNS button you can confirm whether your chosen name resolves successfully. In my case it does as I see the following:


23. Click OK and then OK again to exit the SMTP Virtual Server #1 Properties. You can also perform this test by running nslookup to confirm the existence of the host name as well as confirming the IP address it resolves to – which should the IP address of your server:


Please note that DNS is crucial to successful email delivery. If your SMTP server cannot resolve the domains it is trying to send messages to then it will fail. Ensure that the DNS servers you have configured are able to resolve DNS queries successfully. From the above screenshot you can see that the DNS server I have configured,, was able to successfully resolve my SMTP server’s hostname,

The reason I am highlighting this is because if your SMTP Server sits within a corporate network it will likely use an internal DNS server. Often these are only configured to resolve internal namespaces therefore resolving external hostnames may fail. Also, firewall rules may block your SMTP Server from querying any DNS servers so please check and ensure DNS queries are resolved successfully and if not make sure it get fixed before going onto the testing phase below.

Another very important point about DNS is that you must ensure that you have a PTR record for reverse DNS lookups configured. The PTR record allows your SMTP Server’s public IP address to be resolved back to your hostname. Some of the major email providers perform revers DNS lookups of  mail servers connecting to them as a security measure to check their credibility or reputation. Your web host should have a control panel that allows you to configure reverse DNS if you have a dedicated public IP address. Not having a PTR record will not guarantee email delivery failure but it will very likely delay email delivery and at worst may result in your messages being blocked and your host being blacklisted. I highly recommend you you configure a PTR record for your server.

Follow the instructions in this post which shows you how to verify correct DNS configuration using the SMTPDIAG tool.

24. The last configuration step will be to set the SMTP Service to Automatic so that it automatically starts when the server boots up. Open up the Powershell console and run the command below to enable this setting:

PS C:\> set-service smtpsvc -StartupType Automatic

Then run the command below to confirm that the service is actually running:

PS C:\> get-service smtpsvc

Status   Name               DisplayName
------   ----               -----------
Running  smtpsvc            Simple Mail Transfer Protocol (SMTP)

If the SMTP Service is not running the command will return a status of Stopped. If that is the case then run the command below to start it:

PS C:\> start-service smtpsvc

We are now ready to test the configuration.

 Testing the SMTP Server

The next step is to verify that the SMTP server is able to send email successfully. To do this follow the steps below:

25. Open a PowerShell console and simply run the command below, ensuring that you complete the sending and receiving email addresses plus the subject and body text:

PS C:\> Send-MailMessage -SMTPServer localhost -To -From -Subject "This is a test email" -Body "Hi Japinator, this is a test email sent via PowerShell"

The above command sent an email to my Gmail account, a screenshot of the email generated is below:


You can save the above command in a file with a .ps1 (PowerShell) file extension and run it whenever you need to test sending/routing of mail.

That’s all there is to it! Now you have a fully functioning STMP server that can successfully send emails. Many of the companies that I have worked with use this method to send emails generated by their web applications.

If emails are not being successfully delivered you may notice that messages are building up in specific SMTP folders. Visit this post to understand the purpose of each SMTP folder and how to approach issues when messages are queuing up in those folders.

How to test outbound mail flow with a file in the Pickup folder
IIS SMTP Folder Structure and how SMTP service works

LVM – Setup and configure Filesystems in RHEL 6/Centos 6 – Part 4

Welcome to Part 4 of this series of 4 articles detailing how to setup and configure multiple filesystems running on LVM partitions. Each article will cover a specific topic, per the below:

Part 1 – Setup and configure Physical Volumes
Part 2 – Setup and configure Volume Groups
Part 3 – Setup and configure Logical Volumes
Part 4 – Setup and configure Filesystems

In Part 4 we are going to we will:

  • Format the logical volumes with the ext4 filesystem.
  • Mount the logical volumes create in Part 3 as filesystems.
  • Add these filesystems into /etc/fstab to ensure they are mounted during the boot process.

To format the music logical volume with the ext4 filesystem run:

mkfs.ext4 /dev/data/music

The resulting output is:

[root@lnx-svr-01 ~]# mkfs.ext4 /dev/data/music
mke2fs 1.41.12 (17-May-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
655360 inodes, 2621440 blocks
131072 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=2684354560
80 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632

Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 32 mounts or
180 days, whichever comes first.  Use tune2fs -c or -i to override.
[root@lnx-svr-01 ~]#

Perform the same steps for the video and pictures logical volumes.

Now that the filesystems have been created, we need to mount them. First, We will create the folders upon which the filesystems will be mounted, their relationships to the corresponding folders (mount point) is:

music -------> /var/music
video -------> /var/video
pictures ----> /var/pictures

Run mkdir to create the folder above:

mkdir /var/music /var/video /var/pictures

Mount the newly created filesystems by running the mount command per the below:

mount /dev/data/music /var/music
mount /dev/data/video /var/video
mount /dev/data/pictures /var/pictures

Then run df -h to see the currently mounted filesystems:

[root@lnx-svr-01 ~]# df -h
Filesystem            Size  Used Avail Use% Mounted on
                       18G  903M   16G   6% /
tmpfs                 939M     0  939M   0% /dev/shm
/dev/sda1             477M   25M  427M   6% /boot
                      9.8G   23M  9.2G   1% /var/music
                      4.8G   10M  4.6G   1% /var/video
                      4.8G   10M  4.6G   1% /var/pictures
[root@lnx-svr-01 ~]#

We can see from the above that our filesystems are listed and mounted. However, we mounted the filesystems manually, we need them to mount automatically when the system boots up, so in order to enable this we need to add them to /etc/fstab.

So to proceed, run vi to edit /etc/fstab:

vi /etc/fstab

This is what is looks like at present:

# /etc/fstab
# Created by anaconda on Sat May 30 19:17:27 2015
# Accessible filesystems, by reference, are maintained under '/dev/disk'
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info
/dev/mapper/VolGroup-lv_root /                       ext4    defaults        1 1
UUID=db505cff-1d69-4f12-b22a-9d4335dc2275 /boot                   ext4    defaults        1 2
/dev/mapper/VolGroup-lv_swap swap                    swap    defaults        0 0
tmpfs                   /dev/shm                tmpfs   defaults        0 0
devpts                  /dev/pts                devpts  gid=5,mode=620  0 0
sysfs                   /sys                    sysfs   defaults        0 0
proc                    /proc                   proc    defaults        0 0

Add the following lines into the file:

/dev/data/music         /var/music              ext4    rw,noatime      0 0
/dev/data/video         /var/video              ext4    rw,noatime      0 0
/dev/data/pictures      /var/pictures           ext4    rw,noatime      0 0

So it looks like this:

# /etc/fstab
# Created by anaconda on Sat May 30 19:17:27 2015
# Accessible filesystems, by reference, are maintained under '/dev/disk'
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info
/dev/mapper/VolGroup-lv_root /                       ext4    defaults        1 1
UUID=db505cff-1d69-4f12-b22a-9d4335dc2275 /boot                   ext4    defaults        1 2
/dev/mapper/VolGroup-lv_swap swap                    swap    defaults        0 0
tmpfs                   /dev/shm                tmpfs   defaults        0 0
devpts                  /dev/pts                devpts  gid=5,mode=620  0 0
sysfs                   /sys                    sysfs   defaults        0 0
proc                    /proc                   proc    defaults        0 0
/dev/data/music         /var/music              ext4    rw,noatime      0 0
/dev/data/video         /var/video              ext4    rw,noatime      0 0
/dev/data/pictures      /var/pictures           ext4    rw,noatime      0 0

Save and exit the file, then reboot the system by running the shutdown command per the below:

[root@lnx-svr-01 ~]# shutdown -r now

Broadcast message from root@lnx-svr-01.vsysad.local
        (/dev/pts/0) at 14:35 ...

The system is going down for reboot NOW!
[root@lnx-svr-01 ~]#

Once the server comes back up, login and run df -h to confirm that all of our filesystems are mounted:

[root@lnx-svr-01 ~]# df -h
Filesystem            Size  Used Avail Use% Mounted on
                       18G  903M   16G   6% /
tmpfs                 939M     0  939M   0% /dev/shm
/dev/sda1             477M   25M  427M   6% /boot
                      9.8G   23M  9.2G   1% /var/music
                      4.8G   10M  4.6G   1% /var/video
                      4.8G   10M  4.6G   1% /var/pictures
[root@lnx-svr-01 ~]#

There we have it, three filesystems running on LVM partitions which are ready for production use. I hope this was easy to follow and understand. Please also take time to read the references at the bottom, they are excellent resources and were bookmarked by myself for reference whenever I needed to check anything LVM related.

How to Create LVM Partition in RHEL 6 / CentoOS
Linux Basics – LVM (Logical Volume Manager) Tutorial
How to Install LVM on Linux and Disk Operations
A Beginner’s Guide To LVM
How To Create LVM Using vgcreate, lvcreate, and lvextend lvm2 Commands