starred/Set-OutlookSignatures-Set-OutlookSignatures
1
0
Fork 0
mirror of https://github.com/Set-OutlookSignatures/Set-OutlookSignatures.git synced 2026-04-26 10:45:52 +03:00
Code Issues Projects Releases 10 Packages Wiki Activity
10 releases 105 tags
  • v4.20.0 feaeafdb7b

    v4.20.0 Stable

    kerem released this 2025-06-18 17:37:25 +03:00 | 23 commits to main since this release

    📅 Originally published on GitHub: Wed, 18 Jun 2025 14:39:08 GMT
    🏷️ Git tag created: Wed, 18 Jun 2025 14:37:25 GMT

    v4.20.0 - 2025-06-18

    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 MSAL.Net to v4.73.0.
    • Update dependency PreMailer.Net to v2.7.0.
    • Update Outlook add-in dependency @azure-msalbrowser to v4.13.1.
    • Update dependency QRCoder to v1.6.0.
    • Switch from dependencies AngleSharp and HTMLFile to HtmlAgilityPack v1.12.1.
    • Remove 'Set-Location -LiteralPath $PSScriptRoot' from scripts that do not require to know from which path they are run from.
    • Reduce Entra ID throttling probability in '.\sample code\SimulateAndDeploy.ps1' by applying the following changes:
      • Do not refresh the Graph token every time a new job is started, but only when:
        • Token is expired.
        • The remaining token lifetime is less than or equal the job timeout.
        • At least half of the token lifetime has already passed.
      • In case of an error, wait 70 seconds between the three retries.
    • Show all replacement variables in verbose output, not just the ones that have values. This helps detect null or empty values.
    • Rewrite and radically simplify the Quick Start Guide.
    • Reduce repository and release size by deleting unused image files and by outsourcing the detailed documentation to set-outlooksignatures.com.

    Added

    • Support for cross-tenant access and Multitenant Organizations. This allows to deploy signatures for mailboxes that are not hosted in the users home tenant, with all the properties, replacement variables and Benefactor Circle features being fully available. See the description of the parameter 'GraphClientID' in the parameter documentation for details.
    • Detect the encoding of HTML template files automatically, using the same logic as browsers do. See the FAQ 'Should I use .docx or .htm as file format for templates?' for details.
    • Convert HTML files to UTF8 when uploading or downloading roaming signatures, with the same logic browsers use. This is another fix for the problems of Outlook's own signature sync mechanism, and also solves issues with signatures that have been created manually in Non-UTF-8 encoding.
    • Check if the automatic variable '$PSScriptRoot' is available when scripts require to know from which path they are run from. This avoids follow-up problems when scripts are not run as file, but as selection of text in code editors.
    • Delete local copies of roaming signatures when cleaning up if they have previously been downloaded from other mailboxes (not the mailbox of the current user) and if these mailboxes are no longer available in Outlook.
    • Allow defining the text of the notification banner that is shown after a signature has been added to an email or an appointment by the Outlook add-in. The parameter is called 'NOTIFICATION_TEXT' and can be passed to 'run_before_deployment.ps1'.
    • Add 'Does it support cross-tenant access and Multitenant Organizations?' to the FAQ section.

    Removed

    Fixed

    • Switch from 'Set-Location $PSScriptRoot' to 'Set-Location -LiteralPath $PSScriptRoot' in scripts that do require to know from which path they are run from. This allows the use of paths containing characters with a specific meaning in PowerShell (square brackets, for example).
    • Fix a typo in source code of FAQ 'How can I start the software only when there is a connection to the Active Directory on-prem?' in the FAQ section, and add checks for the forest root domain and it's child domains.
    • Make sure that DOCX template files are not opened in "Read" view in Microsoft Word, as search and replace is not available in this view.
    • Make sure that temporary copies of template files are not write protected and do not have the "mark of the web", as both may lead to problems with search and replace or file type conversion in Microsoft Word.
    • Add support for Outlook profile names with special characters, which Classic Outlook for Windows saves in the registry using a completely unknown and not publicly documented encoding. Set-OutlookSignatures can not display the special characters correctly due to the unknown encoding, but can now read the contents without errors.
    • Make sure that leading whitespace in signature lines is correctly represented in the email draft containing all signatures (parameter 'SignatureCollectionInDrafts' and signature preview in the taskpane of the Outlook add-in).
    • Correctly handle HTML template files referencing the same image file multiple times but with different image replacement variables such as '$CurrentUserPhoto$': Do not overwrite image files which are referenced multiple times, create a new GUID named file instead.

    File hashes and code signing

    • SHA256 hash of 'Set-OutlookSignatures_v4.20.0.zip': CEA64ED45AD001CB845FFCC75AB439DD63A4ED07594044CC27E3920DF18F436E
    • See 'hashes.txt' in 'Set-OutlookSignatures_v4.20.0.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'.
    Downloads