Re: [Djigzo users] Problem after java-Update in CentOS 6

2016-05-18 Thread fatcharly 


> Gesendet: Mittwoch, 18. Mai 2016 um 10:43 Uhr
> Von: "Martijn Brinkers" 
> An: users@lists.djigzo.com
> Betreff: Re: [Djigzo users] Problem after java-Update in CentOS 6
>
> On 05/17/2016 06:16 PM, Martijn Brinkers wrote:
> > On 05/17/2016 06:02 PM, fatcha...@gmx.de wrote:
> >> Hi, I`m using a ciphermail on a CentOS 6 fully patched and it worked
> >> fine for quite a while, but after an update to
> >> java-1.6.0-openjdk-1.6.0.39-1.13.11.0.el6_7.x86_64 today, I found
> >> this in the /var/log/djigzo.log: ...ff60-ff601000
> >> r-xp  00:00 0  [vsyscall] JVM process is
> >> gone. JVM exited while loading the application. Launching a JVM... 
> >> JVM received a signal UNKNOWN (6). java version "1.6.0_39" OpenJDK
> >> Runtime Environment (IcedTea6 1.13.11) (rhel-1.13.11.0.el6_7-x86_64) 
> >> OpenJDK 64-Bit Server VM (build 23.25-b01, mixed mode)
> >>
> >> *** glibc detected ***
> >> /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.39.x86_64/jre/bin/java: double
> >> free or corruption (!prev): 0x01e5ac c0 *** ===
> >> Backtrace: = /lib64/libc.so.6(+0x75f4e)[0x7fc450e82f4e] 
> >> /lib64/libc.so.6(+0x78cf0)[0x7fc450e85cf0] 
> >> /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.39.x86_64/jre/bin/java[0x402fbb]
> >>
> >>
> > /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.39.x86_64/jre/bin/java(JavaMain+0x51c)[0x40373c]
> >> /lib64/libpthread.so.0(+0x7aa1)[0x7fc4515b0aa1] 
> >> /lib64/libc.so.6(clone+0x6d)[0x7fc450ef593d] 
> >>
> >> There were 10 failed launches in a row, each lasting less than 300
> >> seconds.  Giving up. There may be a configuration problem: please
> >> check the logs. <-- Wrapper Stopped
> >>
> >> On the Weblogin-page I got the message about a not fully started
> >> background problem.
> >>
> >> Any suggestions are welcome
> > 
> > This looks like a bug in Java 6. A similar bug was reported last week:
> > 
> > https://jira.djigzo.com/browse/GATEWAY-101
> > 
> > For now the best solution is to upgrade to Java 6. See bug report
> > #GATEWAY-101 for more information.
> > 
> > A possible workaround is to add the following line to the file
> > djigzo.wrapper.conf
> > 
> > wrapper.debug=true
> > 
> > Let me know whether this work around works for you. It looks like some
> > interaction between Java wrapper (which starts the Java process) and
> > Java 6 update.
> > 
> > I will investigate this further.
> 
> As a workaround (instead of installing Java 7), you can add
> wrapper.disable_console_input=FALSE to the Java wrapper config. You can
> add this option by editing the file /etc/init.d/djigzo
> 
> Change
> 
> WRAPPER_OPTS="wrapper.daemonize=TRUE"
> 
> To:
> 
> WRAPPER_OPTS="wrapper.daemonize=TRUE wrapper.disable_console_input=FALSE"
> 
> I'll contact the java wrapper developers. It might be some interaction
> bug between changes in Java 6 and java wrapper.
> 
Hi Martin,

thank you very much for your fast support. Mailencrypt and decrypt works fine 
with the last workaround.
But we are running in a new problem with the weblogin. I always get an 
ssl-error (ERR_SSL_FALLBACK_BEYOND_MINIMUM_VERSION -> Chrome) messages in FF 
and Chrome when I try to open the login page.
 

Kind regards

fatcharly


> Kind regards,
> 
> Martijn Brinkers
> 
> -- 
> CipherMail email encryption
> 
> Email encryption with support for S/MIME, OpenPGP, PDF encryption and
> secure webmail pull.
> 
> https://www.ciphermail.com
> 
> Twitter: http://twitter.com/CipherMail
> ___
> Users mailing list
> Users@lists.djigzo.com
> https://lists.djigzo.com/lists/listinfo/users
> 
___
Users mailing list
Users@lists.djigzo.com
https://lists.djigzo.com/lists/listinfo/users

Re: [Djigzo users] Problem after java-Update in CentOS 6

2016-05-18 Thread Martijn Brinkers 
On 05/18/2016 11:37 AM, fatcha...@gmx.de wrote:
> 
> 
>> Gesendet: Mittwoch, 18. Mai 2016 um 10:43 Uhr Von: "Martijn
>> Brinkers"  An: users@lists.djigzo.com 
>> Betreff: Re: [Djigzo users] Problem after java-Update in CentOS 6
>> 
>> On 05/17/2016 06:16 PM, Martijn Brinkers wrote:
>>> On 05/17/2016 06:02 PM, fatcha...@gmx.de wrote:
 Hi, I`m using a ciphermail on a CentOS 6 fully patched and it
 worked fine for quite a while, but after an update to 
 java-1.6.0-openjdk-1.6.0.39-1.13.11.0.el6_7.x86_64 today, I
 found this in the /var/log/djigzo.log:
 ...ff60-ff601000 r-xp  00:00 0
 [vsyscall] JVM process is gone. JVM exited while loading the
 application. Launching a JVM... JVM received a signal UNKNOWN
 (6). java version "1.6.0_39" OpenJDK Runtime Environment
 (IcedTea6 1.13.11) (rhel-1.13.11.0.el6_7-x86_64) OpenJDK 64-Bit
 Server VM (build 23.25-b01, mixed mode)
 
 *** glibc detected *** 
 /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.39.x86_64/jre/bin/java:
 double free or corruption (!prev): 0x01e5ac c0 ***
 === Backtrace: =
 /lib64/libc.so.6(+0x75f4e)[0x7fc450e82f4e] 
 /lib64/libc.so.6(+0x78cf0)[0x7fc450e85cf0] 
 /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.39.x86_64/jre/bin/java[0x402fbb]


>>>
 
/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.39.x86_64/jre/bin/java(JavaMain+0x51c)[0x40373c]
 /lib64/libpthread.so.0(+0x7aa1)[0x7fc4515b0aa1] 
 /lib64/libc.so.6(clone+0x6d)[0x7fc450ef593d] 
 
 There were 10 failed launches in a row, each lasting less than
 300 seconds.  Giving up. There may be a configuration problem:
 please check the logs. <-- Wrapper Stopped
 
 On the Weblogin-page I got the message about a not fully
 started background problem.
 
 Any suggestions are welcome
>>> 
>>> This looks like a bug in Java 6. A similar bug was reported last
>>> week:
>>> 
>>> https://jira.djigzo.com/browse/GATEWAY-101
>>> 
>>> For now the best solution is to upgrade to Java 6. See bug
>>> report #GATEWAY-101 for more information.
>>> 
>>> A possible workaround is to add the following line to the file 
>>> djigzo.wrapper.conf
>>> 
>>> wrapper.debug=true
>>> 
>>> Let me know whether this work around works for you. It looks like
>>> some interaction between Java wrapper (which starts the Java
>>> process) and Java 6 update.
>>> 
>>> I will investigate this further.
>> 
>> As a workaround (instead of installing Java 7), you can add 
>> wrapper.disable_console_input=FALSE to the Java wrapper config. You
>> can add this option by editing the file /etc/init.d/djigzo
>> 
>> Change
>> 
>> WRAPPER_OPTS="wrapper.daemonize=TRUE"
>> 
>> To:
>> 
>> WRAPPER_OPTS="wrapper.daemonize=TRUE
>> wrapper.disable_console_input=FALSE"
>> 
>> I'll contact the java wrapper developers. It might be some
>> interaction bug between changes in Java 6 and java wrapper.
>> 
> Hi Martin,
> 
> thank you very much for your fast support. Mailencrypt and decrypt
> works fine with the last workaround. But we are running in a new
> problem with the weblogin. I always get an ssl-error
> (ERR_SSL_FALLBACK_BEYOND_MINIMUM_VERSION -> Chrome) messages in FF
> and Chrome when I try to open the login page.

Works for me with CipherMail 2.10.0-3 on CentOS 6 with Java 6 and
Firefox and Chrome.

Which version of CipherMail are you using?

Kind regards,

Martijn Brinkers

-- 
CipherMail email encryption

Email encryption with support for S/MIME, OpenPGP, PDF encryption and
secure webmail pull.

https://www.ciphermail.com

Twitter: http://twitter.com/CipherMail

-- 
CipherMail email encryption

Email encryption with support for S/MIME, OpenPGP, PDF encryption and
secure webmail pull.

https://www.ciphermail.com

Twitter: http://twitter.com/CipherMail
___
Users mailing list
Users@lists.djigzo.com
https://lists.djigzo.com/lists/listinfo/users

[Djigzo users] Upgrade 2.10 to 3.05

2016-05-18 Thread lst_hoe02 

Hello,

we are on the way from Djigzo 2.10.0-3 to 3.0.5 mostly to keep up with  
releases. The upgrade guide list a additional injection port 10027  
needed for this release an i wonder why it is needed. Should mail  
injected there be passed through the djigzo gateway (again)? If yes,  
why not use the already used 10025 Djigzo input?
We have an AV Scanner listening at 10027 in our stack and i wonder  
which part of the setup to change...


Furthermore we have not found the additonal PostgreSQL package  
djigzo-postgres_3.0.5-0_all.deb mentioned in the Guide. Is it needed  
or is it just a configuration package?


Regards

Andreas



___
Users mailing list
Users@lists.djigzo.com
https://lists.djigzo.com/lists/listinfo/users

Re: [Djigzo users] Problem after java-Update in CentOS 6

2016-05-18 Thread Martijn Brinkers 
On 05/18/2016 11:37 AM, fatcha...@gmx.de wrote:
> 
> 
>> Gesendet: Mittwoch, 18. Mai 2016 um 10:43 Uhr Von: "Martijn
>> Brinkers"  An: users@lists.djigzo.com 
>> Betreff: Re: [Djigzo users] Problem after java-Update in CentOS 6
>> 
>> On 05/17/2016 06:16 PM, Martijn Brinkers wrote:
>>> On 05/17/2016 06:02 PM, fatcha...@gmx.de wrote:
 Hi, I`m using a ciphermail on a CentOS 6 fully patched and it
 worked fine for quite a while, but after an update to 
 java-1.6.0-openjdk-1.6.0.39-1.13.11.0.el6_7.x86_64 today, I
 found this in the /var/log/djigzo.log:
 ...ff60-ff601000 r-xp  00:00 0
 [vsyscall] JVM process is gone. JVM exited while loading the
 application. Launching a JVM... JVM received a signal UNKNOWN
 (6). java version "1.6.0_39" OpenJDK Runtime Environment
 (IcedTea6 1.13.11) (rhel-1.13.11.0.el6_7-x86_64) OpenJDK 64-Bit
 Server VM (build 23.25-b01, mixed mode)
 
 *** glibc detected *** 
 /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.39.x86_64/jre/bin/java:
 double free or corruption (!prev): 0x01e5ac c0 ***
 === Backtrace: =
 /lib64/libc.so.6(+0x75f4e)[0x7fc450e82f4e] 
 /lib64/libc.so.6(+0x78cf0)[0x7fc450e85cf0] 
 /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.39.x86_64/jre/bin/java[0x402fbb]


>>>
 
/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.39.x86_64/jre/bin/java(JavaMain+0x51c)[0x40373c]
 /lib64/libpthread.so.0(+0x7aa1)[0x7fc4515b0aa1] 
 /lib64/libc.so.6(clone+0x6d)[0x7fc450ef593d] 
 
 There were 10 failed launches in a row, each lasting less than
 300 seconds.  Giving up. There may be a configuration problem:
 please check the logs. <-- Wrapper Stopped
 
 On the Weblogin-page I got the message about a not fully
 started background problem.
 
 Any suggestions are welcome
>>> 
>>> This looks like a bug in Java 6. A similar bug was reported last
>>> week:
>>> 
>>> https://jira.djigzo.com/browse/GATEWAY-101
>>> 
>>> For now the best solution is to upgrade to Java 6. See bug
>>> report #GATEWAY-101 for more information.
>>> 
>>> A possible workaround is to add the following line to the file 
>>> djigzo.wrapper.conf
>>> 
>>> wrapper.debug=true
>>> 
>>> Let me know whether this work around works for you. It looks like
>>> some interaction between Java wrapper (which starts the Java
>>> process) and Java 6 update.
>>> 
>>> I will investigate this further.
>> 
>> As a workaround (instead of installing Java 7), you can add 
>> wrapper.disable_console_input=FALSE to the Java wrapper config. You
>> can add this option by editing the file /etc/init.d/djigzo
>> 
>> Change
>> 
>> WRAPPER_OPTS="wrapper.daemonize=TRUE"
>> 
>> To:
>> 
>> WRAPPER_OPTS="wrapper.daemonize=TRUE
>> wrapper.disable_console_input=FALSE"
>> 
>> I'll contact the java wrapper developers. It might be some
>> interaction bug between changes in Java 6 and java wrapper.
>> 
> Hi Martin,
> 
> thank you very much for your fast support. Mailencrypt and decrypt
> works fine with the last workaround. But we are running in a new
> problem with the weblogin. I always get an ssl-error
> (ERR_SSL_FALLBACK_BEYOND_MINIMUM_VERSION -> Chrome) messages in FF
> and Chrome when I try to open the login page.

It looks like Chrome, FF (and Java 6?) removed support for certain
ciphers. In the latest release of CipherMail (3.0.5) the list of
supported ciphers was optimized for security reasons (check with
ssllabs). However Java 6 does not support all those ciphers. The best
for now is to remove the ciphers lists setting from
/etc/tomcat6/server.xml. This way Tomcat will provide support for all
ciphers Java 6 supports. After changing server.xml, restart tomcat
(service tomcat6 restart)

Kind regards,

Martijn Brinkers


-- 
CipherMail email encryption

Email encryption with support for S/MIME, OpenPGP, PDF encryption and
secure webmail pull.

https://www.ciphermail.com

Twitter: http://twitter.com/CipherMail

-- 
CipherMail email encryption

Email encryption with support for S/MIME, OpenPGP, PDF encryption and
secure webmail pull.

https://www.ciphermail.com

Twitter: http://twitter.com/CipherMail
___
Users mailing list
Users@lists.djigzo.com
https://lists.djigzo.com/lists/listinfo/users

Re: [Djigzo users] Problem after java-Update in CentOS 6

2016-05-18 Thread Martijn Brinkers 
On 05/17/2016 06:16 PM, Martijn Brinkers wrote:
> On 05/17/2016 06:02 PM, fatcha...@gmx.de wrote:
>> Hi, I`m using a ciphermail on a CentOS 6 fully patched and it worked
>> fine for quite a while, but after an update to
>> java-1.6.0-openjdk-1.6.0.39-1.13.11.0.el6_7.x86_64 today, I found
>> this in the /var/log/djigzo.log: ...ff60-ff601000
>> r-xp  00:00 0  [vsyscall] JVM process is
>> gone. JVM exited while loading the application. Launching a JVM... 
>> JVM received a signal UNKNOWN (6). java version "1.6.0_39" OpenJDK
>> Runtime Environment (IcedTea6 1.13.11) (rhel-1.13.11.0.el6_7-x86_64) 
>> OpenJDK 64-Bit Server VM (build 23.25-b01, mixed mode)
>>
>> *** glibc detected ***
>> /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.39.x86_64/jre/bin/java: double
>> free or corruption (!prev): 0x01e5ac c0 *** ===
>> Backtrace: = /lib64/libc.so.6(+0x75f4e)[0x7fc450e82f4e] 
>> /lib64/libc.so.6(+0x78cf0)[0x7fc450e85cf0] 
>> /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.39.x86_64/jre/bin/java[0x402fbb]
>>
>>
> /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.39.x86_64/jre/bin/java(JavaMain+0x51c)[0x40373c]
>> /lib64/libpthread.so.0(+0x7aa1)[0x7fc4515b0aa1] 
>> /lib64/libc.so.6(clone+0x6d)[0x7fc450ef593d] 
>>
>> There were 10 failed launches in a row, each lasting less than 300
>> seconds.  Giving up. There may be a configuration problem: please
>> check the logs. <-- Wrapper Stopped
>>
>> On the Weblogin-page I got the message about a not fully started
>> background problem.
>>
>> Any suggestions are welcome
> 
> This looks like a bug in Java 6. A similar bug was reported last week:
> 
> https://jira.djigzo.com/browse/GATEWAY-101
> 
> For now the best solution is to upgrade to Java 6. See bug report
> #GATEWAY-101 for more information.
> 
> A possible workaround is to add the following line to the file
> djigzo.wrapper.conf
> 
> wrapper.debug=true
> 
> Let me know whether this work around works for you. It looks like some
> interaction between Java wrapper (which starts the Java process) and
> Java 6 update.
> 
> I will investigate this further.

As a workaround (instead of installing Java 7), you can add
wrapper.disable_console_input=FALSE to the Java wrapper config. You can
add this option by editing the file /etc/init.d/djigzo

Change

WRAPPER_OPTS="wrapper.daemonize=TRUE"

To:

WRAPPER_OPTS="wrapper.daemonize=TRUE wrapper.disable_console_input=FALSE"

I'll contact the java wrapper developers. It might be some interaction
bug between changes in Java 6 and java wrapper.

Kind regards,

Martijn Brinkers

-- 
CipherMail email encryption

Email encryption with support for S/MIME, OpenPGP, PDF encryption and
secure webmail pull.

https://www.ciphermail.com

Twitter: http://twitter.com/CipherMail
___
Users mailing list
Users@lists.djigzo.com
https://lists.djigzo.com/lists/listinfo/users

Re: [Djigzo users] Upgrade 2.10 to 3.05

2016-05-18 Thread Martijn Brinkers 
On 05/18/2016 04:13 PM, lst_ho...@kwsoft.de wrote:
> 
> Zitat von Martijn Brinkers :
> 
>> On 05/18/2016 03:33 PM, lst_ho...@kwsoft.de wrote:
>>> Hello,
>>>
>>> we are on the way from Djigzo 2.10.0-3 to 3.0.5 mostly to keep up with
>>> releases. The upgrade guide list a additional injection port 10027
>>> needed for this release an i wonder why it is needed. Should mail
>>> injected there be passed through the djigzo gateway (again)? If yes, why
>>> not use the already used 10025 Djigzo input?
>>> We have an AV Scanner listening at 10027 in our stack and i wonder which
>>> part of the setup to change...
>>
>> The port 10027 is used for email sent by the web GUI, i.e., email sent
>> from the PDF reply page and from the "Compose a test email" tool (admin
>> -> send email).
> 
> Sorry for being unclear. I was wondering if the mail injected to this
> port should pass the djigzo gateway or if it should be injected to
> postfix *without* being passed to the gateway by content_filter. We
> don't use PDF encryption or Reply so i have not checked how this is
> supposed to work.
> 
>>
>>> Furthermore we have not found the additonal PostgreSQL package
>>> djigzo-postgres_3.0.5-0_all.deb mentioned in the Guide. Is it needed or
>>> is it just a configuration package?
>>
>> Are you sure it is missing from the guide? The quick install guide pdf
>> and txt both mention the installation of
>> djigzo-postgres_3.0.5-0_all.deb...
>>
>> Oh I think you mean the upgrade guide? The reason why it was not added
>> was that if you upgrade, the database is already setup and configured.
>> You therefore do not need to install it when upgrading. That said, it
>> might be good to add it just to be complete.
>>
>> The djigzo-postgres package configures postgres and the database. You
>> only need this if you are going to use Postgres. Again for upgrading
>> this is not required although it does not hurt to install it.
>>
> 
> It is mentioned on the upgrade-guide page 4, but i was wondering about
> where to download this package. If it is only for automatic
> configuration we don't need it anyway.

This should be fixed now (refresh browser).

Thanks for reporting!

Martijn


-- 
CipherMail email encryption

Email encryption with support for S/MIME, OpenPGP, PDF encryption and
secure webmail pull.

https://www.ciphermail.com

Twitter: http://twitter.com/CipherMail
___
Users mailing list
Users@lists.djigzo.com
https://lists.djigzo.com/lists/listinfo/users

Re: [Djigzo users] Upgrade 2.10 to 3.05

2016-05-18 Thread Martijn Brinkers 
On 05/18/2016 03:33 PM, lst_ho...@kwsoft.de wrote:
> Hello,
> 
> we are on the way from Djigzo 2.10.0-3 to 3.0.5 mostly to keep up with
> releases. The upgrade guide list a additional injection port 10027
> needed for this release an i wonder why it is needed. Should mail
> injected there be passed through the djigzo gateway (again)? If yes, why
> not use the already used 10025 Djigzo input?
> We have an AV Scanner listening at 10027 in our stack and i wonder which
> part of the setup to change...

The port 10027 is used for email sent by the web GUI, i.e., email sent
from the PDF reply page and from the "Compose a test email" tool (admin
-> send email).

Originally the email sent from the web GUI was sent to localhost on port
25. The reason why we changed it to a special port (default 10027) is
that if the admin added some additional checks on the SMTP daemon on
port 25 (for example some anti spam check), this could interfere with
the email sent from the GUI.

If you want to switch back to using port 25 you can modify the port in
the following two config files in the directory /usr/share/djigzo-web/conf/

djigzo-web-portal.properties
djigzo-web.properties

The setting client.mail.smtp.port defines the port it connects to to
send email. In the latest version of CipherMail this has been changed
from 25 to 10027.

Alternatively, instead of changing back to port 25, you can change the
port to a different port, like for example 10028, and add an smtpd
service for that port in master.cf.

> Furthermore we have not found the additonal PostgreSQL package
> djigzo-postgres_3.0.5-0_all.deb mentioned in the Guide. Is it needed or
> is it just a configuration package?

Are you sure it is missing from the guide? The quick install guide pdf
and txt both mention the installation of djigzo-postgres_3.0.5-0_all.deb...

Oh I think you mean the upgrade guide? The reason why it was not added
was that if you upgrade, the database is already setup and configured.
You therefore do not need to install it when upgrading. That said, it
might be good to add it just to be complete.

The djigzo-postgres package configures postgres and the database. You
only need this if you are going to use Postgres. Again for upgrading
this is not required although it does not hurt to install it.


Kind regards,

Martijn Brinkers


-- 
CipherMail email encryption

Email encryption with support for S/MIME, OpenPGP, PDF encryption and
secure webmail pull.

https://www.ciphermail.com

Twitter: http://twitter.com/CipherMail
___
Users mailing list
Users@lists.djigzo.com
https://lists.djigzo.com/lists/listinfo/users

Re: [Djigzo users] Upgrade 2.10 to 3.05

2016-05-18 Thread lst_hoe02 


Zitat von Martijn Brinkers :


On 05/18/2016 03:33 PM, lst_ho...@kwsoft.de wrote:

Hello,

we are on the way from Djigzo 2.10.0-3 to 3.0.5 mostly to keep up with
releases. The upgrade guide list a additional injection port 10027
needed for this release an i wonder why it is needed. Should mail
injected there be passed through the djigzo gateway (again)? If yes, why
not use the already used 10025 Djigzo input?
We have an AV Scanner listening at 10027 in our stack and i wonder which
part of the setup to change...


The port 10027 is used for email sent by the web GUI, i.e., email sent
from the PDF reply page and from the "Compose a test email" tool (admin
-> send email).


Sorry for being unclear. I was wondering if the mail injected to this  
port should pass the djigzo gateway or if it should be injected to  
postfix *without* being passed to the gateway by content_filter. We  
don't use PDF encryption or Reply so i have not checked how this is  
supposed to work.





Furthermore we have not found the additonal PostgreSQL package
djigzo-postgres_3.0.5-0_all.deb mentioned in the Guide. Is it needed or
is it just a configuration package?


Are you sure it is missing from the guide? The quick install guide pdf
and txt both mention the installation of djigzo-postgres_3.0.5-0_all.deb...

Oh I think you mean the upgrade guide? The reason why it was not added
was that if you upgrade, the database is already setup and configured.
You therefore do not need to install it when upgrading. That said, it
might be good to add it just to be complete.

The djigzo-postgres package configures postgres and the database. You
only need this if you are going to use Postgres. Again for upgrading
this is not required although it does not hurt to install it.



It is mentioned on the upgrade-guide page 4, but i was wondering about  
where to download this package. If it is only for automatic  
configuration we don't need it anyway.


Regards

Andreas


___
Users mailing list
Users@lists.djigzo.com
https://lists.djigzo.com/lists/listinfo/users

Re: [Djigzo users] Upgrade 2.10 to 3.05

2016-05-18 Thread Martijn Brinkers 
On 05/18/2016 04:13 PM, lst_ho...@kwsoft.de wrote:
> 
> Zitat von Martijn Brinkers :
> 
>> On 05/18/2016 03:33 PM, lst_ho...@kwsoft.de wrote:
>>> Hello,
>>>
>>> we are on the way from Djigzo 2.10.0-3 to 3.0.5 mostly to keep up with
>>> releases. The upgrade guide list a additional injection port 10027
>>> needed for this release an i wonder why it is needed. Should mail
>>> injected there be passed through the djigzo gateway (again)? If yes, why
>>> not use the already used 10025 Djigzo input?
>>> We have an AV Scanner listening at 10027 in our stack and i wonder which
>>> part of the setup to change...
>>
>> The port 10027 is used for email sent by the web GUI, i.e., email sent
>> from the PDF reply page and from the "Compose a test email" tool (admin
>> -> send email).
> 
> Sorry for being unclear. I was wondering if the mail injected to this
> port should pass the djigzo gateway or if it should be injected to
> postfix *without* being passed to the gateway by content_filter. We
> don't use PDF encryption or Reply so i have not checked how this is
> supposed to work.

Normally this is configured to be handled by the back-end (i.e, using
the after queue filter) to make sure that email is encrypted if
required. For example you might want to encrypt a PDF reply message.
Another reason you might want email from the GUI to go through the
back-end is that the "Compose a test email" will be helpful to test if
encryption to external recipients work as expected without having to ask
someone with a mail client to send an email. If you however do not need
this functionality, you can skip sending email sent from the GUI through
the back-end by by setting content_filter to empty on the reinjection port.


>>
>>> Furthermore we have not found the additonal PostgreSQL package
>>> djigzo-postgres_3.0.5-0_all.deb mentioned in the Guide. Is it needed or
>>> is it just a configuration package?
>>
>> Are you sure it is missing from the guide? The quick install guide pdf
>> and txt both mention the installation of
>> djigzo-postgres_3.0.5-0_all.deb...
>>
>> Oh I think you mean the upgrade guide? The reason why it was not added
>> was that if you upgrade, the database is already setup and configured.
>> You therefore do not need to install it when upgrading. That said, it
>> might be good to add it just to be complete.
>>
>> The djigzo-postgres package configures postgres and the database. You
>> only need this if you are going to use Postgres. Again for upgrading
>> this is not required although it does not hurt to install it.
>>
> 
> It is mentioned on the upgrade-guide page 4, but i was wondering about
> where to download this package. If it is only for automatic
> configuration we don't need it anyway.

Oops you are right :( somehow the links are missing. I will fix it asap.

Thanks

Martijn

-- 
CipherMail email encryption

Email encryption with support for S/MIME, OpenPGP, PDF encryption and
secure webmail pull.

https://www.ciphermail.com

Twitter: http://twitter.com/CipherMail
___
Users mailing list
Users@lists.djigzo.com
https://lists.djigzo.com/lists/listinfo/users