Users March 2011

users@lists.ciphermail.com

4 participants
6 discussions

by Manuel Faux

Hi, I want to run multiple Djigzo instances on one server with one Postfix installation. What I did so far is the following: - Copied the Djigzo files in one folder for each instance - Created one database for each instance - Configured each instance to use its database in the hibernate.cfg.xml - Configured an individual SOAP port for each instance - Deployed the backend for each Djigzo instance (this was a bit tricky, because I had to modify djigzo-web to allow overruling some configuration values via the Tomcat context (feel free to contact me to hand over you the sources) because each instance has to use an own SOAP port) - Added the content filter pipe to Postfix's master.cf for each instance - Added the inet TCP socket for each instance in master.cf - Created one init script for each instance This setup works so far, but I'm unsure if I've forgotten something or some other things will interfere. I am aware of the fact I cannot use Djigzo-Web to configure Postfix anymore or to view the logs, does anyone see other limitations? Is there a documented way, how to chroot Djigzo? Kind Regards, Manuel Faux

10 years, 9 months

[Djigzo users] Question about content_filter

by Stefan-Michael Guenther

Hello, Djigzo adds the line content_filter = djigzo:127.0.0.1:10025 to /etc/postfix/main.cf. I already use this parameter to call Amavis: content_filter = smtp-amavis:[127.0.0.1]:10024 Is it possible to call Amavis after Djigzo or maybe the other round? Amavis has a few more entries in /etc/postfix/master.cf, e.g.: 127.0.0.1:10025 inet n - n - - smtpd -o content_filter= ..... But I guess it make more sense to first call Djizgo and Amavis afterwards. By the way, both programs like to use port 10025. Thanks for any suggestions or hints, Stefan

10 years, 10 months

[Djigzo users] Upgrade errors, do they matter?

by Nancy Anthracite

I just did the upgrade on Debian using the .db packages and ran into these errors during the process of doing it. I am presuming they do not matter, but I want to be sure. creating djigzo PostgreSQL database and database user ERROR: role "djigzo" already exists createdb: database creation failed: ERROR: database "djigzo" already exists ERROR: relation "admin" already exists ERROR: relation "admin_authority" already exists ERROR: relation "authority" already exists ERROR: relation "blob" already exists ERROR: relation "certificaterequest" already exists ERROR: relation "certificates" already exists ERROR: relation "certificates_email" already exists ERROR: relation "crls" already exists ERROR: relation "ctl" already exists ERROR: relation "ctl_namevalues" already exists ERROR: relation "keystore" already exists ERROR: relation "mail_repository" already exists ERROR: relation "mail_repository_recipients" already exists ERROR: relation "named_blob" already exists ERROR: relation "named_blob_named_blob" already exists ERROR: relation "properties" already exists ERROR: relation "properties_namevalues" already exists ERROR: relation "sms" already exists ERROR: relation "userpreferences" already exists ERROR: relation "userpreferences_certificates" already exists ERROR: relation "userpreferences_inheritedpreferences" already exists ERROR: relation "userpreferences_named_blob" already exists ERROR: relation "userpreferences_named_certificates" already exists ERROR: relation "users" already exists ERROR: constraint "fk31eb4613a92db044" for relation "admin_authority" already exists ERROR: constraint "fk31eb46135dd88a6" for relation "admin_authority" already exists ERROR: relation "certificaterequest_email_index" already exists ERROR: relation "certificaterequest_next_update_index" already exists ERROR: relation "certificaterequest_created_index" already exists ERROR: relation "certificates_issuer_index" already exists ERROR: relation "certificates_key_alias_index" already exists ERROR: relation "certificates_thumbprint_index" already exists ERROR: relation "certificates_creationdate_index" already exists ERROR: relation "certificates_subject_index" already exists ERROR: relation "certificates_store_name_index" already exists ERROR: relation "certificates_subject_key_id_index" already exists ERROR: relation "certificates_serial_index" already exists ERROR: constraint "fk904263596f91dc04" for relation "certificates_email" already exists ERROR: relation "crls_thumbprint_index" already exists ERROR: relation "crls_issuer_index" already exists ERROR: relation "crls_crlnumber_index" already exists ERROR: relation "crls_store_name_index" already exists ERROR: constraint "fkc370b4312c4f7350" for relation "ctl_namevalues" already exists ERROR: relation "keystore_alias_index" already exists ERROR: relation "keystore_storename_index" already exists ERROR: constraint "fk9f4a42d2a7662f3" for relation "mail_repository" already exists ERROR: constraint "fk16fd4d076bba8de5" for relation "mail_repository_recipients" already exists ERROR: constraint "fkef3face33f4fe1e7" for relation "named_blob" already exists ERROR: constraint "fkc12079bf50dff003" for relation "named_blob_named_blob" already exists ERROR: constraint "fkc12079bf9df0d9c9" for relation "named_blob_named_blob" already exists ERROR: constraint "fk1de74a19d9423b4c" for relation "properties_namevalues" already exists ERROR: relation "sms_datelasttry_index" already exists ERROR: relation "userpreferences_name_index" already exists ERROR: relation "userpreferences_category_index" already exists ERROR: constraint "fk8551364dfe700867" for relation "userpreferences" already exists ERROR: constraint "fk8551364d3f326a0d" for relation "userpreferences" already exists ERROR: constraint "fkb8b48a6e4e408931" for relation "userpreferences_certificates" already exists ERROR: constraint "fkb8b48a6e6f91dc04" for relation "userpreferences_certificates" already exists ERROR: constraint "fk46abee904e408931" for relation "userpreferences_inheritedpreferences" already exists ERROR: constraint "fk46abee90f11d70ab" for relation "userpreferences_inheritedpreferences" already exists ERROR: constraint "fka77dca154e408931" for relation "userpreferences_named_blob" already exists ERROR: constraint "fka77dca159df0d9c9" for relation "userpreferences_named_blob" already exists ERROR: constraint "fkaab29434a3567c25" for relation "userpreferences_named_certificates" already exists ERROR: constraint "fkaab294344e408931" for relation "userpreferences_named_certificates" already exists ERROR: constraint "fk6a68e08ba1f7c2e" for relation "users" already exists ERROR: relation "hibernate_sequence" already exists ERROR: relation "certificates_email_email_index" already exists -- Nancy Anthracite

10 years, 10 months

[Djigzo users] new bug fix release of the Djigzo gateway (2.0.1)

by Martijn Brinkers

Hi, An update of the Djigzo Gateway has been released which fixes a problem related to the DLP quarantine queue. Release notes: Bug fix * Fix for GATEWAY-15 (https://jira.djigzo.com/browse/GATEWAY-15). If a message was placed in quarantine because of a DLP violation and the message-id or from header contained a '%' character, deleting the mail from quarantine resulted in an error. This bug was reported by Andreas Beier. The updated version is only relevant if you are using the DLP functionality and quarantine messages that violate a DLP policy. The new release can be downloaded from www.djigzo.com. If you want to upgrade to the new version, please read the "Upgrade guide" (http://www.djigzo.com/documents/upgrade-guide.pdf) for instructions. Kind regards, Martijn Brinkers -- Djigzo open source email encryption

10 years, 10 months

[Djigzo users] Unable to locate tools.jar

by Nancy Anthracite

I am a rank newbie trying to use djigzo with an open source project I work on with WorldVistA (http://worldvista.org) for connecting WorldVistA EHR with the National Health Information Network using the NHIN Direct Project Gateway (http://wiki.directproject.org/). Thank you very much for making your code open source. It appears that it will be right on the money for solving a problem we are having and have expended a lot of energy trying to solve. I am in the process of installing djigzo 2.0.0.7 on a Debian machine and when running the sudo -u djigzo ant command encountered the error above. I tried to find a way to search the archives for a similar thread but I don't see a search function. Do I need to do something to address this? This is the full output with a check of Java alternatives on the machine at the end. I look forward to a reply. Thank you! *********** mail2:/usr/local/djigzo# sudo -u djigzo ant Unable to locate tools.jar. Expected to find it in /usr/lib/jvm/java-6- openjdk/lib/tools.jar Buildfile: /usr/local/djigzo/build.xml create-symlinks: [delete] Deleting directory /usr/local/djigzo/james-2.3.1/apps/james/SAR- INF/lib [mkdir] Created dir: /usr/local/djigzo/james-2.3.1/apps/james/SAR-INF/lib create-symlink: create-symlink: create-symlink: create-symlink: create-symlink: create-symlink: create-symlink: create-symlink: create-symlink: create-symlink: create-symlink: create-symlink: create-symlink: create-symlink: create-symlink: create-symlink: create-symlink: create-symlink: create-symlink: create-symlink: create-symlink: create-symlink: create-symlink: create-symlink: create-symlink: create-symlink: create-symlink: create-symlink: create-symlink: create-symlink: create-symlink: create-symlink: create-symlink: create-symlink: create-symlink: create-symlink: create-symlink: create-symlink: create-symlink: create-symlink: create-symlink: create-symlink: create-symlink: create-symlink: create-symlink: create-symlink: create-symlink: create-symlink: create-symlink: create-symlink: create-symlink: create-symlink: create-symlink: create-symlink: create-symlink: create-symlink: create-symlink: create-symlink: create-symlink: create-symlink: create-symlink: create-symlink: create-symlink: create-symlink: create-symlink: create-symlink: create-symlink: create-symlink: create-symlink: create-symlink: create-symlink: make-scripts-executable: create-sunjceprovider-softlink: [echo] create symlink to /usr/lib/jvm/java-6- openjdk/jre/lib/ext/sunjce_provider.jar in james-2.3.1/lib init-wrapper: init: [echo] Trying to load 'wrapper.dist.Linux.i386.properties' [echo] wrapper.dist.tar: wrapper-linux-x86-32-3.4.1.tar.gz [untar] Expanding: /usr/local/djigzo/wrapper/wrapper-linux- x86-32-3.4.1.tar.gz into /usr/local/djigzo/wrapper create-james-config-symlinks: [mkdir] Created dir: /usr/local/djigzo/james-2.3.1/apps/james/conf symlink-overwrite: symlink-overwrite: symlink-overwrite: symlink-overwrite: symlink-overwrite: symlink-overwrite: symlink-overwrite: symlink-overwrite: symlink-overwrite: symlink-overwrite: init: BUILD SUCCESSFUL Total time: 53 seconds mail2:/usr/local/djigzo# sudo update-alternatives --config java There is 1 choice for the alternative java (providing /usr/bin/java). Selection Path Priority Status ------------------------------------------------------------ 0 /usr/lib/jvm/java-6-openjdk/jre/bin/java 1061 auto mode * 1 /usr/lib/jvm/java-6-openjdk/jre/bin/java 1061 manual mode Press enter to keep the current choice[*], or type selection number: -- Nancy Anthracite

10 years, 10 months

[Djigzo users] New version of Djigzo gateway (2.0.0) released

by Martijn Brinkers

A new version of Djigzo gateway (2.0.0) has been released. The most notable new feature is the inclusion of a Data Leak Prevention (DLP) module which can be used to automatically scan outgoing email on keywords and regular expressions for sensitive data. If sensitive data is detected, the DLP module can take specific actions depending on the user settings: the email can be blocked or quarantined, or encryption can be enforced. Djigzo DLP currently filters email bodies, attachments and nested attachments of type text, html, xml and other text-based formats. Filtering attachments of type pdf, doc, xls etc. will be part of a future offering of Djigzo DLP. Release notes: New * Data leak prevention (DLP) module added * S/MIME strict mode * Locally generated notifications are now signed. If a locally generated notification is received by the gateway (for example because of email forwarding) the email is send as-is to prevent mail loops * DSN is now supported (DSN is transparently handled by the back-end) * Header protection can be disabled (GATEWAY-13) Improvements * workaround for non RFC compliant SKI support from Outlook 2010. For info why this workaround is needed see: https://bugzilla.mozilla.org/show_bug.cgi?id=559243 and http://www.ietf.org/mail-archive/web/smime/current/msg18730.html * Javamail updated to 1.4.4 final The new release and updated documentation can be downloaded from www.djigzo.com Kind regards, Martijn Brinkers -- Djigzo open source email encryption

10 years, 10 months

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

Users March 2011