Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DisableSmtpParsing parameter is missing in Set-MpPreference #3505

Closed
HotCakeX opened this issue Jun 5, 2023 · 1 comment · Fixed by #3684
Closed

DisableSmtpParsing parameter is missing in Set-MpPreference #3505

HotCakeX opened this issue Jun 5, 2023 · 1 comment · Fixed by #3684
Assignees
Labels
area-defender Issues for defender module doc-bug For Upwork freelance team categories/reporting.

Comments

@HotCakeX
Copy link

HotCakeX commented Jun 5, 2023

DisableSmtpParsing parameter is available in Windows 11 build 22621.1778 Stable channel in Defender module's Set-MpPreference cmdlet but isn't listed in the document page.


Document Details

Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

@scanum scanum self-assigned this Jun 7, 2023
@scanum scanum added area-defender Issues for defender module doc-bug For Upwork freelance team categories/reporting. labels Jun 7, 2023
msbemba added a commit to msbemba/windows-powershell-docs that referenced this issue Oct 28, 2023
Updated DisableNetworkProtectionPerfTelemetry, DisableSmtpParsing, IntelTDTEnabled and ThrottleForScheduledScanOnly

Fixes MicrosoftDocs#3504

Fixes MicrosoftDocs#3505

Fixes MicrosoftDocs#3506

Fixes MicrosoftDocs#3508
@msbemba
Copy link
Contributor

msbemba commented Oct 28, 2023

@HotCakeX Thank you for your feedback. We have made changes to the document via PR##3684

Once the author approves, the changes will be live.

Thanks
Sri

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-defender Issues for defender module doc-bug For Upwork freelance team categories/reporting.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants