similar to: doveconf complains No matches on !include conf.d/* line but still writes out contents in conf.d

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

Hi, # dovecot --version 2.3.3 (dcead646b) # doveinfo Nombre d'utilisateurs : 1151 Sockets IMAP : 4356 Process dovecot/imap : 4357 Process dovecot/imap-login : 1339 Process dovecot/pop3 : 0 Process dovecot/pop3-login : 0 Process dovecot/auth : 1 Process dovecot/auth -w : 2 Process dovecot/anvil : 1 Process

> > On 16.10.2018 21.32, J. de Meijer wrote: >> I'm still trying to fix this problem. Hopefully someone can help. >> >> I've upgraded dovecot to 2.3.3 >> # dovecot --version >> 2.3.3 (dcead646b) >> >> That didn't help. >> >> Next I switched 10-auth.conf to use a local password file (instead of >> LDAP) > > Can you

On 18.10.2018 21.24, J. de Meijer wrote: >> On 16.10.2018 21.32, J. de Meijer wrote: >>> I'm still trying to fix this problem. Hopefully someone can help. >>> >>> I've upgraded dovecot to 2.3.3 >>> # dovecot --version >>> 2.3.3 (dcead646b) >>> >>> That didn't help. >>> >>> Next I switched

Hi all, To backup our imap folders I've a cronjob running in the night: /usr/bin/doveadm -o stats_writer_socket_path= backup -R -A -N tcp:xxx.yyy.zzz:4191 This ran successful when I set it up and didn't look at it anymore. Recently I noticed errors: dsync-local(administration)<uO/qHjXS6FteLAAA3i05xw>: Panic: file dsync-mailbox-tree-sync.c: line 1253 (sync_create_mailboxes):

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 all, I'm trying to setup a Dovecot proxy that authenticates the user against two backend servers. If login server1 fails, server2 should be tried. The problem: Only the first server seems to be tried, even if the login fails. Config snippet: protocol imap { passdb { driver = static args = proxy=y nopassword=y host=oldserver1.example.com port=993 ssl=y }

Hello, I'm also running FreeBSD 11.1, Dovecot 2.3, and Pidgeonhole 0.5, I am not getting the error you are noticing. I also do have a symlinked /var/run/dovecot/dovecot.conf which goes to /usr/local/etc/dovecot/dovecot.conf. Can you send a complete doveconf -n and your dovecot startup lines in /etc/rc.conf? Thanks. Dave. On 4/10/18, Jerry <jerry at seibercom.net> wrote: > FreeBSD

Am 30.10.18 um 13:37 schrieb Stephan Bosch: > > > Op 28-10-2018 om 23:28 schreef Peter Nabbefeld: >> Hello, >> >> cannot fetch mails from an IMAP folder because of the error in the >> subject - fetching always stops with SIGABRT. >> >> Could anybody help me, please? > > We need more information than that: > > - Your configuration and

The 'noreplicate' user database field described in the wiki appears to make no difference as to whether an account gets replicated or not. My sql user query returns a 'noreplicate' field and I can confirm that this is getting set using 'doveadm user', however when I add a new account with noreplicate=true it gets replicated regardless. User query: user_query = SELECT

pam(foobar at example.com,192.0.1.1,<9zMTUUCGNfHZzMpL>): unknown user (SHA1 of given password: ff75068c2f4d700a49dae204d56477a5ffa5d23d) The password is correct, i.e. 'echo -n 'passed' | openssl dgst -sha1' matches. The user is setup correctly in /etc/dovecot/users (the /etc/dovecot/users was copied from another known-good server, so the syntax is correct and appropriate

dear dovecot users, trying to setup this quota-status thingy in dovecot so postfix can query the quota on the mailbox via following in main.cf smtpd_recipient_restrictions = ??? ... ??? check_policy_service inet:127.0.0.1:12340 I got this in my dovecot config service quota-status { ? client_limit = 1 ? executable = quota-status -p postfix ? inet_listener { ??? port = 12340 ? } }

<!doctype html> <html> <head> <meta charset="UTF-8"> </head> <body> <div> PAM is trying to lookup user@domain while you probably only have user. PAM driver does not yet support username_format. </div> <div> <br> </div> <div> Aki </div> <blockquote type="cite">

Hi, After updating some of our director servers from 2.2.36 to 2.3.3 (dcead646b) we experience crashes in about 1/5000 mails in lmtp delivery: Nov 13 12:23:36 Fatal: lmtp(113620): master: service(lmtp): child 113620 killed with signal 6 (core dumped) Nov 13 12:23:36 Panic: lmtp(113623): file ostream-dot.c: line 208 (o_stream_dot_sendv): assertion failed: ((size_t)ret == sent + added) Nov 13

On 16.10.2018 21.32, J. de Meijer wrote: > I'm still trying to fix this problem. Hopefully someone can help. > > I've upgraded dovecot to 2.3.3 > # dovecot --version > 2.3.3 (dcead646b) > > That didn't help. > > Next I switched 10-auth.conf to use a local password file (instead of LDAP) Can you provide doveconf -n please? Aki

it's not very helpful when the process exists without any output [root at srv-rhsoft:~]$ /usr/sbin/smbd -D [root at srv-rhsoft:~]$ /usr/sbin/smbd --foreground [root at srv-rhsoft:~]$ ps aux | grep smb root 8877 0.0 0.0 10904 960 pts/1 S<+ 15:04 0:00 /usr/bin/grep --color smb [root at srv-rhsoft:~]$ rpm -qa | grep samba samba-libs-4.7.4-2.fc27.x86_64

> On 26 December 2018 at 11:26 Daniel Miller via dovecot <dovecot at dovecot.org> wrote: > > > Ubuntu 18.04, AMD Opteron, Dovecot Version 2.3.3, local file storage.? I > believe it's one of my users checking mail remotely via mobile - don't > remember if it's an iPhone or Android. > > gdb backtrace: > Reading symbols from

Hi! Thank you for the report, few points though: ?- The link you provided is broken ?- getting glibc-2.28 prebuilt seems to be bit problematic, and what I read from their changelog, the crypt function should work as normal. That said, it would be somewhat helpful if you could use gdb to find out what was passed to crypt p sample[i].key p sample[i].salt the return value is, for some reason, an

Hi, Dovecot 2.3 (release and current -git) versions compile, but fail to run when compiled against glibc-2.28. This is what is logged on startup: Aug 8 08:24:39 thunderstorm.reub.net dovecot[569]: master: Dovecot v2.3.2.1 (0719df592) starting up for imap, lmtp, sieve, submission, sieve Aug 8 08:24:39 thunderstorm.reub.net dovecot[569]: master: Error: service(auth): command startup failed,

Hi, The link to the release notes seems should have an 'l' on the end: Try: https://www.sourceware.org/ml/libc-alpha/2018-08/msg00003.html This with gdb: thunderstorm /usr/src/dovecot/dovecot-2.3/src/auth # gdb /root/dovecot-auth-crash/auth /root/dovecot-auth-crash/core.auth.29667 GNU gdb (Gentoo 8.1.1 p1) 8.1.1 Copyright (C) 2018 Free Software Foundation, Inc. License GPLv3+: GNU