similar to: http://wiki.centos.org/HowTos/postfix

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 the error persists. Please advise. Thanks, Nick

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

# 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

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:

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:

I encountered this error on FreeBSD 9.3 with dovecot2-2.2.13_3 Short version; vsz_limit is 18,447 PB and it ran out of RAM. Suggestions for change? Sep 6 03:39:32 mailjail dovecot: imap(dan): Panic: file imap-fetch.c: line 556 (imap_fetch_more): assertion failed: (ctx->client->output_cmd_lock == NULL || ctx->client->output_cmd_lock == cmd) Sep 6 03:39:32 mailjail dovecot:

Hi, I have two servers replicating mail as required, the directory structure (per user), however they will not replicate the sieve scripts directory: server 1 Maildir sieve server 2 Maildir Output of doveconf -n on server 1: # 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.4 () doveconf: Warning: NOTE: You can get a new clean config file with: doveconf -Pn >

On 12/08/2014 03:07, Teemu Huovila wrote: > A config would always be useful, but I can venture a guess. Perhaps the > affected users have a dovecot.index.cache file > somehwere, e.g. under INBOX, that is larger than the memory limit for > the lmtp process. Try increasing "default_vsz_limit" or > the "service lmtp { vsz_limit }". Removing the overly large index

Hello In my installation the disable_plaintext_auth does not appear to take effect. I can see that the value is correct using doveconf -a but it doesn't change anything. Whenever attempting to log in using IMAP I get this: * BAD [ALERT] Plaintext authentication not allowed without SSL/TLS, but your client did it anyway. If anyone was listening, the password was exposed. ls NO

Hi, I just upgraded from version 1 to version on Debian Squeeze using their backports. Like I expected my dovecot1 config had to be converted using doveconf and this I did. However, I see problems with files inside directory: drwxr-xr-x 4 dovenull root 4096 Feb 25 20:35 /var/run/dovecot All of them were created owned by root:root rw. I tried to changed, for example : chown postfix:dovecot

Dne 07.09.2020 v 12:43 Sami Ketola napsal(a): >> On 7. Sep 2020, at 12.38, Miloslav H?la <miloslav.hula at gmail.com> wrote: >> >> Hello, >> >> I sent this into the Linux Kernel Btrfs mailing list and I got reply: "RAID-1 would be preferable" (https://lore.kernel.org/linux-btrfs/7b364356-7041-7d18-bd77-f60e0e2e2112 at lechevalier.se/T/). May I ask you

Am 31. J?nner 2017 16:36:35 MEZ schrieb Kristian Pedersen <kp at asom-net.dk>: >Hi list, > >We still did not manage to get quota-status working. >We're hoping someone can provide some feedback/ideas on how we may >investigate this issue further? >Is it likely to be a bug fixed in a newer version? > >Regards, > >Kristian > > [...] >> >>

Hi, I've been running dovecot for many years, but now i've hit a strange problem. when retrieving imap there is sometimes in 1 of 4 imap requests a 4sec latency. * notes: - connected directly to the backends this latency disappears - removing a director from the loadbalancer(lvs) so i'm the only connected to the director this latency disappears too I would appreciate some feedback

Hi Folks, I am having a problem configuring imapsieve via dovecot-pidgeonhole on CentOS7. After following the docs here: https://wiki2.dovecot.org/Pigeonhole/Sieve/Plugins/IMAPSieve I get: dovecot[22026]: managesieve: Fatal: Plugin 'sieve_imapsieve' not found from directory /usr/lib64/dovecot/sieve dovecot[22026]: doveconf: Error: managesieve-login: dump-capability process returned 89

I'm using dovecot in a multi server setup. Two directors forward pop3, imap and smtp to backend dovecots with their central storage on NFS. Yesterday I stumbled upon these log lines: 2019-11-18 20:17:51 lmtp(17274): Info: Connect from 172.22.1.6 2019-11-18 20:17:51 lmtp(17274): Panic: file smtp-client-connection.c: line 1142 (smtp_client_connection_established): assertion failed:

Greetings, I'm setting up replication and am getting this error from the server where the replicated mails are being initially created: Aug 27 11:03:53 molecular dovecot: dsync-server(user at domain.org): Error: Couldn't create lock /vmail/domain.org/user/home/.dovecot-sync.lock: No such file or directory Can anyone shed some light on this? Here's the Replicator config of the

I have two servers pointing to an NFS mounted mail spool with dovecot.? Since I recently switched from using Dovecot v1.X, I have been experiencing high CPU use with the two Dovecot servers. I am not certain why they are not well behaved.? Here is the configuration information. This configuration is currently running at a load average of 17. /usr/sbin/dovecot -n # 2.1.15:

Hi, I am using Dovecot 2.2.32 (dfbe293d4) I noticed lots of messages like: dovecot: master: Warning: Sent SIGKILL to 100 imap-login processes in /var/log/maillog I commented out "process_limit" service imap { # Most of the memory goes to mmap()ing files. You may need to increase this # limit if you have huge mailboxes. #vsz_limit = $default_vsz_limit # Max. number of IMAP

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