Skip to content

SMLets Exchange Connector v3.1
Compare
Choose a tag to compare
@AdhocAdam AdhocAdam released this 13 Dec 21:42
· 37 commits to primary since this release
v3.1
4428506
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

SMLets Exchange Connector v3.1

General
The Management Pack (3.1.0.9) introduces 2 new UI elements to ignore digitally signed emails with invalid certificates and define the new [pwsh] keyword.

New Features

  • Emails with an invalid certificate can now be ignored for processing. You can also optionally trigger the Invoke-InvalidDigitalSignatureAction function through Custom Events.
  • New [pwsh] keyword and Custom Action (Invoke-ValidDigitalSignatureAction) introduces the ability invoke PowerShell directly from email. This use of this feature requires the use of digital signatures in order to securely verify the Sender's authenticity. For a list of ideas and how to get started, head over to the wiki.

Enhancements

  • More logging has been introduced to handle events generated by Mimekit
  • Emails that are both digitally signed and encrypted can now be parsed correctly

Bugs

  • When using the management pack outside of the United States, the Minimum File Size in KB decimal field can't pass validation due to use of different decimal delimiters used
  • When using the management pack outside of the United States, decimal fields that don't have validation (Announcement Hour Expirations, Azure Cognitive Services, and Azure Machine Learning) compound their values on every save of the MP. This eventually leads to an inability to open the Settings UI due to conversion overflow errors as the decimal values become so large that .NET can no longer parse them
    • If you experience this error, you unfortunately must delete the MP, re-import the MP, and then reconfigure your settings
    • If you do not currently experience this error, you should upgrade to prevent the error from occurring in your environment

Miscellaneous

  • MimeKit has been upgraded from v1.18.1 to v2.9.2
  • MimeKit requires the use of BouncyCastle cryptography. This new dll should be placed in the same location/alongside where MimeKit.dll is stored
  • If you're currently using Custom Events and wish to take advantage of the two new functions introduced in this release. Just copy the two new functions into your current Custom Events and save
Assets 3