search for: login_settings

Hi, I came up with the following patch while trying to figure out a good solution for the situation described in Debian bug #871987[1]. In short, OpenSSL in Debian unstable has disabled TLSv1.0 and TLSv1.1 *by default*. That means that unless an application requests otherwise, only TLSv1.2 is supported. In the world of e-mail this is seemingly an issue, as there are still way too many old clients

....0/src/config -DPKG_LIBEXECDIR=\""/usr/local/libexec/dovecot"\" -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -Wstrict-aliasing=2 -module -avoid-version -g -Wl,--as-needed -o libmanagesieve_login_settings.la -rpath /usr/local/lib/dovecot/settings libmanagesieve_login_settings_la-managesieve-login-settings.lo libmanagesieve_login_settings_la-managesieve-login-settings-plugin.lo -lrt gcc -DHAVE_CONFIG_H -I. -I../.. -I/usr/src/dovecot-2.0/dovecot-2.0 -I/usr/src/dovecot-2.0/dovecot-2.0/src/lib -I/usr/s...

I upgraded 2.1 -> 2.2 something like a week ago because I needed INDEXPVT. Not sure if this crash started immediately or not, noticed it today looking at journalctl. Backtrace http://bpaste.net/raw/181944/ and pasted below. This seems to crash on every IMAP connection made, so any ideas for a possible client-level workaround are quite welcome until dovecot code improves here. root at

#0 0x00007f497ecdb067 in __GI_raise (sig=sig at entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 resultvar = 0 pid = 10092 selftid = 10092 #1 0x00007f497ecdc448 in __GI_abort () at abort.c:89 save_stage = 2 act = {__sigaction_handler = {sa_handler = 0xfffe, sa_sigaction = 0xfffe}, sa_mask = {__val = {1024, 140722499998576, 94791001010256, 513,

Reading symbols from /usr/local/dovecot-2.2/libexec/dovecot/pop3...done. [New LWP 17294] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/i386-linux-gnu/i686/cmov/libthread_db.so.1". Core was generated by `dovecot/pop3'. Program terminated with signal 11, Segmentation fault. #0 0x0804eb6a in client_update_mails (client=client at entry=0x82017a0)

...ssl_proxy_ctx_use_key(ctx->ctx, ssl_set); if (ctx->verify_client_cert) - ssl_proxy_ctx_verify_client(ctx->ctx, xnames); + ssl_proxy_ctx_verify_client(ctx->ctx); hash_table_insert(ssl_servers, ctx, ctx); return ctx; @@ -1343,12 +1310,10 @@ ssl_proxy_init_client(const struct login_settings *login_set, const struct master_service_ssl_settings *ssl_set) { - STACK_OF(X509_NAME) *xnames; - if ((ssl_client_ctx = SSL_CTX_new(SSLv23_client_method())) == NULL) i_fatal("SSL_CTX_new() failed"); - xnames = ssl_proxy_ctx_init(ssl_client_ctx, ssl_set, TRUE); - ssl_proxy_c...

100% reproducible. User is using alpine to write an email. Continue postponed composition (answering "No" won't erase it)? y -> [>Empty folder! No messages really postponed!<] Can't delete {mproxy.charite.de/ssl/novalidate-cert/user=theusername}postponed-msgs Setup: ====== http://wiki2.dovecot.org/HowTo/ImapcProxy coredump available for further inspection Full

Hello, I'm using the Debian builds of dovecot-2.2 by S[r]us. Today I started getting the following panic: log: Panic: file priorityq.c: line 122 (priorityq_remove_idx): assertion failed: (idx < count) log: Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x7f1ae) [0x7fd368dc31ae] -> /usr/lib/dovecot/libdovecot.so.0(+0x7f269) [0x7fd368dc3269] ->

Hi! After upgrading from Debian wheezy with (self compiled) dovecot 2.2.15 to Debian jessie with (self compiled) 2.2.24, I observe the following segmentation fault in the logs: Jun 7 09:23:09 imap dovecot: imap(user at example.com): Error: read(<imap client>) failed: read(size=8003) failed: Connection reset by peer (uid=0, box=trash) Jun 7 09:23:09 imap dovecot: imap(user at

Hi, could not find it -- back to the list, maybe someone can suggest a fix/workaround. Best, Tamas On Wed, Oct 07 2015, Dominik Breu wrote: > Hello, > > yeah this one looks familiar to me can you search the list back in > september there was a somewhat similar bug with thunderbird imho timo > posted a notice about it. > > greetings, > > dominik > > Am

Hello, Dovecot keeps crashing at login time. Things were fine on 2.2.2 Fatal: master: service(imap): child 5014 killed with signal 11 Here is the trace: Core was generated by `imap'. Program terminated with signal 11, Segmentation fault. #0 0x00000000105cdfdf in mailbox_list_get_storage (list=0x7fffffffe310, vname=0x10a04ab0 "INBOX/spam", storage_r=0x7fffffffe308) at

> On July 18, 2017 at 5:31 PM Thomas Leuxner <tlx at leuxner.net> wrote: > > > #0 0x00007f497ecdb067 in __GI_raise (sig=sig at entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 > resultvar = 0 > pid = 10092 > selftid = 10092 > #1 0x00007f497ecdc448 in __GI_abort () at abort.c:89 > save_stage = 2 > act =

Core was generated by `dovecot/pop3'. Program terminated with signal 11, Segmentation fault. #0 0x0804eb6a in client_update_mails (client=client at entry=0x8afd7a8) at pop3-commands.c:256 256 seq_range_array_add(&deleted_msgs, client->msgnum_to_seq_map[msgnum]); #0 0x0804eb6a in client_update_mails (client=client at entry=0x8afd7a8) at pop3-commands.c:256

Hi, I got all excited about IMAP NOTIFY support and tried enabling mailbox_list_index on my server. Unfortunately, I rather quickly ran into trouble of the segfault variety. This prevented me from doing basic things like seeing the contents of some of my folders. Disabling mailbox_list_index got me back up and running, but... darnit, that's annoying. The only message I got in my log file

Hi, Dec 5 20:24:31 dovecot: imap(xx at yy.zz,7ckWZu1CuZFVTILa): Fatal: master: service(imap): child 7292 killed with signal 6 (core dumped) Dec 5 20:24:32 dovecot: imap(xx at yy.zz,LnAlZu1COBVVTILa): Panic: file mail-index-map.c: line 549 (mail_index_map_lookup_seq_range): assertion failed: (first_uid > 0) Dec 5 20:24:32 dovecot: imap(xx at yy.zz,LnAlZu1COBVVTILa): Error: Raw backtrace:

27.08.2015, 16:09, "Eugene Paskevich" <eugene at raptor.kiev.ua>: > Hello, > > I'm using the Debian builds of dovecot-2.2 by S[r]us. > Today I started getting the following panic: > > log: Panic: file priorityq.c: line 122 (priorityq_remove_idx): assertion > failed: (idx < count) Just in case, here is the full backtrace. (gdb) thread apply all bt full

Hi, today I upgraded to version 2.2.12 under Debian Squeeze. I saw some people on the list they had the same problems with version 2.2.11, but which should have been fixed in version 2.2.12. My logfile shows: .. Mar 28 08:25:01 mailstore dovecot: pop3-login: Login: user=<ul at domain.net>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=34568, secured, session=<Jp6RmaX1YAB/AAAB>

Hi All, I have my dovecot/imap crashing on my Centos7 server. Below is the stacktrace I got: #0? 0x00007f32d9b84e58 in array_count_i (array=0x55b332a1f8f8) at array.h:155? ? ? ? ? ? ? ? ? ? ? ? ? ?No locals.? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ??#1? array_get_i (count_r=<synthetic pointer>, array=0x55b332a1f8f8) at array.h:209? ? ? ? ? ?

On 19.07.2017 09:39, Aki Tuomi wrote: > > On 19.07.2017 09:36, Thomas Leuxner wrote: >> * Aki Tuomi <aki.tuomi at dovecot.fi> 2017.07.19 08:31: >> >>> oh and any idea which one of these crashes? >> This one does: >> >> # cat Flagged/dovecot-virtual >> * >> :public/* >> -Trash >> -Trash/* >> flagged > Thanks,

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Usingt ./sbin/dovecot --version 2.2.rc2 (7a08461c5559) with Maildir, 2 FETCH 1 BODY.PEEK[ALL] dumps core, bt full is: #0 0x00007fa166e721b5 in raise () from /lib/libc.so.6 No symbol table info available. #1 0x00007fa166e74fc0 in abort () from /lib/libc.so.6 No symbol table info available. #2 0x00007fa16721ac47 in default_fatal_finish