Gpgmailencrypt

Latest version: v3.4.7

Safety actively analyzes 701215 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 2 of 4

3.3.0

new features:
* mails can be decrypted automatically, see configuration entry:
[default]
decrypt=True

The private key must be in the private key ring of the gpg-mailencrypt user and without password protection
* many bugfixes

3.2.2

This is a bugfix release.
New feature: mails can be encrypted with additional keys. See config entries

[sql]
use_sqlgpgencryptionkey
use_sqlsmimeencryptionkeys,
gpgencryptionkeysql
smimeencryptionkeysql

[gpg]
encryptionkeys

[smime]
encryptionkeys

3.2.1

This is a major update. Besides a lot of bugfixes it introduces some new security features. The first is the "securitylevel" configuration option. It allows you to have a finer grained handling of e-mails, that can't be encrypted.

Security levels are:

* "**may**" (default) sends e-mails any way, even unencrypted
* "**redirect**" sends unencryptable e-mails to another smtp server, and
* "**bounce**" does not deliver unencryptable e-mails, the sender get's a bounce message instead.

Second security enhancement is the storage of all passwords with a much strong hashing algorithm (bcrypt). When logging in via the admin console, the user password will be automatically changed to the stronger hash.

3.1.2

This is a bugfix release

3.1.1

This is a bugfix release

3.1.0

This is a major update. Besides a lot of bugfixes the following features are implemented:
pdf passwords can be stored in (sql) database backends

Page 2 of 4

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.