On 1/14/19 11:02 AM, Stephan Bosch wrote:
Op 14-1-2019 om 9:58 schreef Dominik Menke:
On 1/13/19 12:23 PM, Stephan Bosch wrote:
With ssl=yes, the TLS layer is enabled immediately on the connection.
Again, that's not what the documentation says:
ssl=yes [...]: SSL/TLS is offered to the
Op 14-1-2019 om 9:58 schreef Dominik Menke:
On 1/13/19 12:23 PM, Stephan Bosch wrote:
With ssl=yes, the TLS layer is enabled immediately on the connection.
Again, that's not what the documentation says:
ssl=yes [...]: SSL/TLS is offered to the client, but the client
isn't required
On 1/13/19 12:23 PM, Stephan Bosch wrote:
With ssl=yes, the TLS layer is enabled immediately on the connection.
Again, that's not what the documentation says:
ssl=yes [...]: SSL/TLS is offered to the client, but the client
isn't required to use it.
If the client is not _required_ to
Op 13/01/2019 om 00:22 schreef Dominik Menke:
For reference: if you put ssl=yes there, the TLS layer is established
immediately. However, the standard ManageSieve protocol does not
support that (not currently anyway): only the establishment of the
TLS layer using the STARTTLS command is
For reference: if you put ssl=yes there, the TLS layer is established
immediately. However, the standard ManageSieve protocol does not support
that (not currently anyway): only the establishment of the TLS layer
using the STARTTLS command is part of the standard. That is why your
clients fail
Op 11/01/2019 om 16:05 schreef Dominik Menke:
Hello Gerald,
that did the trick, thank you very much!
--Dominik
On 1/11/19 10:54 AM, Gerald Galster wrote:
Hi Dominik,
I have set ssl = required in 10-ssl.conf globally but no ssl here:
service managesieve-login {
inet_listener sieve {
Hello Gerald,
that did the trick, thank you very much!
--Dominik
On 1/11/19 10:54 AM, Gerald Galster wrote:
Hi Dominik,
I have set ssl = required in 10-ssl.conf globally but no ssl here:
service managesieve-login {
inet_listener sieve {
port = 4190
}
...
}
Nevertheless,
