Forum Discussion
Solved
[Server Buld 20303.1] IIS 6 Manager crashes trying to edit SMTP Virtual Server Properties
I have installed 20303.1 and added the SMTP Service and add the management tools. Install-WindowsFeature SMTP-Server -IncludeManagementTools After the installation, I bring up t...
- We found that doing the following worked, and can now edit the settings in the II6 Manager without errors (and without crashing when applying settings) every time:
Stop SMTPSVC service [Display Name: Simple Mail Transfer Protocol (SMTP)]
Stop IISADMIN service [Display name: IIS Admin Service]
Edit "C:\Windows\System32\inetsrv\MetaBase.xml"
Find: <IIsSmtpServer Location ="/LM/SmtpSvc/1"
Add (Settings are alphabetical): RelayIpList=""
Save file
Start IISAdmin Service
Start SMTPSVC service
You can now open the Internet Information Services (IIS) 6.0 Manager (InetMgr6.exe) and work like normal. The setting above relates to the Access Tab > Relay Restrictions section, but doesn't set anything in it (i.e. "all except the below list" with a blank list).
After setting this value you can change it to what you need it to be. (i.e. the value doesn't need to be 'null' for the fix to work, just so long as the variable is present in the file).
The above has been tested on a few new installs of Windows Server 2022, and has worked for us every time. If you have done an upgrade there are some other things to consider (seems like the SMTP service is not installed after upgrade so will require a backup of the settings that can be applied post reinstalling the service. But that is discussed in other topics).
PS: Remember to set the SMTPSVC service to start "automatically". By default its set to "manual".
Source: https://serverfault.com/questions/1088555/server-2022-smtp-server-issue
KevinShaughnessy
Microsoft
MicrosoftHello, the SMTP stack and management tools have been deprecated since Windows Server 2012 and will soon be removed from Windows Server 2022. Please refer to this article: https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/hh831568(v=ws.11)
SMTP and the associated management tools are deprecated. Though the functionality is still available in Windows Server 2012, you should begin using System.Net.Smtp.
Kevin Shaughnessy
Sr. Program Manager
Microsoft Exchange Transport
SMTP and the associated management tools are deprecated. Though the functionality is still available in Windows Server 2012, you should begin using System.Net.Smtp.
Kevin Shaughnessy
Sr. Program Manager
Microsoft Exchange Transport
- Hello Kevin, could you please check with the server docs team, they should include this warning on this page please. Hi @406979
https://docs.microsoft.com/en-us/windows-server/get-started/removed-deprecated-features-windows-server-2022
The 2012/2012R2 could be referenced but they are not much visible in the ToC,- Elden_Christensen
Clarification, SMTP was 'Deprecated' in Windows Server 2012:
https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/hh831568(v=ws.11)#smtp
SMTP is included all the way up through (including) Windows Server 2022.However SMTP has been 'Removed' for the next release of Windows Server, and you will see this change has been made that SMTP is no longer available in the current Windows Server Insider preview builds.
Thanks!
Elden- Thx a lot for your feedback
SharePoint Server 2019 and SharePoint Server Subscription Edition are supported for Windows Server 2022 and SharePoint required SMTP Service to receive e-mails.
If the SMTP service is removed then the information for SharePoint 2019 and SE is not correct.
- This is a terrible move! A lot of us still utilize this feature heavily, if anything, it should be updated. Everything can't be pointed to 365, this will force customers to evaluate 3rd party smtp software now.
Maverickx AGREE! That SMTP server is a useful utility that we use heavily. Rolling back to 2019 ASAP.
Microsoft: At least consider open sourcing this. We use it as our core SMTP engine and we do not want or need to get a new service or app. 365 and Azure are not alternatives for self-hosted SMTP.
phollows
After trying all things listed here, I found that stopping the Relay service in IIS and running the IIS 6 console as the administrator, allowed me to get in and configure it in Server 2022 Datacenter.EDIT: However it still doesn't work after configuring it, the SMTP Service stops when it receives a message.
So what is a good light weight relay I can go get ?
Thanks Chris
- First, that article gives me a 404. Can you check it?
Also, how do we relay mail with System.SMTP.Mail? 🙂
My use case is that I want to relay local mail from FSRM which uses unauthenticated SMTP. With Server 2019, I set up a relay on localhost, then relay to my account at SendMail.Org to send on to the real account. It works a treat. Can you suggest an alternative way to achieve these FSRM email reports?- KevinShaughnessySorry about that. Try this: https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/hh831568(v=ws.11). You'd have to write an application using System.SMTP.Mail or update an existing app to use it. MailKit is another popular SMTP set of services - still requires coding though. Other alternatives include turboSMTP (https://www.serversmtp.com/smtp-for-windows/), a popular SMTP service for Windows that doesn't require coding.
- KevinShaughnessyHmm. That link was good but posting it somehow made it invalid, apparently by stripping the last parenthesis off it. Try copy/pasting this into your address bar then add the "https://" prefix to it: docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/hh831568(v=ws.11)
