similar to: proxy, managesieve and ssl?

Hello, If you don?t have a ssl_key and ssl_cert configured in your dovecot config managesieve-login will fail to start with the following error message: dovecot: managesieve-login: Fatal: Couldn't parse private ssl_key: error:0906D06C:PEM routines:PEM_read_bio:no start line: Expecting: ANY PRIVATE KEY, even if you haven?t enabled ssl for managesieve-login. Infos according to

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, STARTTLS is offered "IMPLEMENTATION" "Dovecot Pigeonhole" "SIEVE" "fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags

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 connects to port 4190? Looking > > ... at the default configuration files in /etc/dovecot/conf.d/ I don't > see an obvious difference. > > > --Dominik Can you provide

Hi, I have a "ubuntu10.04 + dovecot-2.0.13" configuration in my server. It works fine with ~50k accounts. Recently I enabled TLS: $ cat /etc/dovecot/dovecot.conf ... # Use SSL ? ssl = yes ... The goal was to provide only IMAPS and POP3S. But Managesieve says "STARTTLS": $ telnet _MY_IP_ 2000 Trying _MY_IP_... Connected to _MY_IP_. Escape character is '^]'.

Hi, I am using Dovecot 2.1.16. I'm trying to get Roundcube to talk to the managesieve plugin. Postfix/Dovecot/Roundcube all exist on the same server. I'd like to get managesieve working. I've gone through a few guides, such as: https://wiki.archlinux.org/index.php/dovecot#Sieve But so far roundcube won't connect to the managesieve plugin. ("Cant reach server").

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 { >> ???? port =

Hello Everyone, I am running Dovecot 2.0.15 with its Sieve plug-in, and Roundcube 0.5.3. I have a problem with just one particular user, who after creating a filters set and creating a filter in Roundcube, this user cannot activate the filters set. At first, this user could not create a filter at all. That was resolved by creating the "sieve" directory with the right permissions in

Hello dovecot users, I have updated the MANAGESIEVE patch to (hopefully) fix the compilation issues reported by Robin Breathe. This is a patch against the latest stable release 1.0.3. It currently won't compile with 1.1 due to significant changes in the master code. Change Log V6 ------------- - Corked the client output stream while producing the capability greeting and on other some

As mentioned on earlier email, are you sure you are connecting to port 4190 and not 143 for ManageSieve? Aki > On 06/11/2019 17:48 telsch via dovecot <dovecot at dovecot.org> wrote: > > > I need a more detailed hint. Dovecot proxy IMAP is running fine, but how > to add to the same proxy managesieve support? > > I thougt it's activated in the proxy: >

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 = plain login scram-sha-1 service managesieve-login { inet_listener sieve {

http://dovecot.org/releases/2.1/alpha/dovecot-2.1.alpha1.tar.gz http://dovecot.org/releases/2.1/alpha/dovecot-2.1.alpha1.tar.gz.sig So it's time for the first alpha version of Dovecot v2.1. There are no huge intrusive changes, so I expect v2.1.0 to be released this year (maybe even in a few months?) The biggest changes are related to full text search handling. I'll probably still make

http://dovecot.org/releases/2.1/alpha/dovecot-2.1.alpha1.tar.gz http://dovecot.org/releases/2.1/alpha/dovecot-2.1.alpha1.tar.gz.sig So it's time for the first alpha version of Dovecot v2.1. There are no huge intrusive changes, so I expect v2.1.0 to be released this year (maybe even in a few months?) The biggest changes are related to full text search handling. I'll probably still make

Hi, I've enabled client certificate authentication for imap and managesieve. When I use Thunderbird with the sieve plugin it tries to login, but times out. Initially I reported this to the sieve plugin, but we came to the conclusion that it managesieve is misbehaving. https://github.com/thsmi/sieve/issues/94 Thunderbird (win10-64) 52.4.0 (32bit) Sieve 0.2.3k Dovecot (Ubuntu 16.04.3 LTS)

Hello, I've got dovecot 1.2.11 running on Fedora 12 (x86_64) with the managesieve protocol and sieve plugins enabled, with deliver handling local delivery. I've set disable_plaintext_auth = yes ssl = yes ssl_cert_file = /etc/pki/dovecot/certs/dovecot.pem ssl_key_file = /etc/pki/dovecot/private/dovecot.pem mail_debug = yes protocol managesieve { listen = *:2000 login_executable =

Hi! I'm trying to get information about a server certificate from a pigeonhole sieve server. Various connection attempts show only "wrong version number" or "unknown protocol" errors from openssl: $ openssl s_client -connect example.com:4190 { -tls1, -tls1_1, -tls1_2 } [ -starttls { imap, pop3 } ] None of these work. I'm trying to see who signed the server cert. How

Also those variables can't be returned from passdb as they are needed pre-auth. Sami > On 6 Nov 2019, at 16.51, Aki Tuomi via dovecot <dovecot at dovecot.org> wrote: > > You are hardcoding the port. I'm pretty sure your managesieve is not listening on 143 =) > > Aki > >> On 06/11/2019 16:46 telsch via dovecot <dovecot at dovecot.org> wrote:

Hi, TLS on imap port 143 works. But if I try TLS on managesieve port 4190, I get no connection. Dec 12 21:16:10 managesieve-login: Info: Disconnected (no auth attempts in 5 secs): rip=192.168.10.117, lip=192.168.10.117, secured Dec 12 21:16:20 managesieve-login: Info: Disconnected (no auth attempts in 5 secs): rip=192.168.10.117, lip=192.168.10.117, TLS handshaking: Disconnected # gnutls-cli

Hi, I allow only TLS/SSL connection to dovecot. The managesieve doesn't work with TLS but it works without it. gladiac at magrathea:~> gnutls-cli -p 2000 -s --insecure -V milliways.cynapses.org Resolving 'milliways.cynapses.org'... Connecting to '213.239.217.124:2000'... - Simple Client Mode: - Received[194]: "IMPLEMENTATION" "dovecot"

Send this to dovecot at dovecot.org, not dovecot-owner at dovecot.org On 14.3.2012, at 4.45, paul wrote: > HI. I have just started to play with sieve and everything seems ok when > logging on using telnet localhost 4190 and an encoded username/password. > If I try to connect with firefox at localhost:4190 I get > "IMPLEMENTATION" "Dovecot Pigeonhole" >

Hello, there is a problem between Dovevot 1.2 Managesieve 0.11.7 and Horde webmail 1.2.2 (possibly also in 1.2.3) in imap4flags $ telnet localhost 2000 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. "IMPLEMENTATION" "dovecot" "SIEVE" "fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric