similar to: v2.1 memory usage

# 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 line 35: Invalid size: $default_vsz_limit # grep default_vsz_limit

Hi Aki, # dovecot --build-options Build options: ioloop=epoll notify=inotify ipv6 openssl io_block_size=8192 Mail storages: shared mdbox sdbox maildir mbox cydir imapc pop3c raw fail SQL driver plugins: mysql postgresql sqlite Passdb: checkpassword ldap pam passwd passwd-file shadow sql Userdb: checkpassword ldap(plugin) nss passwd prefetch passwd-file sql -- On June 5, 2017 8:59:08 AM

http://dovecot.org/releases/2.1/alpha/dovecot-2.1.alpha2.tar.gz http://dovecot.org/releases/2.1/alpha/dovecot-2.1.alpha2.tar.gz.sig This is actually looking rather stable. I'm still calling it "alpha" in case I think of doing some more API changes, but I think the next one will be called "beta1", hopefully soon followed by "rc1". - Statistics gathering

http://dovecot.org/releases/2.1/alpha/dovecot-2.1.alpha2.tar.gz http://dovecot.org/releases/2.1/alpha/dovecot-2.1.alpha2.tar.gz.sig This is actually looking rather stable. I'm still calling it "alpha" in case I think of doing some more API changes, but I think the next one will be called "beta1", hopefully soon followed by "rc1". - Statistics gathering

Can you create file /etc/dovecot/conf.d/10-ssl.conf and type in '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:

Sophie ( ?? ?? ??) > On 5 Jun 2017, at 09:42, Matthias Sitte <matthias at familie-sitte.org> wrote: > > I have the feeling that the config file is incorrect and loading > subsequent files results in reading in entries at the wrong level? > > Could you attach the full 10-master.conf? > > Matthias > > > On 06/05/2017 09:30 AM, Sophie Loewenthal wrote:

Hi Stefan, My apologies for the long delay. Been ill. I tried this and had an error, # mv /etc/dovecot/conf.d/10-ssl.conf /etc/dovecot/conf.d/10-ssl.conf.bak # cp -p /usr/share/dovecot/conf.d/10-ssl.conf /etc/dovecot/conf.d/ # /etc/init.d/dovecot restart /var/log/daemon.log Jun 4 11:05:55 mail systemd[1]: Starting Dovecot IMAP/POP3 email server... Jun 4 11:05:55 mail systemd[1]: Started

Hi, I've been trying to get dovecot2 running and kept having this error message: May 13 13:38:32 mail systemd[1]: Started Dovecot IMAP/POP3 email server. May 13 13:38:32 mail dovecot[2178]: doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/10-ssl.conf line 61: Unknown setting: ssl # dovecot --build-options Build options: ioloop=epoll notify=inotify ipv6 openssl

I did eventually was forced to do this and setup a 2 node test environment with the latest dovecot: /usr/dovecot/sbin/dovecot --version 2.2.25 (7be1766) /usr/dovecot/sbin/dovecot --build-options Build options: ioloop=epoll notify=inotify ipv6 openssl io_block_size=8192 Mail storages: shared mdbox sdbox maildir mbox cydir imapc pop3c raw fail SQL drivers: mysql Passdb:

Apparently Dovecot with kqueue ioloop enabled causes random crashes in FreeBSD 9.1. Anyone else noticed something like that? I'm wondering if Dovecot's kqueue code has a bug somewhere (I can't find it) or could it be that FreeBSD itself has a bug? Anyway it seems to be returning events for filters that have already been removed.

I think the problem still is that your keytab file has no entry imap/hostname at DOMAIN and IMAP/hostname at DOMAIN you also have no host/hostname at DOMAIN Aki On 29.06.2016 18:40, Mark Foley wrote: > Yes, I think that's exactly correct. I just made a similar reply to Edgar Pettijohn about that. > The Thunderbird message is: > > "The Kerberos/GSSAPI ticket was not accepted

Hello, I am a complete newbie to dovecot, but do have reasonable experience in compiling Unix/Linux software. I am currently trying to do a cross-compile of dovecot-2.29.1 to be used on my home office Thecus NAS (host: Thecus kernel 2.6.33 on 32-bit Intel Atom: "i686-nptl-linux-gnu"; my build machine has Ubuntu 16.04.2 LTS) "from ground up", i.e. I need to build and

I would also check where the "... is not portable!" messaage is generated. If it's done by the configure script, you can look at the test to give you a hint as to why this message was generated. For my setup, I did much the same as you but didn't have to set the SSL_CFLAGS, SSL_LIBS environment variables, nor did I set the --with-ssldir configure option (although your setup may

Hello I have 2.2.18 built with: ./configure \ --prefix="$prefix" \ --bindir="$prefix/bin" \ --sbindir="$prefix/bin" \ --sysconfdir="/etc" \ --with-storages="maildir,imapc,pop3c" \ --without-vpopmail \ --without-ldap I'm attempting to sync (backup) from another Dovecot server running version 2.0.21: Both servers

Hello, Are you sure about that I would need so recent version? That is ok to have some bugfixes but you are talking about the latest cutting edge debian jessie backports package. Even the mainline debian jessie only have 2.2.13 in it and my system is a complex wheezy installation, the last thing I want to do is to move all my components into jessie just because of this or do you know

http://dovecot.org/releases/2.1/beta/dovecot-2.1.beta1.tar.gz http://dovecot.org/releases/2.1/beta/dovecot-2.1.beta1.tar.gz.sig Here's the first beta release of Dovecot v2.1. This version has already been tested quite a lot, so I'm not expecting any major bugs. So please upgrade and see if you can find any problems. I'm optimistic about getting rc1 released this year and perhaps even

http://dovecot.org/releases/2.1/beta/dovecot-2.1.beta1.tar.gz http://dovecot.org/releases/2.1/beta/dovecot-2.1.beta1.tar.gz.sig Here's the first beta release of Dovecot v2.1. This version has already been tested quite a lot, so I'm not expecting any major bugs. So please upgrade and see if you can find any problems. I'm optimistic about getting rc1 released this year and perhaps even

Hi list, I'm trying to do a domain migration using the imapc feature, but i'm having some problems and I really don't know what is happening. So if you guys could help me with a path to solve this, I will be glad. I'm using Dovecot 2.1.7 in a Debian Wheezy machine. The command I'm using is: dsync -Dv -o imapc_features=rfc822.size -o imapc_host=IP -o imapc_port=143 -o

In https://wiki2.dovecot.org/Tools/Doveadm/Sync#section_arguments the destination list 5 possible options for the destination but in the page on migration https://wiki2.dovecot.org/Migration/Dsync it seems to use a sixth undocumented "imapc:" option for destination e.g. doveadm -o mail_fsync=never backup -R -u user at domain imapc: "imapc:" is also referenced on

Hi, I've a broken IMAP server, which doesn't support pipelining and fails on dovecot's attempt to do this ([C] is dovecot's imapc, [S] is the IMAP server): [C] 24 LOGIN "user" "pass" [S] 23 OK [C] 25 SELECT "INBOX" [C] 23 UID FETCH 2 (INTERNALDATE) [S] 25 OK [S] 23 BAD No mailbox selected Sadly, fixing the server would be a hard task, turning off