gpg4o Changelog

What's new in gpg4o 8.5.0 Build 725

Oct 25, 2022
  • New functionalities for exporting decrypted e-mails: Individual e-mails or complete Outlook folders can be exported.
  • Ability to decrypt the subject of e-mails ("Protected Header").
  • Increased compatibility with modern (non-SKS) key servers and updated list of suggested key servers.
  • Introduction of experimental functions, which can be activated/deactivated globally.
  • New experimental functionality: Support for S/MIME encrypted and signed emails. For this purpose, the corresponding Outlook functionality has been integrated into gpg4o.
  • More detailed information about failed decryption and signature verification.
  • Improved handling of partially encrypted and/or signed e-mails.
  • Increased compatibility when reading emails from other Open PGP implementations.
  • New "Send Again" feature for encrypted/signed emails.
  • Gpg4o now supports GnuPG v2.2.33
  • Compatibility mode for processing emails with outdated encryption standard without MDC protection.
  • 54 bug fixes and minor comfort adjustments.

New in gpg4o 6.0.9 Build 9529 (Feb 19, 2019)

  • Support for Outlook 2019 implemented
  • Decryption of incoming emails
  • Decryption of all emails in a folder
  • Saving passphrases using DPAPI available
  • Handling of errors of the HomeDir backup improved
  • Pop out inline response when replying/forwarding PGP/MIME emails
  • Removed delay when sending emails with large amount of recipients
  • Replying/Forwarding non MDC protected emails improved

New in gpg4o 5.3.201 Build 9100 (Jun 21, 2018)

  • Emails without MDC protection can be decrypted after a security message
  • Encrypted emails will be sent MDC protected by default.
  • Registry Key “ReadAsPlain” is respected when rolled out per group policies.
  • (De)Activated keypairs are displayed correct again.
  • Support of GnuPG 1.4.23 and 2.2.8

New in gpg4o 5.3.100 Build 9082 (May 18, 2018)

  • MDC check for older GnuPG Versions (1.4.xx) implemented.
  • Fixed error – unable to change the GnuPG homedir path in gpg4o options.

New in gpg4o 5.3.8 Build 9035 (Jan 24, 2018)

  • Messages at startup no longer as single windows, but in a separate bar in Outlook
  • Performance improvements for multiple email accounts in one PST file
  • Release all references to emails opened from the file system after use
  • Minor improvements to program behavior and user interface
  • Improved GnuPG 2.2 support
  • Improved/simplified logging
  • Fixed a bug in the group policies (ADM and AMDX)
  • Allow to reply or forward not decrypted/decryptable e-mails
  • Improved caching of keys
  • Fixed key import when composing an email
  • Fixed error message displayed incorrectly within the trial period
  • Fixed handling of running GnuPG agents
  • Prevent multiple display of disabled queries
  • Avoid incorrectly displayed error message when sending an e-mail
  • Error message when unsuccessfully signing public keys added
  • Improved signatures of gpg4o program files

New in gpg4o 5.2.19 Build 8730 (Dec 22, 2017)

  • gpg4o now supports GnuPG version 2.2.0 upwards
  • Determination of the GnuPG path improved
  • Extended signature verification is now enabled by default
  • Performance optimization for account management
  • Fixed manual path entry during key creation for revocation certificate and backup
  • Several possible dialogs after key creation combined to a single one
  • Optimized structure and content of the manuals
  • Several other minor bugs fixed

New in gpg4o 3.5.43.6457 (Nov 26, 2015)

  • Fixed an issue at the initialization of the add-in
  • Fixed an issue at the initialization of new email windows
  • Better handling of too large attachments
  • Limited the amount of logfiles to prevent too large attachments on support requests

New in gpg4o 3.5.39.6410 (Nov 26, 2015)

  • Support of Microsoft Windows 10 and Microsoft Office 2016
  • Added Gnupg version checking and update
  • Added management of identities (User-IDs) of keys
  • Passphrase dialog shows the key for which the passphrase is requested
  • Automatic signature verifcation of all attachments
  • Improved signature verifcation in case of a difference between the signature and the sender
  • Email preview automaticall resizes to the best fit
  • Export of keys to the clipboard is now possible
  • gpg4o supports the zoom slider of Outlook in its own email preview
  • Fingerprints for subkeys will also be shown now + Optimized performance and stability
  • Optimized handling of unusable keys when sending emails
  • Bugfixes when using “Send from”
  • Fixed minor problems with handling of keys
  • [Administrators] Setup completely rebuilt

New in gpg4o 3.4.104.5555 (Nov 26, 2015)

  • Fixed an issue in the update mechanism

New in gpg4o 3.4.103.5490 (Apr 30, 2015)

  • This is a patch release especially for PGP/MIME handling
  • Bug resolved: Handling of PGP/MIME Mails with non RFC compatible content type
  • Starting behaviour of Outlook improved. Its faster now
  • Improved handling of PGP/MIME Signature handling
  • Deleted unnecessary userprompt

New in gpg4o 3.4.19.5391 (Dec 30, 2014)

  • Now it’s possible to verify detached signatures (PGP/MIME signatures) (The extended signature checking has to be activated when you select such an email)
  • Improved resolving process of recipients to their public keys
  • The improved key selection dialog can be opened before sending an email to verify or change a key for a recipient
  • Alternative sending email addresses (“Send To” – field in OL) are now supported (The configuration of these new accounts could be done in “gpg4o” options dialog)
  • Reading of encrypted mails when Outlook’s security setting “Read all mail in plain text” is active
  • Reduced startup time of “gpg4o” in Outlook
  • Several performance improvements and bugfixes
  • Usage of Long Key-IDs doublechecked
  • Central administration of Keyserver and Autoimport-Keyserver possible

New in gpg4o 3.3.26.5094 (Dec 30, 2014)

  • Fixed a refresh issue in the send options
  • Fixed issue while sending encrypted attachments
  • Fixed issues while upgrading the configuration from 3.2 to 3.3