On 04/13/2011 01:11 PM, Manuel Faux wrote: > Hi, > > Where is the system variable djigzo-web.home used? Is it really necessary to > set this variable? Is it possible to set it per Tomcat context?
djigzo-web.home is used to find the factory settings file for the web app (normally found in /usr/share/djigzo-web/conf/djigzo-web.properties) and to know where to store the uploaded SSL certificate (SSL certificate that's uploaded with the GUI). I have checked and almost all settings in djigzo-web.properties are set at the default value. The only exception are "upload.filesize-max" and "upload.requestsize-max" which I belief by default do not have a max. The upload max settings are used when you upload something to the gateway (a file with certificates, an attachment on the pdf reply page etc.). The upload max settings are the upper limit of any file you can send to the gateway. For the PDF reply page there is an additional maximum fort the allowed attachment "email.attachment.max-size" which is by default 5MB. So, if you do not need to override the default settings, an unlimited upload of acceptable and you do not need to upload a SSL certificate via the GUI you can skip setting djigzo-web.home. If you do need to override any setting I think you can use the method explained in the previous email using the Context. Kind regards, Martijn Brinkers > > -----Original Message----- > From: [email protected] [mailto:[email protected]] > On Behalf Of Martijn Brinkers > Sent: Friday, February 25, 2011 12:46 PM > To: [email protected] > Subject: Re: [Djigzo users] Multipe Djigzo Instances > > On 02/25/2011 10:46 AM, Manuel Faux wrote: >> 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? > > How does Postfix decide which back-end to use? based on sender domain? > > You should be able to manage Postfix and see the log files from the Web GUI > but each instance modifies the same Postfix config and shows the same log > file. > > Instead of modifying djigzo-web to use a different soap port you can specify > the soap port in the Tomcat context file > (/etc/tomcat6/Catalina/localhost): > > <Context docBase="/usr/share/djigzo-web/djigzo.war" unpackWAR="false"> > <Parameter name="djigzo.system.properties" > value="djigzo-web.spring.authenticator.config=spring-default-authenticator.xml djigzo.ws.server.port=12345" > override="false"/> > </Context> > > The <Parameter> setting overrides the <context-param> setting for > "djigzo.system.properties" in web.xml. In the above example, the soap port is > set to 12345. > >> Is there a documented way, how to chroot Djigzo? > > Djigzo runs on Java (OpenJDK) so you should chroot the complete OpenJDK > runtime. This is probably possible although I'm not sure whether it's worth > the effort since Java is very secure (unless you use Web Applets in your > browser but no one is using that any more :). > > Kind regards, > > Martijn > > -- > Djigzo open source email encryption > _______________________________________________ > Users mailing list > [email protected] > http://lists.djigzo.com/lists/listinfo/users > -- Djigzo open source email encryption
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ Users mailing list [email protected] http://lists.djigzo.com/lists/listinfo/users
smime.p7s
Description: S/MIME Cryptographic Signature
