similar to: Upgrade to v2.0 conf file fails

Am 20.07.2012 01:25, schrieb Edward Cavill: > Hi in the wiki, using 64 without the trailing 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:

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

http://dovecot.org/releases/2.0/dovecot-2.0.16.tar.gz http://dovecot.org/releases/2.0/dovecot-2.0.16.tar.gz.sig I only now noticed that the VSZ limits weren't being enforced with earlier v2.0.x releases (or they were set 1024 times too high). So if a Dovecot process was leaking memory, it wasn't being killed by kernel. Now that this enforcing is done, some installations will probably

http://dovecot.org/releases/2.0/dovecot-2.0.16.tar.gz http://dovecot.org/releases/2.0/dovecot-2.0.16.tar.gz.sig I only now noticed that the VSZ limits weren't being enforced with earlier v2.0.x releases (or they were set 1024 times too high). So if a Dovecot process was leaking memory, it wasn't being killed by kernel. Now that this enforcing is done, some installations will probably

I just upgraded my Dovecot IMAP package on my mail server and when I restarted the service, I got the following warnings... doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:12: add auth_ prefix to all settings inside auth {} and remove the auth {} section completely doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:14: passdb pam {} has been replaced by passdb {

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

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

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:

Hello, as described in [253363], login_process_size of 32M is not enough on 64-bit versions of Fedora and RHEL (and possibly other distributions as well). [253363] https://bugzilla.redhat.com/show_bug.cgi?id=253363 As I understand it, there's an intersegment gap between read-only/executable and writable segments of shared libs. That's probably a security feature or something. I found a

Hi, I'm new to Dovecot. I'm trying to start Dovecot(2.0.9) but I'm getting an error. I think the error is because I'm doing a tutorial for an old version of Devcot(1.x.x). What I get is the following: [code] [root at mailserver dovecot]# service dovecot start Starting Dovecot Imap: doveconf: Warning: NOTE: You can get a new clean config file with: doveconf -n >

Hi; [root at example jack]# /usr/local/sbin/dovecot --version 2.0.15 [root at example jack]# /usr/local/bin/doveconf -n # 2.0.15: /usr/local/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 /usr/local/etc/dovecot/dovecot.conf:5: imap_client_workarounds=outlook-idle is no longer

Any suggestions on sizing login_process_size and login_processes_count for a server expected to be doing 100 to 200 simultaneous connections? Is there a way to separate login_processes_count between imap and pop? I would like to have at least 50 imap processes ready, but we rarely have any more than 5 to 10 pop connections. Would be a shame to have 40+ pop login processes doing nothing most

boah how i hate that "reply all" attitude leading to break "reply to list" and leads in off-list replies -------- Original-Nachricht -------- Betreff: Re: [Dovecot] Dovecot not honoring configuration settings (auth failure) Datum: Tue, 01 Apr 2014 00:02:42 +0200 Von: Reindl Harald <h.reindl at thelounge.net> Organisation: the lounge interactive design An: noloader at

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:

http://dovecot.org/releases/2.0/beta/dovecot-2.0.beta4.tar.gz http://dovecot.org/releases/2.0/beta/dovecot-2.0.beta4.tar.gz.sig I think this release is finally feature complete. There are still some bugs left to be fixed, but it's mainly in the dsync/mdbox area. v2.0.rc1 should hopefully be out in a couple of weeks. After that v2.0.0 will be released after no serious bugs have been found for

http://dovecot.org/releases/2.0/beta/dovecot-2.0.beta4.tar.gz http://dovecot.org/releases/2.0/beta/dovecot-2.0.beta4.tar.gz.sig I think this release is finally feature complete. There are still some bugs left to be fixed, but it's mainly in the dsync/mdbox area. v2.0.rc1 should hopefully be out in a couple of weeks. After that v2.0.0 will be released after no serious bugs have been found for

Hi Timo, I've just tried to convert my v1.2 configuration to a v2.0 configuration. Below a few obsolete warnings, among others "mail_executable has been replaced by service { executable }", was an interesting error: "doveconf: Error: duplicate listener: 198:" The broken parts of the converted configuration: # 2.0.beta4 (84ffb38839b9): /etc/dovecot/dovecot.conf # OS: Linux

I have a few systems which run dovecot 1.x as the authentication backend for Postfix, with multiple auth { } sections like this one, each one with a different passdb and its own socket: auth ldap-10 { passdb ldap { args = /etc/dovecot/dovecot-ldap-10.conf } socket listen { client { path = /var/spool/postfix/private/auth-10 mode = 0666 } } } I need multiple

Our imap/pop service is moving from UW imap to dovecot 0.99.11 on RHEL4. This is for around 200 users with lots of different email clients, e.g.: Windows: outlook, outlook Express, eudora, thunderbird, netscape OS X: mail, eudora, thunderbird Unix/Linux: evolution, thunderbird, pine, mutt Web: squirrelmail Apart from the example configuration file, I can't find

Hi, I have a mailserver(Postfix+MySql) on OpenBSD 4.9 with Dovecot 1.2.16, all works fine. Now i want to do the same but on OpenBSD 5.0. I meet problems using dovecot 2.0.13 on OpenBSD 5.0. Some tests (on the box): telnet 127.0.0.1 110 Trying 127.0.0.1... Connected to 127.0.0.1. Escape character is '^]'. Connection closed by foreign host. telnet 127.0.0.1 143 Trying 127.0.0.1...