similar to: RTFM: Manual pages for Dovecot v2.0

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

http://dovecot.org/releases/2.0/rc/dovecot-2.0.rc1.tar.gz http://dovecot.org/releases/2.0/rc/dovecot-2.0.rc1.tar.gz.sig All of the important features are implemented and all of the important bugs are fixed. The only thing I'd like to solve before v2.0.0 is that two people have said their doveconf fails when trying to convert old v1.x config file. I haven't been able to reproduce this, so

http://dovecot.org/releases/2.0/rc/dovecot-2.0.rc1.tar.gz http://dovecot.org/releases/2.0/rc/dovecot-2.0.rc1.tar.gz.sig All of the important features are implemented and all of the important bugs are fixed. The only thing I'd like to solve before v2.0.0 is that two people have said their doveconf fails when trying to convert old v1.x config file. I haven't been able to reproduce this, so

Hi Timo, I've configured the user nobody for the the service auth. doveconf -n # 2.0.alpha3: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 2.6.30-1-amd64 x86_64 Debian squeeze/sid ? service auth { user = nobody } ? The other processes are executed by root (or logged in user): root 8758 0.0 0.0 2604 1052 ? Ss 07:21 0:00 /usr/local/sbin/dovecot root 8759 0.0

I've found this in my dovecot.log: ,--[ /path/to/dovecot.log ]-- | Jul 11 01:44:29 dovecot: Info: Dovecot v1.2.1 starting up | ... | Jul 11 01:50:21 auth(default): Info: client in: AUTH 1 PLAIN service=sieve lip=192.168.111.222 rip=192.168.111.122 lport=12000 rport=35084 resp=<hidden> | Jul 11 01:50:21 auth(default): Info: sql(j.doe at

Hi Timo, I've just setup Dovecot v1.2.rc5 and switched the mailbox format of one account to dbox. Therefor I've created an empty directory, called dbox, with access mode 0700, like the user's home directory. After the IMAP login with Thunderbird some dboxes was created. All permissions were set fine (0700 / 0600), except the permissions for the files: *

Hi Stephan, I've compiled the latest managesieve code from Sun May 17th 2009. ManageSieve had created the sieve directory with 0770 permissions, but the user's home directory has only 0700 permissions. With dovecot-1.{0,1}-managesieve the permissions was set properly. Regards, Pascal -- The trapper recommends today: cafebabe.0916419 at localdomain.org

Hi Timo, gcc tells me: main.c: In function ?main_init?: main.c:182: warning: suggest parentheses around comparison in operand of & src/imap/main.c:182: if (username == NULL & IS_STANDALONE()) Regards, Pascal -- The trapper recommends today: cafebabe.0920623 at localdomain.org

On 05/10/2015 04:01 PM, Thomas Leuxner wrote: > ... Not sure how it is supposed to interact with the file /etc/default/dovecot and its ALLOW_COREDUMPS=1 variable, but one needs to explicitly add LimitCORE=infinity in the 'Service' section (until someone with more systemd foo fixes it): > The attached patch could solve the problem. Regards, Pascal -- The trapper recommends today:

http://dovecot.org/releases/2.0/rc/dovecot-2.0.rc6.tar.gz http://dovecot.org/releases/2.0/rc/dovecot-2.0.rc6.tar.gz.sig I expect this to be the last release candidate. Unless release critical bugs are reported, I'll update the version number to v2.0.0 on Monday morning without any other changes. Since rc5 there have been mainly some small fixes and some error message improvements. The only

http://dovecot.org/releases/2.0/rc/dovecot-2.0.rc6.tar.gz http://dovecot.org/releases/2.0/rc/dovecot-2.0.rc6.tar.gz.sig I expect this to be the last release candidate. Unless release critical bugs are reported, I'll update the version number to v2.0.0 on Monday morning without any other changes. Since rc5 there have been mainly some small fixes and some error message improvements. The only

http://dovecot.org/releases/2.0/rc/dovecot-2.0.rc3.tar.gz http://dovecot.org/releases/2.0/rc/dovecot-2.0.rc3.tar.gz.sig A lot of dsync fixes. I think I've fixed now all of the bugs ever reported about dsync and I'm hopeful that it's now stable. All the rest of Dovecot looks pretty good too. Maybe v2.0.0 will be out next week. Changes since rc2: * Single-dbox is now called

http://dovecot.org/releases/2.0/rc/dovecot-2.0.rc3.tar.gz http://dovecot.org/releases/2.0/rc/dovecot-2.0.rc3.tar.gz.sig A lot of dsync fixes. I think I've fixed now all of the bugs ever reported about dsync and I'm hopeful that it's now stable. All the rest of Dovecot looks pretty good too. Maybe v2.0.0 will be out next week. Changes since rc2: * Single-dbox is now called

http://dovecot.org/releases/2.0/rc/dovecot-2.0.rc5.tar.gz http://dovecot.org/releases/2.0/rc/dovecot-2.0.rc5.tar.gz.sig Unfortunately v2.0.0 has to be delayed a while longer, because I found that there were still problems in plugin hook handling when using more than 2 plugins. Hopefully it's now finally fully fixed, but I'd like to be sure and wait for one more week to see if people can

http://dovecot.org/releases/2.0/rc/dovecot-2.0.rc5.tar.gz http://dovecot.org/releases/2.0/rc/dovecot-2.0.rc5.tar.gz.sig Unfortunately v2.0.0 has to be delayed a while longer, because I found that there were still problems in plugin hook handling when using more than 2 plugins. Hopefully it's now finally fully fixed, but I'd like to be sure and wait for one more week to see if people can

Hi, just in the process of updating my packages for R v2.0.0 and I have not had time to followed the R v2.0.0 discussions so maybe my questions have already been answered. A concern I have is that when creating packages they should be backward compatible with R v1.9.x for a while until all users and computers has migrated to R v2.0.x. It is pretty straightforward to setup my packages so that

http://dovecot.org/releases/2.0/rc/dovecot-2.0.rc4.tar.gz http://dovecot.org/releases/2.0/rc/dovecot-2.0.rc4.tar.gz.sig I'm planning to release rc5 maybe this Friday or weekend, and if there are no serious bugs just change the version number to v2.0.0 a day or two later. Largest changes since rc3: + director: Added director_doveadm_port for accepting doveadm TCP connections. +

http://dovecot.org/releases/2.0/rc/dovecot-2.0.rc4.tar.gz http://dovecot.org/releases/2.0/rc/dovecot-2.0.rc4.tar.gz.sig I'm planning to release rc5 maybe this Friday or weekend, and if there are no serious bugs just change the version number to v2.0.0 a day or two later. Largest changes since rc3: + director: Added director_doveadm_port for accepting doveadm TCP connections. +

There is a roff typo in pigeonhole's sievec.1.in. Roff treats the leading apostrophe on line 54 as an invalid command and produces bad output: dump to be written to stdout. The out-file argument may also be omitted, which has the same effect as for a com- piled Sieve binary file. Note that this option is not The output should be: