I had the problem that the only good way to check for valid e-mail
addresses at my firewall, which also does SPAM prevention and virus
scanning etc., is to use SMPT verify. Before I've setup Ciphermail my
internal mail server was the relay and handled this. With Ciphermail as
a relay between the firewall and my mail server hist was no longer
possible. As I found no solution on the web I decided to build my own:
With this SMTP verify works again. If you know other, better solutions,
please let me know. If you try this and find a bug drop me a note. This
is quick&dirty cut&paste code ... but it works.
MHC SoftWare GmbH
HR Coburg: B2242
Geschäftsführer: Matthias Henze
A new release candidate of the CipherMail gateway community edition is
now available (version 3.0.3-0).
* Support for MySQL/MariaDB and Oracle Database added.
* JDB connection tester tool added. This can be used to test a
connection to an external database (Postgres,
MySQL/MariaDB and Oracle Database).
* Log export functionality added to the virtual appliance (previously
this was a CipherMail Enterprise only feature).
* Because support for MySQL/MariaDB and Oracle Database was added, there
is now a separate package for Postgres. The
main back-end package no longer requires Postgres. The separate
postgres package can be used to auto configure a local postgres
* Mail generated by the web GUI ("Compose a test email" tool and "PDF
reply" page) is now sent to a special local port
on port 10027. This makes it possible to change settings on the
default smtpd port (25) without interfering with email sent from the
GUI. This requires an additional service setting for port 10027 in
* Java wrapper updated to 3.5.28
This fixes the following Java wrapper bugs: multi byte char logging
sometimes resulted in ? in the log files, memory leak on
* Libraries updated.
* Java 8 is now supported. Note: because of bug#
https://bugs.centos.org/view.php?id=9482, OpenJDK 8 on RedHat/CentOS
currently cannot be used because EC ciphers are not supported for
* Certificate request page now supports more request parameters
(country, locality, state, OU).
* Fix for bug GATEWAY-91. Djigzo should trim off whitespace in the
beginning and/or end of any PGP header lines. Note that this is not
enabled by default because this is not RFC compliant. A system
property must be set to enable this.
* Fix for bug GATEWAY-92. PDF encryption failed on non-standard Unicode
characters (Webdings font).
* Fix for bug GATEWAY-96. PGP keyring importer does not report import
failure if password is incorrect.
* Fix for bug GATEWAY-97. PGP/MIME signing a message with an invalid
content-transfer-encoding results in a message in the error queue.
* The database connection string is now stored in a separate xml
fragment (hibernate.connection.xml). This makes upgrading easier
because upgrading the hibernate configuration file no longer results
in overwriting the database connection string.
* The Web portal is now responsive (i.e., scales on smaller devices).
* Ciphermail.backup.enabled system property added which can be used to
disable backup option from the web GUI.
* Default Tomcat server.xml now only supports strong SSL/TLS ciphers
(ssllabs gives GUI an A rating).
The release candidate can be downloaded from
When upgrading an existing installation, a number of (minor) additional
configuration steps are required. See the upgrade guide for more
This release has been extensively tested. If there are no major issues
found this week, it will be officially released.
CipherMail email encryption
Email encryption with support for S/MIME, OpenPGP, PDF encryption and
secure webmail pull.
We have a domain for which encrypt mode has been set as mandatory. I
would like to know whether it is possible to exclude an email from
encryption based on its subject. I checked the configuration and saw
that there is an option to encrypt based on subject and would like to
know if there is any option that works in the other way.
I'm running ciphermail Version: 2.10.3-1. Built: 2015-07-07-09:13. Looking at the downloads section of the ciphermail website, I'm a little confused cause the latest version seems to be earlier than what I have, i.e. the latest version on the website is 2.10.0-3
I've created a proof of concept Thunderbird add on (based on Display
Mail User Agent), which indicates if a incoming mail was encrypted an/or
signed. At the moment I'm a bit confused about the Ciphermail Headers. I
need to understand them better. What's all about these numbers?
These are the combinations I found so far. But I found no rule when a 1
appears and if, why. Could there be other numbers? My problem is that I
can ask the TB API only for complete headers and not for fragments. This
is why I need to know which combinations are possible.
Besides of these numbers I also need a good explanation what exactly
could be derived form the headers. E.g. is it possible that a signed
mail is verified but not trusted and vice versa.
MHC SoftWare GmbH
HR Coburg: B2242
Geschaeftsfuehrer: Matthias Henze