Upgrade 2.10 to 3.05

Gateway
1

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

2

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

···

On 05/18/2016 03:33 PM, lst_hoe02(a)kwsoft.de wrote:

--
CipherMail email encryption

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

Twitter: http://twitter.com/CipherMail

3

Zitat von Martijn Brinkers <martijn(a)ciphermail.com>:

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

···

On 05/18/2016 03:33 PM, lst_hoe02(a)kwsoft.de wrote:

4

Zitat von Martijn Brinkers <martijn(a)ciphermail.com>:

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 :frowning: somehow the links are missing. I will fix it asap.

Thanks

Martijn

···

On 05/18/2016 04:13 PM, lst_hoe02(a)kwsoft.de wrote:

On 05/18/2016 03:33 PM, lst_hoe02(a)kwsoft.de wrote:

--
CipherMail email encryption

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

Twitter: http://twitter.com/CipherMail

5

This should be fixed now (refresh browser).

Thanks for reporting!

Martijn

···

On 05/18/2016 04:13 PM, lst_hoe02(a)kwsoft.de wrote:

Zitat von Martijn Brinkers <martijn(a)ciphermail.com>:

On 05/18/2016 03:33 PM, lst_hoe02(a)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.

--
CipherMail email encryption

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

Twitter: http://twitter.com/CipherMail