User Profile
KevinShaughnessy
MicrosoftJoined 7 years ago
User Widgets
Recent Discussions
Re: [Server Buld 20303.1] IIS 6 Manager crashes trying to edit SMTP Virtual Server Properties
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.34KViews1like1CommentRe: [Server Buld 20303.1] IIS 6 Manager crashes trying to edit SMTP Virtual Server Properties
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)35KViews0likes5CommentsRe: [Server Buld 20303.1] IIS 6 Manager crashes trying to edit SMTP Virtual Server Properties
Sorry 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.35KViews1like6CommentsRe: [Server Buld 20303.1] IIS 6 Manager crashes trying to edit SMTP Virtual Server Properties
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/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 Transport35KViews0likes17CommentsRe: Exchange Message Trace Reporting and e-Discovery
EmyLoanzon Thanks so much for the additional info about those reports to encourage folks to use OneDrive or Sharepoint instead. Good to know! I'll share that info with my colleague who owns Message Trace UI / scenarios. Cheers!3.6KViews0likes0CommentsRe: Exchange Message Trace Reporting and e-Discovery
EmyLoanzon it's not included with E3, but with E5. It's available in ATP Plan 2 which comes with E5. https://docs.microsoft.com/en-us/microsoft-365/security/office-365-security/office-365-atp?view=o365-worldwide#office-365-atp-plan-1-and-plan-2 Can you elaborate on a non-security/threat related scenario where you'd want to trace messages by attachment type or name, where the concern isn't primarily security/threat related? Thanks!3.7KViews0likes2CommentsRe: Exchange Message Trace Reporting and e-Discovery
EmyLoanzon Threat Explorer in the Security Center allows you to search messages by file attachment, but as you know Message Trace does not. Whether or not to include a new capability in Message Trace is based on the scenario: If the scenario is more a security related investigation then it's a better candidate for Threat Explorer; if it's more about troubleshooting mail flow routing or delivery issues then it's a candidate for inclusion in Message Trace. Since all investigations that filter by attachment that we've heard about from customers are for security-related investigations, that capability landed in Threat Explorer.3.7KViews0likes4Comments
Recent Blog Articles
No content to show