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 t
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
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 t
TLS negotiation now."
...
You can check if it works with tcpdump:
tcpdump -nn -l -A -i eth0 port 4190
Best regards
Gerald
Am 11.01.2019 um 09:59 schrieb Dominik Menke :
Sure, here you go (I've masked a few unimportant fields, though):
# 2.2.33.2 (d6601f4ec): /etc/dovecot/
= yes
}
service_count = 1
}
service managesieve {
process_limit = 256
}
ssl_cert =
On 10.1.2019 18.28, Dominik Menke wrote:
I've missed a part at the end:
This leads me to my question: How do I force Dovecot to print at
least a STARTTLS line after a client connec
I've missed a part at the end:
This leads me to my question: How do I force Dovecot to print at least a
STARTTLS line after a client connects to port 4190? Looking
... at the default configuration files in /etc/dovecot/conf.d/ I don't
see an obvious difference.
--Dominik
Hello list,
I'm trying to get pidgeonhole/managesieve running, and I'm stuck
connecting clients to the server (Dovecot 2.2.33.2-1ubuntu4.1 on an
Ubnutu 18.04 machine). So far, my config looks like this:
protocols = imap lmtp sieve
disable_plaintext_auth = yes
auth_mechanisms = pl
