similar to: Failure in doveconf

Hi, It would be nice if the recipient_delimiter configuration option supported multiple recipient delimiters as Postfix now does. e.g. now if I set: recipient_delimiter = +- in Postfix, then test-extension at sample.com and test+extension at sample.com are both recognized. But if I set: recipient_delimiter = +- in Dovecot, neither of the above are recognized and instead test+-extension at

On Tue, 10 Apr 2018 11:08:20 -0400, David Mehler stated: >Can you send a complete doveconf -n and your dovecot startup lines in >/etc/rc.conf? /etc/rc.conf ## Dovecot dovecot_enable="YES" # 2.3.1 (8e2f634): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.5.1 (d9bc6dfe) # OS: FreeBSD 11.1-RELEASE-p9 amd64 zfs # Hostname: localhost auth_mechanisms = plain login

After upgrading my IMAP server to the new debian stable, and upgrading dovecot from 1.x to 2.1.7 in the process, dovecot no longer logs anything to /var/log/mail.*. The last entries there are from before the upgrade, and no starts or error messages or failed login attempts, since then, have been logged. Does anyone know what might cause this? "doveconf -n" doesn't mention any of

Hi, It happens when I try to convert this config (with the dovecot 2.0 beta4 release) : test-mail:/tmp# dovecot -n -c ./dovecot.old.conf # 1.2.11: ./dovecot.old.conf # OS: Linux 2.6.26-2-686-bigmem i686 Debian 5.0.4 log_path: /var/log/dovecot.log info_log_path: /var/log/dovecot_info.log protocols: imap listen: 127.0.0.1:30143 disable_plaintext_auth: no login_dir: /var/run/dovecot/login

FreeBSD 11.1-RELEASE-p9 amd64 doveconf # 2.3.1 (8e2f634): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.5.1 (d9bc6dfe) # OS: FreeBSD 11.1-RELEASE-p9 amd64 zfs # Hostname: localhost I can send the entire output if necessary. Error message upon boot up: doveconf: error: t_readlink(/var/run/dovecot/dovecot.conf) failed: readlink() failed: No such file or directory Starting dovecot.

Hi! First of all, can you provide output of 'doveconf -n'? It's much cleaner to read and shows what's really there? Aki On 22.1.2019 17.57, Ted wrote: > Hello, > > We're having difficulty with our updated cluster of dovecot servers > accessing the email storage on the NFS mounts.? It seems index files get > corrupted when 2 backend mailservers access the same

Rick et al, The link you gave was a start, but is targeted for Samba3 and is assuming a probably Windows [SBS]Server AD/DC separate from the DC hosting dovecot, and includes setting up kerberos. I'm using a Samba4 AD/DC with integrated kerberos (so I don't think there is any setup I can do there). Nevertheless I've followed the instructions otherwise; specifically adding to

This can't be that hard. I think I've enabled LDAP in Dovecot just by including dovecot-ldap.conf.ext in 10-auth.conf and using the default settings. I now have the configuration shown below. Two questions: 1. How do I set Outlook to authenticate with LDAP? Currently the Outlook accounts still have the ID and password set in "Logon Information". Checking "Require logon

Hello, I have encountered with strange issue. When I uncomment the following line auth_verbose_passwords = yes in the /etc/dovecot/conf.d/10-logging.conf I get the following errors # dovecot -a # 2.2.10: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-431.3.1.el6.x86_64 x86_64 CentOS release 6.5 (Final) ext4 # NOTE: Send doveconf -n output instead when asking for help. Segmentation fault (core

Hmm.? I would expect to see 'mark at hprs.com'.? Whatever your full domain name is. It also won't look up /etc/shadow - Samba is doing the AD->Unix UID mapping.? Your AD users shouldn't be in there when all is said and done.? Well, at when I did a Samba4 install as a DC it still behaved like a Samba3 member, and there were no AD users in the local unix passwd files. What does

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:

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

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 anyone can provide information on suspicious

Citeren jimc <jimc at jfcarter.net>: > Distro: OpenSuSE Tumbleweed for x86_64 > Failing version: dovecot23-2.3.11.3-1.1.x86_64 Install Date: 2020-08-18 > Reverting to previous version works: 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

More experimentation ... I tried removing userdb and passdb from the dovecot NTLM config. That didn't work. I then tried adding a static userdb as follows: userdb { driver = static # allow_all_users = yes args = gid=100 home=/home/HPRS/%n } (Interestingly, when I uncommented "allow_all_users" I got an "unsupported setting" [or something like that], even though that

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, attached patch tries to hide any setting that ends in _password (singular) in the output of doveconf by default. doveconf -n - -> passwords replaced by "<hidden>" to prevent information leak when submitting bug reports doveconf -n -P - -> passwords visible when used by admins locally doveconf -n -P -P - -> setting

Another interesting thing, noticed now: before the segfault error I have always this log: Jul 3 11:50:26 mail dovecot: config: Error: managesieve-login: dump-capability process killed with signal 11 Jul 3 11:50:26 mail kernel: [1514971.045499] doveconf[23971]: segfault at 55d0fd61c000 ip 00007f3f7cc242d0 sp 00007ffcb29341b8 error 6 in libc-2.23.so[7f3f7cb95000+1c0000] But I have no idea of

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

Hi Timo, If I could tell you a little smart wish, I've one for you. ;) Today I'm writing my own configurationdocumentation 'bout Dovecot in my dokuwiki and for documentation purposes I changing some options several times a day. Postfix supports on its own postconf an option -e. So I can set up mostly every configuration-option on the fly. Dovecot's doveconf has no such option.

Sorry for the noise, local.conf wasn't readable by a normal user, so it wasn't tried (!include vs !include_try) Marc Marc Weustink wrote: > 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. > > >