github Set-OutlookSignatures/Set-OutlookSignatures v4.20.2
Release v4.20.2

latest releases: v4.22.0, v4.21.0, v4.20.4...
2 months ago

v4.20.2 - 2025-07-08

Add features with the Benefactor Circle add-on and get fee-based support from ExplicIT Consulting
See 'Benefactor Circle add-on' for details about these features and how you can benefit from them with a Benefactor Circle license.

Changed

  • Update dependency PreMailer.Net to v2.7.2.
  • Update Outlook add-in dependency @azure-msalbrowser to v4.14.0.

Added

Removed

Fixed

  • Update handling of the '@' character in signatures names. Microsoft no longer allows '@' in roaming signature names as it is reserved for internal use, and Microsoft Outlook will follow soon.
    • Add '@' to the list of invalid characters for signatures names as documented in sample INI files. The new complete list of invalid characters is '\/:"*?><,|@'.
    • Convert all invalid characters to '_', but '@' to '_at_'.
    • Only keep the '@' character where it is required for Microsoft internal use in roaming signature names.

File hashes and code signing

  • SHA256 hash of 'Set-OutlookSignatures_v4.20.2.zip': 9F92CC325560E978E762AAA947DB8F72CB4EC2A00B5FC4370C89F5191F15D75C
  • See 'hashes.txt' in 'Set-OutlookSignatures_v4.20.2.zip' for the hash value of every single file in the release.
    • Compare these hashes with the output of 'Get-ChildItem -Recurse | Get-FileHash -Algorithm SHA256'.
  • Files are code signed with ExplicIT Consulting's Extended Validation (EV) certificate.
    • Check the signature with 'Get-ChildItem -Include '*.ps*1', '*.dll' -Recurse | Get-AuthenticodeSignature'.

Don't miss a new Set-OutlookSignatures release

NewReleases is sending notifications on new releases.