similar to: v2.0.16 released

http://dovecot.org/releases/2.1/rc/dovecot-2.1.rc1.tar.gz http://dovecot.org/releases/2.1/rc/dovecot-2.1.rc1.tar.gz.sig I'll probably release v2.1.0 pretty soon, unless people report some new bugs. I know v2.1 is already being used to serve mails to tens (or hundreds?) of thousands of users, so it should be pretty stable. Most of the changes since v2.1.beta1 have been for rather small

http://dovecot.org/releases/2.1/rc/dovecot-2.1.rc1.tar.gz http://dovecot.org/releases/2.1/rc/dovecot-2.1.rc1.tar.gz.sig I'll probably release v2.1.0 pretty soon, unless people report some new bugs. I know v2.1 is already being used to serve mails to tens (or hundreds?) of thousands of users, so it should be pretty stable. Most of the changes since v2.1.beta1 have been for rather small

Aki, is it possible to have doveconf print the current section upon error? Like, change the following error message 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 to something like May 13 13:38:32 mail dovecot[2178]: doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/10-ssl.conf line

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: /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

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: > # 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

Hi, in line 17 of your 10-master.conf you enable the "imap-login" service, but you fail to close the config section in line 36 ... :-) That results in loading 10-ssl.conf and trying to apply the "ssl" option to "imap-login" which of course doesn't apply here. Best, Matthias On 06/05/2017 09:43 AM, Sophie Loewenthal wrote: > > Sophie > ( ?? ?? ??)

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:

Hi, I upgraded from Dovecot v2.0.16 to v2.1.7 over night and I noticed this morning that one of my daily reports which lists summarised mailbox sizes per user has started listing nonsense for vsizes. The reporting script at its core calls : doveadm -f flow mailbox status -A -t 'messages vsize' '*' It appears that Dovecot 2.1.7 is not resetting the vsize after collating the sum

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:

# 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

Hello Dovecot users, Before I move active development of Pigeonhole to Dovecot v2.1, I first release all the pending bug fixes and small improvements. Changelog v0.2.5: + Sieve vacation extension: made discard message for implicit delivery more verbose - The sieve-test tool: mixed up original and final envelope recipient in implementation of command line arguments. - Sieve vacation

Hello Dovecot users, Before I move active development of Pigeonhole to Dovecot v2.1, I first release all the pending bug fixes and small improvements. Changelog v0.2.5: + Sieve vacation extension: made discard message for implicit delivery more verbose - The sieve-test tool: mixed up original and final envelope recipient in implementation of command line arguments. - Sieve vacation

Hi! Here such synchronization error: dovecot: dsync-local(alex at aaa.com): Warning: Mailbox changes caused a desync. You may want to run dsync again. dovecot: dsync-remote(alex at aaa.com): Warning: /var/mail/virtual/aaa.com/alex/.INBOX.System/dovecot-uidlist: Duplicate file entry at line 2298: 1380157263.M585262P25253.mail1.aaa.com,S=2476,W=2553 (uid 3645 -> 3662) dovecot: dsync-remote(alex

Quoting Timo Sirainen <tss at iki.fi>: > On 24 Sep 2015, at 16:26, Rick Romero <rick at havokmon.com> wrote: >> Update.? Only a single reboot has occurred since changing >> defalt_vsz_limit from 384M to 512M.? It would seem that something the >> users are doing is causing that virtual memory size to be exceeded >> (possibly a mailbox search?), and when that

Hi, Introduction: There are two domains, for example (aaa.com, bbb.com). In the aaa.com domain two users (bob at aaa.com, alex at aaa.com). In the bbb.com domain there are no users. In time full sync replication (replication_full_sync_interval) operations in logs appear errors: dovecot: dsync-local(bob at aaa.com): Error: Mailbox INBOX: Failed to set attribute

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Recently I encountered odd quota increases when using 'dsync' with the latest and greatest: 2.0.8 (89936539e3b8). Say you got something in place like this: plugin { quota = dict:user::file:%h/mdbox/dovecot-quota quota_rule = *:storage=1GB quota_rule2 = Trash:storage=+10%% } Kick off a manual backup: $ dsync -u user at domain.tld

?I meet the problem about dsync with ?expunge. The problems is expunged mail would reappear after dsyncing and it is easily to reproduce. ?Environment Settings: - Two servers(serverA, serverB) both enabled plugin "*replication"* - And more detail get by "dovecot -n" show below ?Reproduce flow: ?- ?Run two processes pA and pB both would run in while loop ?- pA?(All behavior is

Hello Dovecot users, The new Dovecot v2.0.8 release has a few changes that prompted changes in Pigeonhole as well. This means that a new release of Pigeonhole is also necessary, because otherwise things will not compile anymore. Apart from a few rather minor bugfixes, some of which originate in Dovecot, one TODO item has finally been resolved: the reject action uses the LDA mail reject API,

Hello Dovecot users, The new Dovecot v2.0.8 release has a few changes that prompted changes in Pigeonhole as well. This means that a new release of Pigeonhole is also necessary, because otherwise things will not compile anymore. Apart from a few rather minor bugfixes, some of which originate in Dovecot, one TODO item has finally been resolved: the reject action uses the LDA mail reject API,

http://dovecot.org/releases/2.1/dovecot-2.1.2.tar.gz http://dovecot.org/releases/2.1/dovecot-2.1.2.tar.gz.sig There are a ton of proxying related improvements in this release. You should now be able to do pretty much anything you want with Dovecot proxy/director. This release also includes the initial version of dsync-based replication. I'm already successfully using it for @dovecot.fi