servers (services) can be configured to fail correct login, if the login
is made through plain-text channel. This is good, because MITM cannot
instantly see, if the password is correct or not, but the password goes
already plain-text and MITM can test it on secure connection later.
Regards,
Robert Wolf.
On Mon, 21 Aug 2017, Sebastian Arcus wrote:
> On 21/08/17 13:39, Robert Wolf wrote:
> >
> > On Mon, 21 Aug 2017, Sebastian Arcus wrote:
> >
> > >
> > > On 21/08/17 10:37, Gedalya wrote:
> > > > On 08/21/2017 07:28 AM, voy...@sbt.net.au wrote:
&
at they have to encrypt the email itself, if they want
protect it.
Regards,
Robert Wolf.
PG). But he cannot misuse your login.
Regards,
Robert Wolf.
On Tue, 22 Aug 2017, Ivan Warren wrote:
> Le 8/22/2017 à 10:03 AM, Robert Wolf a écrit :
> >
> > WRONG!!! The email is stored plain-text on the first server and then it can
> > be
> > sent to other few MX servers over plain-text connection. I.e. encrypted
> > c
data. Therefore they expect some real DB.
More feature == more requirements.
Regards,
Robert Wolf.
On Tue, 12 Sep 2017, Daniel Miller wrote:
> And remove that "postfix reload" command - Postfix doesn't require explicit
> reloading. It'll pickup the changed cert automagically.
>
> Daniel
Hoi Daniel,
are you sure? What is the refresh time? Instantly or with some delay? Have you
tested what h
On Wed, 13 Sep 2017, Luigi Rosa wrote:
> Robert Wolf wrote on 13/09/2017 10:26:
>
> > are you sure? What is the refresh time? Instantly or with some delay? Have
> > you
> > tested what happens if I install new key, but I delay installing correct
> > certificate?
fts_solr = url=http://localhost:8080/solr/
fts_decoder = decode2text
}
service decode2text {
executable = script /etc/dovecot/scripts/decode2text.sh
user = dovecot
unix_listener decode2text {
mode = 0666
}
}
Regards,
Robert Wolf.
