[Server Buld 20303.1] IIS 6 Manager crashes trying to edit SMTP Virtual Server Properties

%3CLINGO-SUB%20id%3D%22lingo-sub-2215174%22%20slang%3D%22en-US%22%3E%5BServer%20Buld%2020303.1%5D%20IIS%206%20Manager%20crashes%20trying%20to%20edity%20SMTP%20Virtual%20Server%20Properties%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2215174%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20installed%2020303.1%20and%20addes%20the%20SMTP%20Service%20and%20add%20the%20management%20tools%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%20class%3D%22lia-code-sample%20language-powershell%22%3E%3CCODE%3Einstall-windowsfeature%20SMTP-Server%20-IncludeManagementTools%3C%2FCODE%3E%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAfter%20the%20installation%2C%20I%20bring%20up%20the%20IIS%206%20Management%20Console.%3C%2FP%3E%3CP%3EIf%20I%20right-click%20the%20%5BSMTP%20Virtual%20Server%5D%20node%20and%20select%20properties%2C%20I%20get%20an%20error%20like%20this%3A%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%222021-03-16_20-20-52.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F264568iCDF7D67953802BA7%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%222021-03-16_20-20-52.png%22%20alt%3D%222021-03-16_20-20-52.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3EClues%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2215174%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EManagement%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2215279%22%20slang%3D%22en-US%22%3ERe%3A%20%5BServer%20Buld%2020303.1%5D%20IIS%206%20Manager%20crashes%20trying%20to%20edit%20SMTP%20Virtual%20Server%20Properties%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2215279%22%20slang%3D%22en-US%22%3EHello%2C%20the%20SMTP%20stack%20and%20management%20tools%20have%20been%20deprecated%20since%20Windows%20Server%202012%20and%20will%20soon%20be%20removed%20from%20Windows%20Server%202022.%20Please%20refer%20to%20this%20article%3A%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fprevious-versions%2Fwindows%2Fit-pro%2Fwindows-server-2012-R2-and-2012%2Fhh831568(v%3Dws.11%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fprevious-versions%2Fwindows%2Fit-pro%2Fwindows-server-2012-R2-and-2012%2Fhh831568(v%3Dws.11%3C%2FA%3E)%3CBR%20%2F%3E%3CBR%20%2F%3ESMTP%20and%20the%20associated%20management%20tools%20are%20deprecated.%20Though%20the%20functionality%20is%20still%20available%20in%20Windows%20Server%202012%2C%20you%20should%20begin%20using%20System.Net.Smtp.%3CBR%20%2F%3E%3CBR%20%2F%3EKevin%20Shaughnessy%3CBR%20%2F%3ESr.%20Program%20Manager%3CBR%20%2F%3EMicrosoft%20Exchange%20Transport%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2217053%22%20slang%3D%22en-US%22%3ERe%3A%20%5BServer%20Buld%2020303.1%5D%20IIS%206%20Manager%20crashes%20trying%20to%20edit%20SMTP%20Virtual%20Server%20Properties%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2217053%22%20slang%3D%22en-US%22%3EFirst%2C%20that%20article%20gives%20me%20a%20404.%20Can%20you%20check%20it%3F%3CBR%20%2F%3E%3CBR%20%2F%3EAlso%2C%20how%20do%20we%20relay%20mail%20with%20System.SMTP.Mail%3F%20%3A)%3C%2Fimg%3E%3CBR%20%2F%3EMy%20use%20case%20is%20that%20I%20want%20to%20relay%20local%20mail%20from%20FSRM%20which%20uses%20unauthenticated%20SMTP.%20With%20Server%202019%2C%20I%20set%20up%20a%20relay%20on%20localhost%2C%20then%20relay%20to%20my%20account%20at%20SendMail.Org%20to%20send%20on%20to%20the%20real%20account.%20It%20works%20a%20treat.%20Can%20you%20suggest%20an%20alternative%20way%20to%20achieve%20these%20FSRM%20email%20reports%3F%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2217590%22%20slang%3D%22en-US%22%3ERe%3A%20%5BServer%20Buld%2020303.1%5D%20IIS%206%20Manager%20crashes%20trying%20to%20edit%20SMTP%20Virtual%20Server%20Properties%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2217590%22%20slang%3D%22en-US%22%3ESorry%20about%20that.%20Try%20this%3A%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fprevious-versions%2Fwindows%2Fit-pro%2Fwindows-server-2012-R2-and-2012%2Fhh831568(v%3Dws.11%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fprevious-versions%2Fwindows%2Fit-pro%2Fwindows-server-2012-R2-and-2012%2Fhh831568(v%3Dws.11%3C%2FA%3E).%20You'd%20have%20to%20write%20an%20application%20using%20System.SMTP.Mail%20or%20update%20an%20existing%20app%20to%20use%20it.%20MailKit%20is%20another%20popular%20SMTP%20set%20of%20services%20-%20still%20requires%20coding%20though.%20Other%20alternatives%20include%20turboSMTP%20(%3CA%20href%3D%22https%3A%2F%2Fwww.serversmtp.com%2Fsmtp-for-windows%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.serversmtp.com%2Fsmtp-for-windows%2F%3C%2FA%3E)%2C%20a%20popular%20SMTP%20service%20for%20Windows%20that%20doesn't%20require%20coding.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2217592%22%20slang%3D%22en-US%22%3ERe%3A%20%5BServer%20Buld%2020303.1%5D%20IIS%206%20Manager%20crashes%20trying%20to%20edit%20SMTP%20Virtual%20Server%20Properties%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2217592%22%20slang%3D%22en-US%22%3EHmm.%20That%20link%20was%20good%20but%20posting%20it%20somehow%20made%20it%20invalid%2C%20apparently%20by%20stripping%20the%20last%20parenthesis%20off%20it.%20Try%20copy%2Fpasting%20this%20into%20your%20address%20bar%20then%20add%20the%20%22https%3A%2F%2F%22%20prefix%20to%20it%3A%20docs.microsoft.com%2Fen-us%2Fprevious-versions%2Fwindows%2Fit-pro%2Fwindows-server-2012-R2-and-2012%2Fhh831568(v%3Dws.11)%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2696895%22%20slang%3D%22en-US%22%3ERe%3A%20%5BServer%20Buld%2020303.1%5D%20IIS%206%20Manager%20crashes%20trying%20to%20edit%20SMTP%20Virtual%20Server%20Properties%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2696895%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F406979%22%20target%3D%22_blank%22%3E%40KevinShaughnessy%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWell%2C%20that's%20fine%20it%20was%20deprecated%2C%20so%20what's%20the%20purpose%20of%20letting%20the%20feature%20SMTP%20to%20be%20installed%20on%20Windows%20Server%202022%2C%20if%20you%20can't%20manage%20it%20anymore.%3C%2FP%3E%3CP%3EWas%20my%20fault%20not%20reading%20this%20before%2C%20now%20I'm%20rolling%20back%20to%202019.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2700221%22%20slang%3D%22en-US%22%3ERe%3A%20%5BServer%20Buld%2020303.1%5D%20IIS%206%20Manager%20crashes%20trying%20to%20edit%20SMTP%20Virtual%20Server%20Properties%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2700221%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1140679%22%20target%3D%22_blank%22%3E%40NunoTex%3C%2FA%3E%20Sorry%20for%20the%20troubles.%20The%20management%20bug%20came%20about%20separately%20%2F%20unrelated%20to%20the%20deprecation%20of%20the%20SMTP%20stack.%20It%20should%20have%20still%20worked%20so%20long%20as%20the%20SMTP%20stack%20shipped%20in%20Windows%20but%20apparently%20some%20updates%20to%20the%20management%20console%20caused%20a%20regression%2Fbug%20here.%20Deprecation%20(when%20we%20no%20longer%20officially%20support%20something%20%2F%20use%20at%20your%20own%20risk)%20usually%20happens%20well%20in%20advance%20of%20removal%20(e.g.%20several%20years).%20In%20this%20case%2C%20due%20to%20the%20strategic%20shift%20at%20Microsoft%20to%20cloud%20services%20the%20backlog%20item%20to%20remove%20the%20SMTP%20stack%20from%20Windows%20was%20deprioritized%20much%20longer%20than%20originally%20expected.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2700879%22%20slang%3D%22en-US%22%3ERe%3A%20%5BServer%20Buld%2020303.1%5D%20IIS%206%20Manager%20crashes%20trying%20to%20edit%20SMTP%20Virtual%20Server%20Properties%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2700879%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F406979%22%20target%3D%22_blank%22%3E%40KevinShaughnessy%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOk%2C%20fair%20enough%2C%20at%20least%20you%20gave%20some%20honest%20feedback%20%3Asmiling_face_with_smiling_eyes%3A%3C%2FP%3E%3CP%3EIn%20meantime%20I%20rollback%20to%202019%2C%20since%20I%20needed%20the%20server%20ASAP.%3C%2FP%3E%3CP%3EWill%20see%20what%20solution%20can%20be%20used%20to%20replace%20this%20entirely.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2737252%22%20slang%3D%22en-US%22%3ERe%3A%20%5BServer%20Buld%2020303.1%5D%20IIS%206%20Manager%20crashes%20trying%20to%20edit%20SMTP%20Virtual%20Server%20Properties%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2737252%22%20slang%3D%22en-US%22%3EThis%20is%20a%20terrible%20move!%20A%20lot%20of%20us%20still%20utilize%20this%20feature%20heavily%2C%20if%20anything%2C%20it%20should%20be%20updated.%20Everything%20can't%20be%20pointed%20to%20365%2C%20this%20will%20force%20customers%20to%20evaluate%203rd%20party%20smtp%20software%20now.%3C%2FLINGO-BODY%3E
Contributor

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 the IIS 6 Management Console.

If I right-click the [SMTP Virtual Server] node and select properties, I get an error like this:

2021-03-16_20-20-52.png

Clues?

8 Replies
Hello, 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/hh...)

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
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?
Sorry about that. Try this: https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/hh...). 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.
Hmm. 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)

@KevinShaughnessy 

Well, that's fine it was deprecated, so what's the purpose of letting the feature SMTP to be installed on Windows Server 2022, if you can't manage it anymore.

Was my fault not reading this before, now I'm rolling back to 2019.

@NunoTex Sorry for the troubles. The management bug came about separately / unrelated to the deprecation of the SMTP stack. It should have still worked so long as the SMTP stack shipped in Windows but apparently some updates to the management console caused a regression/bug here. Deprecation (when we no longer officially support something / use at your own risk) usually happens well in advance of removal (e.g. several years). In this case, due to the strategic shift at Microsoft to cloud services the backlog item to remove the SMTP stack from Windows was deprioritized much longer than originally expected. 

@KevinShaughnessy 

Ok, fair enough, at least you gave some honest feedback :smiling_face_with_smiling_eyes:

In meantime I rollback to 2019, since I needed the server ASAP.

Will see what solution can be used to replace this entirely.

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.