search for: setting_define

...559f8 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, def_r=0x80477f4, link_r=0x80477f8) at settings-parser.c:699 parent_n = 1 parent_def = (const struct setting_define *) 0x0 parent_link = (struct setting_link *) 0x809bf40 def = (const struct setting_define *) 0x7ffffffb link = (struct setting_link *) 0x807ab48 parent_key = 0x807ab48 "plugin/" i = 134720328 __FUNCTION__ = "settings_find_key_nth"...

hi, I've installed a testversion from 2.0.12 and getting coredumps after login via IMAP/POP3. I don't know, if it is a simple config error or something else. ====== dovecot: [ID 583609 local7.error] master: Error: service(imap): child 29333 killed with signal 11 (core dumped) [ID 583609 local7.error] master: Error: service(imap): child 29335 killed with signal 11 (core dumped) ======

...dir, "/"MOUNTPOINT_LIST_FNAME, NULL); return mountpoint_list_init(perm_path, state_path); diff --git a/src/doveadm/doveadm-settings.c b/src/doveadm/doveadm-settings.c --- a/src/doveadm/doveadm-settings.c +++ b/src/doveadm/doveadm-settings.c @@ -53,6 +53,7 @@ static const struct setting_define doveadm_setting_defines[] = { DEF(SET_STR, base_dir), + DEF(SET_STR, state_dir), DEF(SET_STR, mail_plugins), DEF(SET_STR, mail_plugin_dir), DEF(SET_STR, doveadm_socket_path), @@ -70,6 +71,7 @@ const struct doveadm_settings doveadm_default_settings = { .base_dir = PKG_RUNDIR, + .state_d...

...vice-settings.c b/src/lib-master/master-service-settings.c index 30ad936..67fca19 100644 --- a/src/lib-master/master-service-settings.c +++ b/src/lib-master/master-service-settings.c @@ -36,6 +36,7 @@ master_service_settings_check(void *_set, pool_t pool, const char **error_r); static const struct setting_define master_service_setting_defines[] = { DEF(SET_STR, base_dir), DEF(SET_STR, state_dir), + DEF(SET_STR, instance_name), DEF(SET_STR, log_path), DEF(SET_STR, info_log_path), DEF(SET_STR, debug_log_path), @@ -52,6 +53,7 @@ static const struct setting_define master_service_setting_defines[] = {...

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

...ash: Program received signal SIGSEGV, Segmentation fault. settings_find_key_nth (ctx=0x99e4050, key=0x99c4330 "plugin//etc", n=0xbff9bdac, def_r=0xbff9bda8, link_r=0xbff9bda4) at settings-parser.c:696 696 if (parent_def->type != SET_STRLIST) (gdb) p parent_def $1 = (const struct setting_define *) 0x0 (gdb) bt #0 settings_find_key_nth (ctx=0x99e4050, key=0x99c4330 "plugin//etc", n=0xbff9bdac, def_r=0xbff9bda8, link_r=0xbff9bda4) at settings-parser.c:696 #1 0x004f9ce5 in settings_find_key_nth (ctx=0x99e4050, key=0x99c4318 "plugin//etc/dovecot", n=0xbff9be1c,...

...e_field; const char *ssl_crypto_device; const char *ssl_options; + const char *ssl_lowest_version; bool ssl_verify_client_cert; bool ssl_require_crl; --- a/src/lib-master/master-service-ssl-settings.c +++ b/src/lib-master/master-service-ssl-settings.c @@ -26,6 +26,7 @@ static const struct setting_define maste DEF(SET_STR, ssl_protocols), DEF(SET_STR, ssl_cert_username_field), DEF(SET_STR, ssl_crypto_device), + DEF(SET_STR, ssl_lowest_version), DEF(SET_BOOL, ssl_verify_client_cert), DEF(SET_BOOL, ssl_require_crl), DEF(SET_BOOL, verbose_ssl), @@ -54,6 +55,7 @@ static const struct master_...

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