Internal relay host and LMTP

HI,

I've a little problem/iprovement suggestion on WEB-GUI
../ciphermail/admin/mta/config :

My internal relay host is a dovecot-based IMAP-Server, with LMTP for
incomming mails from my borderfilter MX systems. On the web-gui I can
define IP-Address and Port, but not the required protocol LMTP. :confused:
Configuring via WEB-GUI isn't yet possible, so I've to configure this
directly in my main.cf postfix's option *transport_maps* like this
example:

transport_maps = hash:/etc/postfix/transport

in that file I've the required entry:
piraten-it.guru lmtp:[10.0.0.77]:24

It were great, if the WEB-GUI had an option to select the protocol
SMTP or LMTP :wink:

ttyl
Django

路路路

--
http://dokuwiki.nausch.org
http://wetterstation-pliening.info
http://ebersberger-liedersammlung.de

HI!

one again ... :wink:

piraten-it.guru lmtp:[10.0.0.77]:24

It were great, if the WEB-GUI had an option to select the protocol SMTP
or LMTP :wink:

Please don't forget lmtpS ! :wink:

O.K., that's all for now ...

ttyl
Django

路路路

Am 29.06.2015 um 15:21 schrieb django(a)nausch.org:
--
"Bonnie & Clyde der Postmaster-Szene!" approved by Postfix-God
http://wetterstation-pliening.info
http://dokuwiki.nausch.org
http://wiki.piratenpartei.de/Benutzer:Django

Hi Django,

The "problem" is that Postfix has a large number of options. If all
options would be supported by the web gui, the web gui would become too
difficult to use. So, it's our thinking that advanced (and not very
often used) features should be managed from the command line. In all
these years you are the first to request an option to change the
protocol so we will need to figure out whether it's worth while to add
this to the GUI or whether we will keep this as an advanced feature
which should be configured on the command line.

Kind regards,

Martijn Brinkers

路路路

On 06/29/2015 03:21 PM, django(a)nausch.org wrote:

I've a little problem/iprovement suggestion on WEB-GUI
../ciphermail/admin/mta/config :

My internal relay host is a dovecot-based IMAP-Server, with LMTP for
incomming mails from my borderfilter MX systems. On the web-gui I can
define IP-Address and Port, but not the required protocol LMTP. :confused:
Configuring via WEB-GUI isn't yet possible, so I've to configure this
directly in my main.cf postfix's option *transport_maps* like this example:

transport_maps = hash:/etc/postfix/transport

in that file I've the required entry:
piraten-it.guru lmtp:[10.0.0.77]:24

It were great, if the WEB-GUI had an option to select the protocol SMTP
or LMTP :wink:

--
CipherMail email encryption

Open source email encryption gateway with support for S/MIME, OpenPGP
and PDF messaging.

Twitter: http://twitter.com/CipherMail

HI Martijn,

The "problem" is that Postfix has a large number of options.

Oh yes, I know! :wink:

In all
these years you are the first to request an option to change the
protocol so we will need to figure out whether it's worth while to add
this to the GUI or whether we will keep this as an advanced feature
which should be configured on the command line.

O.K. I know, it's nice to have, but I think a small wish. :wink:

At the other end, MariaDB oder Oracle-Support is a killer-request.

O.K. one small question for today:

Cipermail is acting as post-queue-filter. May you tell me something
about ciphermail-integration in i.e. a AMaViS-Milter pre-queue enviroment?

ttyl
Django

路路路

Am 29.06.2015 um 16:26 schrieb Martijn Brinkers:
--
"Bonnie & Clyde der Postmaster-Szene!" approved by Postfix-God
http://wetterstation-pliening.info
http://dokuwiki.nausch.org
http://wiki.piratenpartei.de/Benutzer:Django

Afaik, a milter pre-queue milter is executed before an after queue
filter so the AMaViS-Milter should not interfere with the Ciphermail
post queue filter.

It's possible to combine an existing after queue filter, for example a
spam filter, with the Ciphermail after queue filter by chaining the filters.

For example

Postfix -> spam filter -> Ciphermail -> Postfix

Kind regards,

Martijn Brinkers

路路路

On 06/29/2015 04:36 PM, Django [BOfH] wrote:

HI Martijn,

Am 29.06.2015 um 16:26 schrieb Martijn Brinkers:

The "problem" is that Postfix has a large number of options.

Oh yes, I know! :wink:

In all
these years you are the first to request an option to change the
protocol so we will need to figure out whether it's worth while to add
this to the GUI or whether we will keep this as an advanced feature
which should be configured on the command line.

O.K. I know, it's nice to have, but I think a small wish. :wink:

At the other end, MariaDB oder Oracle-Support is a killer-request.

O.K. one small question for today:

Cipermail is acting as post-queue-filter. May you tell me something
about ciphermail-integration in i.e. a AMaViS-Milter pre-queue enviroment?

--
CipherMail email encryption

Open source email encryption gateway with support for S/MIME, OpenPGP
and PDF messaging.

Twitter: http://twitter.com/CipherMail

Zitat von "Django [BOfH]" <django(a)nausch.org>:

HI Martijn,

The "problem" is that Postfix has a large number of options.

Oh yes, I know! :wink:

In all
these years you are the first to request an option to change the
protocol so we will need to figure out whether it's worth while to add
this to the GUI or whether we will keep this as an advanced feature
which should be configured on the command line.

O.K. I know, it's nice to have, but I think a small wish. :wink:

As LMTP is only a somewhat more effective dumbed down SMTP the gain is
low in most environments and where it is useful the admin is aware of
tweaking the Postfix configuration by hand IMHO. The Djigzo GUI should
only reflect some basic set of Postfix options to get it go and stay
out of the way for the complete Postfix config.

At the other end, MariaDB oder Oracle-Support is a killer-request.

So the company in question like to spent a lot of cash for no
additional benefit. Maybe they will sponsor the work?

Regards

Andreas

路路路

Am 29.06.2015 um 16:26 schrieb Martijn Brinkers: