search for: doveconf

...sql args: /etc/dovecot/dovecot-sql-master.conf pass: yes master: yes passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: sql args: /etc/dovecot/dovecot-sql.conf plugin: quota: maildir:User quota test-mail:/tmp# /usr/local/dovecot2/bin/doveconf -n -c ./ dovecot.old.conf # 2.0.beta4 (6891d20929ca): ./dovecot.old.conf doveconf: Warning: Obsolete setting in ./dovecot.old.conf:26: login_dir has been removed doveconf: Warning: Obsolete setting in ./dovecot.old.conf:29: login_chroot has been replaced by service { chroot } doveconf: Fatal:...

Sorry if I missed the dovecot 2.0.betax managesieve sieve discussions. I have been looking in my list archive and haven't found a reference to this yet. I am trying to convert my dovecot.conf and am getting the following Fatal error: /** doveconf -n -c dovecot/dovecot.conf > dovecot.converted/dovecot.conf doveconf: Warning: Obsolete setting in dovecot/dovecot.conf:10: protocols=managesieve has been renamed to protocols=sieve doveconf: Warning: Obsolete setting in dovecot/dovecot.conf:10: protocols=imaps is no longer necessary, remove...

Hi, I am trying to use the command: doveconf -n -c dovecot-1.conf > dovecot-2.conf to upgrade my dovecot.conf file, but it fails (see below). Judging from the message that vsz_limit is the new setting for login_process_size, I have retried using login_process_size=256 rather than login_process_size=64 (which was the initial value), but...

Hi; I keep getting errors like this one: Oct 22 16:51:08 example postfix/pipe[12021]: C2F705790169: to=<soandso at yup.com>, relay=dovecot, delay=2.1, delays=2/0.01/0/0.08, dsn=4.3.0, status=deferred (temporary failure. Command output: doveconf: Warning: NOTE: You can get a new clean config file with: doveconf -n > dovecot-new.conf doveconf: Warning: Obsolete setting in /usr/local/etc/dovecot/dovecot.conf:5: imap_client_workarounds=outlook-idle is no longer necessary doveconf: Warning: Obsolete setting in /usr/local/etc/dovecot/dovecot...

...g M gives an error. > > <code> > The dovecot configuration file is located at /etc/dovecot.conf. The > following lines should be added, edited or uncommented: > > login_process_size = 64 > > [root at localhost etc]# /etc/init.d/dovecot start > Starting Dovecot Imap: doveconf: Warning: NOTE: You can get a new clean > config file with: doveconf -n > dovecot-new.conf > doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:21: > protocols=imaps is no longer necessary, remove it > doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:21:...

Further investigation shows that `doveconf` called `/usr/lib/dovecot/managesieve` which in return calls `doveconf` again, but with another uid (possible? I'm not sure) and a few extra arguments, which causes a call to `glob` in `src/config/config-parser.c:settings_include` to fail with `GLOB_NOMATCH`. I'd be appreciate if anyon...

...Do not know if it was working on 2.2.23-2.2.27, skipped this versions. Example: namespace inbox { mailbox "&BB4EQgQ,BEAEMAQyBDsENQQ9BD0ESwQ1-" { special_use = \Sent } } Error: # dovecot -n # 2.2.29.1 (e0b76e3): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.18 (29cc74d) doveconf: Panic: file config-parser.c: line 89 (config_add_type): assertion failed: (ret > 0) doveconf: Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0x9b89a) [0x7fa1f8cc789a] -> /usr/lib64/dovecot/libdovecot.so.0(default_fatal_handler+0x32) [0x7fa1f8cc81d2] -> /usr/lib64/dovecot/libdov...

Migrated a 1.0.2 server to 2.0.16 (same old box). IMAP seems working Ok. POP3 give problems with some clients (Outlook 2010 and Thunderbird reported). Seems authentication problem Below my doveconf -n (debug enbled, but no answer found to the problems) Any hints? Thanks, P. # doveconf -n # 2.0.16: /etc/dovecot/dovecot.conf doveconf: Warning: NOTE: You can get a new clean config file with: doveconf -n > dovecot-new.conf doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf...

Hello, I just migrated to 2.0.2 and see some <xx at localhost.redirectme.net> (expanded from<xx at localhost>): Command died with signal 6: "/usr/local/libexec/dovecot/dovecot-lda -c /etc/dovecot2.conf". Command output: doveconf: Panic: file settings-parser.c: line 1838 (settings_copy_deflist_unique): assertion failed: (dest_count == ccount) doveconf: Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0 [0x9395c0] -> /usr/local/lib/dovecot/libdovecot.so.0(default_fatal_handler+0x45) [0x9...

I'm on dovecot 2.3.3 (dcead646b). Output of `dovecot -n`: # 2.3.3 (dcead646b): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.3 (f018bbab) doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 98: No matches doveconf: Error: managesieve-login: dump-capability process returned 89 doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 98: No matches While line 98 of dovecot.conf is just "!includ...

Hi, Today I was testing the last dovecot release 2.3 from the dovecot repo on ubuntu 16.04. (I upgraded from 2.2.23) I cannot recall if I noticed it before, but doveconf -n not showing all changes. To be able to track my changes, I don't touch the config files provided in conf.d/ anymore, but I write them in local.conf (I did in the past so doveconf -n still shows something) I was testing the new submission service so I added to local.conf: protocols =...

Hello! I want to upgrade the docevot-installation from v 1.0.5 to 2.1..7 Now I get the following executing doveconf -n -c /etc/dovecot/dovecot.conf > /home/mail1/dovecot-2.conf doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:217: add auth_ prefix to all settings inside auth {} and remove the auth {} section completely doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:219: pass...

...>> On 18 Oct 2017, at 6.34, Reuben Farrelly <reuben-dovecot at reub.net> >>>>> wrote: >> This problem below is still present in 2.3 -git, as of version 2.3.devel >> (6fc40674e) >> >>>>> Secondly, this ssl_dh messages is always printed from doveconf: >>>>> >>>>> doveconf: Warning: please set ssl_dh=</etc/dovecot/dh.pem >>>>> doveconf: Warning: You can generate it with: dd >>>>> if=/var/lib/dovecot/ssl-parameters.dat bs=1 skip=88 | openssl dh >>>>> -inform der > /e...

Hi, I have some problems of segfault at doveconf: Jul 2 08:13:16 mail kernel: [1415540.297823] doveconf[7103]: segfault at 560cb801e000 ip 00007f861da742d0 sp 00007ffe2d671548 error 6 in libc-2.23.so[7f861d9e5000+1c0000] Jul 2 15:45:38 mail kernel: [1442682.919193] doveconf[11915]: segfault at 563b32420000 ip 00007fcb127ae2d0 sp 00007ffecfc7...

...rks: dovecot23-2.3.10.1-2.3.x86_64 (Packages downgraded coordinately: dovecot23 dovecot23-backend-sqlite) How to make it fail: As the user, execute doveadm expunge mailbox Spam37 savedbefore 3day #User's actual cmd doveadm who #The simplest possible command, for testing It says: doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/10-ssl.conf line 12: ssl_cert: Can't open file /etc/ssl/hostcerts/hostw.cia: Permission denied The actual EPERM occurs trying to traverse a directory in /etc/letsencrypt, but the next configuration item to be read (in the SSL s...

...017 11:40 PM, Timo Sirainen wrote: >>> On 18 Oct 2017, at 6.34, Reuben Farrelly <reuben-dovecot at reub.net> >>> wrote: This problem below is still present in 2.3 -git, as of version 2.3.devel (6fc40674e) >>> Secondly, this ssl_dh messages is always printed from doveconf: >>> >>> doveconf: Warning: please set ssl_dh=</etc/dovecot/dh.pem >>> doveconf: Warning: You can generate it with: dd >>> if=/var/lib/dovecot/ssl-parameters.dat bs=1 skip=88 | openssl dh >>> -inform der > /etc/dovecot/dh.pem >>> >&gt...

Still broken, but I committed the current changes to http://hg.dovecot.org/dovecot-config-rewrite/ The idea is something like: - src/config/ contains a doveconf binary which can be used to dump the current configuration. It's the only binary that reads dovecot.conf directly. Currently the code is kind of ugly because I wanted it to be able to parse the existing v1.2 dovecot.conf which required some kludging around. Perhaps in v2.0 the dovecot.conf coul...

# doveconf -a # 2.2.13: /etc/dovecot/dovecot.conf doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/10-ssl.conf line 6: Unknown setting: ssl doveconf: Error: managesieve-login: dump-capability process returned 89 doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/10-master.conf l...

...n 'ssl = yes' and nothing else? does it work after this? leave the default_vsz_limit off for now. Aki On 05.06.2017 10:34, Aki Tuomi wrote: > Can you remove the offending settings, and then send it? > > Aki > > > On 05.06.2017 10:30, Sophie Loewenthal wrote: >> # doveconf -a >> # 2.2.13: /etc/dovecot/dovecot.conf >> doveconf: Fatal: Error in configuration file >> /etc/dovecot/conf.d/10-ssl.conf line 6: Unknown setting: ssl >> doveconf: Error: managesieve-login: dump-capability process returned 89 >> doveconf: Fatal: Error in configurat...

...t;> >> > > This error, I know, is too newbie and stupid, but I >> >> > > checked more than twice. >> >> > > >> >> > > root at server:/usr/local/etc/dovecot # sievec >/home3/virtual/default.sieve >> >> > > doveconf: Fatal: Error in configuration file >> >> > > /usr/local/etc/dovecot/conf.d/10-ssl.conf line 7: Unknown >setting: ssl >> >> > > root at server:/usr/local/etc/dovecot # >> >> > > >> >> > > I'm running a FreeBSD 12-cur...