Hi Phil
Have you taken a look at dovecot’s namespaces?
https://doc.dovecot.org/configuration_manual/shared_mailboxes/public_shared/
No idea personally, just searched for it now based on your question.
When you mention chattr I assume you’re referring to setting the immutable
bit / flag eg. https
A HTTP API for IMAP and for that matter, POP3 and SMTP is exactly what we
built where I work.
For anyone wonder why build such a thing? A simplified interface is an
exceptionally powerful tool. Many of our clients have encountered issues
constructing multipart http requests so if that’s an issue,
Background:
Dovecot: v 2.0.9
OS: AWS Linux (derived from CentOS)
At this stage I've avoided upgrading to a newer version of Dovecot as
version 2.0.9 is what AWS Linux provides and I'd like to be able to run
a regular AWS Linux installation if I can. As opposed to pulling newer
versions
I noticed a similar/same discussion back on Aug 14th titled force
ciphers order for clients. However from that thread I can't find quite
what I'm after.
From my testing of dovecot 2.1.6, by default it appears to honor the
clients cipher list order for SSL/TLS connections.
I can't find any do
what operating system?
what openssl version?
openssl-1.0.1 supports TLS 1.2
openssl-1.0.0 does not
Thanks for that, yeah the OS is GNU Linux and openssl is currently at
version 1.0.0.
That explains it.
Hi
I'm running dovecot 2.1.6 and am trying to configure it to require TLS
1.2. So far I've only got as far as getting TLS 1.0 going.
In the config file /etc/dovecot/conf.d/10-ssl.conf, I've
tried setting ssl_protocols to values like TLSv1.2:!TLSv1:!SSL3 but
without any success.
Attempts to
