search for: 2.2.28

Hi! I upgraded the 2.2 packages today (from 2:2.2.28-1~auto+5 to 2:2.2.28-1~auto+8) I now I'm getting an error: Mar 20 13:25:58 mproxy dovecot: auth: Error: imapc(email.charite.de:993): Couldn't initialize SSL context: Can't verify remote server certs without trusted CAs (ssl_client_ca_* settings) I checked, and alas, I had ssl_client_ca_dir = ssl_client_ca_file = So I set:

Aki Tuomi skrev den 2017-04-24 09:16: > We consider 2.2.28 stable release. Timo reported one bug in 2.2.28, so not so stable

On 6 Mar 2017, at 9.17, Tom Sommer <mail at tomsommer.dk> wrote: > > > On 2017-02-24 14:34, Timo Sirainen wrote: >> http://dovecot.org/releases/2.2/dovecot-2.2.28.tar.gz >> http://dovecot.org/releases/2.2/dovecot-2.2.28.tar.gz.sig > > Are there any plans to do a bugfix-release, that includes the few issues seen in the mailing-list, or do you consider 2.2.28 safe

http://dovecot.org/releases/2.2/dovecot-2.2.28.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.28.tar.gz.sig * director: "doveadm director move" to same host now refreshes user's timeout. This allows keeping user constantly in the same backend by just periodically moving the user there. * When new mailbox is created, use initially INBOX's dovecot.index.cache

http://dovecot.org/releases/2.2/dovecot-2.2.28.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.28.tar.gz.sig * director: "doveadm director move" to same host now refreshes user's timeout. This allows keeping user constantly in the same backend by just periodically moving the user there. * When new mailbox is created, use initially INBOX's dovecot.index.cache

> On February 28, 2017 at 4:32 PM Max Kostikov <max at kostikov.co> wrote: > > > I just recreated configuration of Dovecot 2.2.28 and got the same error > but in imap service (it was there in logs too as for dovecot-lda but I > don't saw it at time). > > Feb 27 20:09:41 beta dovecot: imap(postmaster at peek.ru): Panic: file > > mail-namespace.c: line

Your backtrace would've been informative already if you had issued bt full. Just opening it with gdb is not sufficient. Aki > On February 28, 2017 at 5:55 PM Max Kostikov <max at kostikov.co> wrote: > > > Probably I need to compile 2.2.28 from sources with debug flags. > Can you tell me wich flags I need to set for more informative backtrace > in gdb? > >

On 07.03.2017 10:52, Nagy, Attila wrote: > On 03/06/2017 11:30 PM, Timo Sirainen wrote: >> On 6 Mar 2017, at 9.17, Tom Sommer <mail at tomsommer.dk> wrote: >>> >>> On 2017-02-24 14:34, Timo Sirainen wrote: >>>> http://dovecot.org/releases/2.2/dovecot-2.2.28.tar.gz >>>> http://dovecot.org/releases/2.2/dovecot-2.2.28.tar.gz.sig >>>

I just recreated configuration of Dovecot 2.2.28 and got the same error but in imap service (it was there in logs too as for dovecot-lda but I don't saw it at time). > Feb 27 20:09:41 beta dovecot: imap(postmaster at peek.ru): Panic: file > mail-namespace.c: line 709 (mail_namespace_find): assertion failed: (ns > != NULL) > Feb 27 20:09:47 beta dovecot: lda(my at domain.ru):

I'm starting to see the following error when upgrading from 2.2.27 to 2.2.29. doveadm(ip.add.re.ss): Error: doveadm client disconnected before handshake: SSL_accept() failed: error:1417A0C1:SSL routines:tls_post_process_client_hello:no shared cipher Downgrading from 2.2.27 resolves, error still persists in 2.2.28. I'm using openssl 1.1.0.f and an ec cert/key with the following curve.

On 28.02.2017 13:16, Max Kostikov wrote: > Hi! > > I posted this problem few days ago in FreeBSD bugtracker > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217364 > So, the problem is in crash of dovecot-lda client while > local mailbox delivery with this message in log >> dovecot: lda(my at email): Panic: file mail-namespace.c: line 709 >> (mail_namespace_find):

> On February 28, 2017 at 7:43 PM Max Kostikov <max at kostikov.co> wrote: > > > Got it. > Here is full backtrace output. > Would appear the bug is in 'Trash' plugin. We'll open an issue about this, thank you for reporting this. Aki

Thank you. Will be waiting for Dovecot update. Aki Tuomi ????? 2017-02-28 20:34: >> On February 28, 2017 at 7:43 PM Max Kostikov <max at kostikov.co> wrote: >> >> >> Got it. >> Here is full backtrace output. >> > > Would appear the bug is in 'Trash' plugin. We'll open an issue about > this, thank you for reporting this. > >

On 28.02.2017 20:40, Max Kostikov wrote: > Thank you. > Will be waiting for Dovecot update. > > Aki Tuomi ????? 2017-02-28 20:34: >>> On February 28, 2017 at 7:43 PM Max Kostikov <max at kostikov.co> wrote: >>> >>> >>> Got it. >>> Here is full backtrace output. >>> >> >> Would appear the bug is in 'Trash'

Hello, On Thu, 6 Apr 2017 09:24:23 +0300 Aki Tuomi wrote: > On 06.04.2017 07:02, Christian Balzer wrote: > > > > Hello, > > > > this is on Debian Jessie box, dovecot 2.2.27 from backports, > > imap-hibernate obviously enabled. > > > > I've been seeing a few of these since starting this cluster (see previous > > mail), they all follow the

Hi there, I desperatly trying to store a BLF-CRYPT password hash in an LDAP userPassword Attribute and get dovecot to authenticate against it. I use a thunderbird as client and send the password plain with starttls. what worked so far but is kinda problematic for my smtp authenticaton was to store the has with the prefix {CRYPT} or {BLF-CRYPT}. Is there a way to get dovecot to authenticate

On 09/23/2016 08:05 AM, Aki Tuomi wrote: > On 29.07.2016 15:35, Nagy, Attila wrote: >> I use pass and userdb with dict protocol in a similar way: >> >> key passdb { >> key = passdb^MAuth-User: %u^MAuth-Pass: %w^MAuth-Protocol: >> %s^MClient-IP: %r >> format = json >> } >> >> (^M is an \r character, inserted with vi CTRL-v + enter)

Probably I need to compile 2.2.28 from sources with debug flags. Can you tell me wich flags I need to set for more informative backtrace in gdb? Aki Tuomi ????? 2017-02-28 17:42: > Can you please issue > bt full > in gdb and post the output here? -- With best regards, Max Kostikov BBM: 24CA5DF8 | W: https://kostikov.co -- With best regards, Max Kostikov BBM: 24CA5DF8 | W:

I have also tested with 2.2.28 and this version has the same issue. The finding of compatible ciphers is not the problem because I have uncommented the ldap entrys: TLSCipherSuite SECURE128:-ARCFOUR-128:-CAMELLIA-128-CBC:-3DES-CBC:-CAMELLIA-128-GCM TLSProtocolMin 3.1 Maybe you have further ideas. Am 2017-03-20 17:42, schrieb Aki Tuomi: >> On March 20, 2017 at 5:28 PM

Hello, Today I started noticing a very odd Dovecot error in the mail logs across 2 replicated Dovecot hosts via dsync. I have searched the Dovecot archives, Google, back tracked, downgraded Dovecot to earlier versions from earlier this year and ruled everything out I could think of to no avail. There really are not any helpful reports with what I am specifically seeing. The strange thing is only