I'm getting to know Djigzo and it looks really great!
I'm experimenting using a Google Gmail recipient. When the recipient receives
from Djigzo an encrypted email bearing a certificate for which the recipient has already
installed a key, the message is appropriately decrypted but there's always
an accompanying smime.p7m attachment. Is this what other users see? Is this
the intended result?
I'm using the Djigzo virtual appliance. And I'm using FireFox version 3.0.17 outfitted
with the Gmail S/MIME 0.4.5 plug-in.
Any insights would be greatly appreciated!
A new release of Djigzo (1.3.1) is available from www.djigzo.com.
* RPM packages for Red Hat/CentOS are now available. Install guides
updated with instructions for Red Hat/CentOS.
* S/MIME signatures can be selectively removed.
* S/MIME can selectively be skipped for calendar items (text/calendar).
Outlook cannot handle signed or encrypted meeting requests.
* CRL downloader and SMS gateway can now access external resources via
configurable HTTP Proxy.
* Config files split into multiple files to make upgrades easier when
local files have been changed.
* Password setting "Send to originator" added. If it's checked generated
passwords for the PDF will be sent to the "sender" of the message.
* Force signing trigger can be used to trigger S/MIME signing of a
message using a special email header.
* Certificate Trust List added which can be used to "white list" or
"black list" certificates.
* Messages sent from BlackBerry (via BIS) can now be relayed through Djigzo.
* Tomcat is now used by default instead of Jetty.
* Most templates are now by default UTF-8. Templates now fully support
* Backup and restore now works accross different PostgreSQL versions.
* Expired column is now shown in red when a certificate is expired.
* The Virtual Appliance now contains a firewall which blocks access to
ports that need not be externally accessible.
* support for MAC OSX Java wrapper added (patch subumitted by Rainer Frey).
* Original Message-ID of messages is retained if possible.
* Subject trigger is now recursively removed.
* Signature check sometimes failed for clear signed message which were
The documentation has been updated/improved as well.
If you want to upgrade to the new version please read the "Upgrade
guide" (http://www.djigzo.com/documents/upgrade-guide.pdf) for instructions.
Djigzo open source email encryption
Hi Guy and Gals (hey, a man can dream ;)),
i've just stumbled on Djigzo and i'm absolutly thrilled about it! This is
something i've been searching since the better part of the last decade, but
all other existing products where expensive and closed (and therefore not
I'm not really a programmer and only using this at home, but maybe there is
some other way to contribute? I'm a nativ Swiss, so if you plan to make it
internation, maybe i could contribute "German" (even if we're NOT germans
here, very important to emphasise that ;))
Are you planing something like this? If not, are you interested in
translations for the documentation?
I have a few questions myself:
- As i see it in the webgui, every signature that passes trough djigzo is
automatically loaded in the certstore. Is there a way to configure djizo so
it automatically uses this sig to encrypt mail that go to that mailadress,
without have to create a user or domain?
- Has someone done a specfile/srpm for RHEL (well centos in my case)?
- Do you plan to integrate GPG in the near future, or was this just a
possibility? (most of my private contacts have gpg keys, but no smime certs)
- Is there a generall roadmap what can be expected (or feared) in the