similar to: 2.0.12 Coredump under Solaris 10

hi, Am Mittwoch, den 27.04.2011, 12:37 +0300 schrieb Timo Sirainen: > Give "bt full" command here and show the output. lot of lines :-) ============================ (gdb) bt full #0 0xfeb559f8 in strcmp () from /lib/libc.so.1 No symbol table info available. #1 0xfee73e7a in settings_find_key_nth (ctx=0x809bec0, key=0x807ab38 "plugin//imap", n=0x80477f0,

Hi, one Fedora user sees regression in dovecot 2.0.11 (compared to prev. 2.0.9). There was change recently: http://hg.dovecot.org/dovecot-2.0/diff/bc77e80947c0/src/lib-settings/settings-parser.c which adds call to settings_find_key_nth(...., &parent_def,...). This function can set parent_def to NULL, but there is no check for this situation in the code. So on next line if (parent_def->type

hi, we have 2.0.13 running and most works well, but today we had some minor problems: The IMAP login process takes sometimes to much time. Over webmail (Roundcube 0.5.0.3) login wasn't sometimes possible, the normal clients hasn't any problems, until they login. We had only ~ 20-30 active accounts, but 50-60 sessions. The most are Apple products (Ip*/Mac/. ..)because they have 4 sessions

On Wed, 2011-04-27 at 10:24 +0200, Denny Schierz wrote: > The gdb coredump shows: Almost great bug report! Just: > gdb ../../dovecot2-testinstanz/libexec/dovecot/imap /var/run/dovecot-testinstanz/core > > Core was generated by `dovecot/imap'. > Program terminated with signal 11, Segmentation fault. > #0 0xfeb559f8 in strcmp () from /lib/libc.so.1 Give "bt

Hello, When running multiple instances of dovecot on the same host (or running multiple docker container), it is hard to distinguish logs from different processes: the syslog entries are all prefixed with the same identifier "dovecot" It is hardcoded here: https://github.com/dovecot/core/blob/master/src/lib-master/master-service.c#L420 Would it make sense to use the already implemented

http://dovecot.org/releases/2.0/beta/dovecot-2.0.beta1.tar.gz http://dovecot.org/releases/2.0/beta/dovecot-2.0.beta1.tar.gz.sig Now that v2.0 is in beta stage I don't expect anything big to change anymore. The configuration and the APIs shouldn't change in non-backwards compatible ways. There are still bugs left to be fixed and some small features to be implemented, but I'd like to

http://dovecot.org/releases/2.0/beta/dovecot-2.0.beta1.tar.gz http://dovecot.org/releases/2.0/beta/dovecot-2.0.beta1.tar.gz.sig Now that v2.0 is in beta stage I don't expect anything big to change anymore. The configuration and the APIs shouldn't change in non-backwards compatible ways. There are still bugs left to be fixed and some small features to be implemented, but I'd like to

Hello all, I am working on a app right now that is going to replace a paper form process out client has. This process has quite a few forms (about 30) and different groups of forms (section) need to be filled out based on what information is required from the user. For example, here is a possible process of 2 users: user 1 user 2 Section 1 Section 1 Section 2 Section 2

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

Sharing an installed copy of dovecot between several users each running a daemon within their own account (or using the same binaries for a system daemon and a user daemon) is difficult because the compile-time directory PKG_STATEDIR (typically /var/lib/dovecot) is hard-coded as the location of things like the ssl-parameters.dat file and the replicator database. Replace all these uses of

Hi! On Thu, 31 May 2018 00:44:58 +0900, A. Schulze wrote: > When running multiple instances of dovecot on the same host (or running multiple docker container), > it is hard to distinguish logs from different processes: the syslog entries are all prefixed with the same identifier "dovecot" > It is hardcoded here: >

The openssl library in Debian unstable (targeting Buster) supports TLS1.2 by default. The library itself supports also TLS1.1 and TLS1.0. If the admin decides to also support TLS1.[01] users he can then enable the lower protocol version in case the users can't update their system. Signed-off-by: Sebastian Andrzej Siewior <sebastian at breakpoint.cc> --- src/config/all-settings.c

On Wed, 2011-04-27 at 12:19 +0200, Denny Schierz wrote: > #7 0xfee74322 in settings_parse_line (ctx=0x809bec0, line=0x807aa98 > "plugin//imap/spool/%d/%1n/%n=/home/testds") at settings-parser.c:869 That's an interesting setting you have there.. I tried to reproduce but I can't seem to make it crash with it. What's in your dovecot-ldap.conf.ext? (This user was looked