Re: doveadm/dsync/imapc loose folder subscriptions

2016-01-15 Thread Timo Sirainen
On 01/08/2016 01:34 PM, Peer Heinlein wrote: > > As I already wrote some days ago we're actually running a huge migration > using doveadm/dsync-backup/imapc: > > doveadm -o imapc_user="$UNAME1" -o imapc_password="$PWORD1" -o > imapc_host=$SERVER1 -o pop3c_user="$UNAME1" -o

sieve - configuration problem

2016-01-15 Thread Hajo Locke
Hello List, first thanks for previous hints, you helped me a lot. Unfortunately i have new problem with sieve and executing multiple scripts sequentially. This is current conf which is complete working : #CONF1 plugin { sieve = ~/sieve/.dovecot.sieve sieve_plugins = sieve_extprograms

Re: Courier generates new UIDVALIDITY

2016-01-15 Thread Timo Sirainen
On 01/15/2016 03:34 PM, Peer Heinlein wrote: > > We just detected, that under some circumstances Courier-IMAP will > generate a new UIDVALIDITY for every access to an IMAP-folder, if the > folder had been created by a simple "mkdir" and not with maildirmake. > Courier doesn't save his

Courier generates new UIDVALIDITY

2016-01-15 Thread Peer Heinlein
We just detected, that under some circumstances Courier-IMAP will generate a new UIDVALIDITY for every access to an IMAP-folder, if the folder had been created by a simple "mkdir" and not with maildirmake. Courier doesn't save his uidvalidity-file in this case. Courier DOES generate a sticky

remote | local blocks in protocol settings

2016-01-15 Thread Nikolaos Milas
Hello, Where can I find detailed documentation on how "remote" & "local" blocks are used in protocol configuration to provide specific settings for particular IPs/Names? I've been searching around (wiki2, Google) but I found very few things. I also checked in the conf.d directory of the

Re: doveconf syntax question

2016-01-15 Thread A. Schulze
Am 05.01.2016 um 15:31 schrieb A. Schulze: I have one sieve extension enabled: /etc/dovecot/conf.d/20-sieve.conf: plugin { sieve_extensions = +vacation-seconds } now (months later) we want to enable an other extension. no big deal: /etc/dovecot/local.conf: plugin {

Re: Corrupted index cache file - migration with zlib

2016-01-15 Thread Robert L Mathews
On 1/14/16 8:51 PM, Leon Kyneur wrote: > figured out my issue > > I changed: > protocol imap { > mail_plugins = quota imap_quota imap_zlib > } > > to this: > protocol imap { > mail_plugins = $mail_plugins imap_quota imap_zlib > } > Right. This is because it needs the "zlib" plugin enabled,

Re: Increasing mail_max_userip_connections and sys resources

2016-01-15 Thread Joseph Tam
In our low-traffic server we have always kept the default value for IMAP mail_max_userip_connections (10). The server has been working fine! (Thank you Timo for this!) However, recently we have been having: Maximum number of connections from user+IP exceeded errors both for IMAP and

Re: sieve - configuration problem

2016-01-15 Thread Stephan Bosch
Op 1/15/2016 om 1:07 PM schreef Hajo Locke: > Hello List, > > first thanks for previous hints, you helped me a lot. > > Unfortunately i have new problem with sieve and executing multiple > scripts sequentially. > This is current conf which is complete working : > #CONF1 > plugin { > sieve =

Dovecot with pam authentication and user@domain

2016-01-15 Thread Christian Schneider
Hello all, I'm trying to setup dovecot for local users with pam authentication. The passdb and userdb entries are as follows: passdb { args = username_format=%n driver = pam } userdb { args = username_format=%n driver = passwd } Using "doveadm user chriss" returns the user record as

Re: Increasing mail_max_userip_connections and sys resources

2016-01-15 Thread Steffen Kaiser
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, 15 Jan 2016, Nikolaos Milas wrote: I tried adding "process_limit = 2048" to imap: protocol imap { imap_client_workarounds = "delay-newmail" mail_plugins = quota imap_quota notify replication process_limit = 2048 this

Re: Increasing mail_max_userip_connections and sys resources

2016-01-15 Thread Nikolaos Milas
On 15/1/2016 10:50 πμ, Steffen Kaiser wrote: this setting belongs to the service imap { section. Oh, this is it! It works now! Thanks, Steffen. All the best, Nick