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:

20170526164721

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:

20170526012744

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

20170526012839

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

20170526013937

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

20170526014003

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

20170526014032

6. In the Select features check SMTP Server:

20170526014121

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:

20170526014203

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

20170526014233

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

20170526014309

9. Check Web Server then click Next to proceed:

20170526014513

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

20170526014602

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

20170526014630

Click Yes and the installation will begin:

20170526014709

11. Once the installation completes click Close:

20170526090039

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:

20170528005334

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:

20170526090654

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):

20170526090949

15. To proceed, click on the Access tab:

20170526092536

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

20170526092606

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

20170526092934

The Connection setting controls which computers can connect to the SMTP server and send mail. By granting only localhost (127.0.0.1) 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 127.0.0.1 as the IP address and then click OK:

20170526092759

The Relay section determines which computers can relay mail through this SMTP server. By only allowing the localhost IP address (127.0.0.1) 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:

20170526093025

19. Next, go to the Delivery tab:

20170528010430

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:

20170526093758

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

20170526093843

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

20170526093957

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 mail.vsysad.com 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:

20170526094249

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:

20170526094855

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, google-public-dns-a.google.com, was able to successfully resolve my SMTP server’s hostname, mail.vsysad.com.

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 xxxxx@gmail.com -From blog@vsysad.com -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:

20131031223718

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.

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

Install .NET Framework 3.5 feature on Windows Server 2012 R2

20170522110941The .NET Framework 3.5 feature is not installed by default on Windows Server 2012 R2 as this version of Windows ships with .NET Framework 4.5 already installed. If you want to install .NET Framework 3.5 then it needs to be manually installed. SQL Server 2012 requires the .NET Framework 3.5 feature to be installed, if it isn’t you will see this error when attemtping to install it:

20170522095650

Installing the .NET Framework 3.5 feature

Please note that you require the Windows Server 2012 media in order to install the .NET Framework 3.5 feature. It must be mounted to a Windows drive, in my case I mounted it to the D:\ drive:

20170523163134

 

 

1. Click on the Server Manager icon in the bottom left-hand corner to load the Server Manager Dashboard:

20141101005404

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

20170520095702

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

20170520095832

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

20170520095906

4. In the Server Selection section, select your server, in my example below, my server is called vs11app001, then click Next to proceed:

20170520100125

5. In the Server Roles section, do not select anything, click Next:

20170520100150

6. In the Features section, select .NET Framework 3.5 Features then click Install to proceed:

20170520100346

7. In the Confirm installation selections section, click on Specify an alternate source path:

20170520100622

8. Then in the Specify an alternate source path section, change the Path to reflect the location of your Windows 2012 media:

20170520100938

Ensure you enter the full path to the SxS folder, in my case the media was on the D:\ drive, so the full path was D:\Sources\SxS.

9. Click OK to go back to the Specify an alternate source path section and then click on Install to proceed with  the installation:

20170520101051

10. You can click close at this stage and the installation will complete soon after.

Please note that you can install .NET Framework 3.5 via the command line using the Deployment Image Servicing and Management (DISM) tool and running:

Dism /online /enable-feature /featurename:NetFX3 /All /Source:D:\Sources\SxS /LimitAccess

Irrespective of the installation method you choose, a reboot is not necessary but I would recommend it to ensure the changes are committed to the system and that it starts up cleanly.

11. Verify that .NET Framework 3.5 has been installed successfully by navigating to C:\Windows\Microsoft.NET\Framework64. You will see folders representing the installed .NET Framework versions:

20170520102304

As you can see versions 2.0, 3.0 and 3.5 were installed by our actions above, version 4.0 was already present.

As an aside, you can run the PowerShell code below, which I found here, to  confirm the installed .NET Framework versions also:

Get-ChildItem 'HKLM:\SOFTWARE\Microsoft\NET Framework Setup\NDP' -recurse |
Get-ItemProperty -name Version,Release -EA 0 |
Where { $_.PSChildName -match '^(?!S)\p{L}'} |
Select PSChildName, Version, Release

Running this script yields the following results:

20170522094711

You can now proceed with installing SQL Server 2012 or any other activity that required you to install .NET Framework 3.5.

References:
PowerShell script to return versions of .NET Framework on a machine?
Installing .NET framework 3.5 on windows server 2012