similar to: Doveadm-Expunge v2.0.5

http://dovecot.org/releases/2.0/dovecot-2.0.5.tar.gz http://dovecot.org/releases/2.0/dovecot-2.0.5.tar.gz.sig See the "ACL handling bugs" message for more details about the ACL merging bug. * acl: Fixed the logic of merging multiple ACL entries. Now it works as documented, while previously it could have done slightly different things depending on the order of the entries. *

http://dovecot.org/releases/2.0/dovecot-2.0.5.tar.gz http://dovecot.org/releases/2.0/dovecot-2.0.5.tar.gz.sig See the "ACL handling bugs" message for more details about the ACL merging bug. * acl: Fixed the logic of merging multiple ACL entries. Now it works as documented, while previously it could have done slightly different things depending on the order of the entries. *

V2 of dovecot has had the following releases (to recap) 2.0.0 2010-08-16 2.0.1 2010-08-24 2.0.2 2010-09-08 2.0.3 2010-09-17 2.0.4 2010-09-26 2.0.5 2010-10-01 I am on FreeBSD, and the port committers want to wait till dovecot V2 "stabilizes" prior to adding it to the FreeBSD ports base. So, my question is, respectfully, is dovecot V2.0.5 stable enough for prime-time on a busy ISP

I am running Win 98 SE and have a Samba server v2.0.5 on a FreeBSD 3.3 system. Both machines sit on the same 100baseTX subnet. I am seeing expected read performance, but writes from Win98 to the Samba share are terrible; upwards of 30 seconds to copy a 900kb file (yes, that's kb). This happens in both Explorer, the DOS "shell", and in the application that actually created the file

Right, Changes made to dovecot-2.0.5/src/lib-master/master-service.c conn.listen_fd = l->fd; conn.fd = net_accept(l->fd, &conn.remote_ip, &conn.remote_port); i_error("conn.fd: %d",conn.fd); i_error("l->fd: %d",l->fd); i_error("&conn.remote_ip:

Hi, ssh server: OpenSSH_6.3-FIPS, OpenSSL FIPS Object Module v2.0.5 ssh client: OpenSSH_5.3p1, OpenSSL FIPS Object Module v1.2 We have built and installed FIPS object module (v2.0.5) using http://www.openssl.org/source/openssl-fips-2.0.5.tar.gz Using this FIPS object module, we have build FIPS capable openssl as well. Note that we have "not" used ecp version (with binary curve

Hello Dovecot v2.0.5 zlib_save_level = 6 # 1..9 zlib_save = gz # or bz2 Is there a config option to disable zlib, even if above config are in place? If so please provide an example. If no, would it be possible to add one? Like if zlib_save_level = 0 disable zlib. So one can configure per mailbox compression level via sql database. KuiZ Thanks

Hi there again, I just wanna tell you what little bug we've found... Namespace is in mbox format. After deleting an mbox the entry in the .imap stays so not everyting is moved away and ist just hanging around... not so bad, but would be nice if it was cleaned up... thanks Tobi -- Dr. Nagler & Company GmbH Hauptstra?e 9 92253 Schnaittenbach Tel : 09622-7197-38 Fax : 09622-7197-50

I am having problems with dovecot regarding base_dir: I have :: base_dir = /opt/dovecot2/var/run/ For some reason, I have to set permissions to(chmod -R 1777 /opt/dovecot2/var/) for dovecot to run properly, but when I start dovecot, I see this: [root at gw] /opt/dovecot2/etc/dovecot# less /var/log/dovecot/dovecot.log Oct 21 16:15:27 master: Warning: Killed with signal 15 (by pid=72634 uid=0

http://dovecot.org/releases/2.0/dovecot-2.0.7.tar.gz http://dovecot.org/releases/2.0/dovecot-2.0.7.tar.gz.sig * master: default_process_limit wasn't actually used anywhere, rather the default was unlimited. Now that it is enforced, you might notice that the default limit is too low and you need to increase it. Dovecot logs a warning when this happens. * mail-log plugin: Log mailbox

http://dovecot.org/releases/2.0/dovecot-2.0.7.tar.gz http://dovecot.org/releases/2.0/dovecot-2.0.7.tar.gz.sig * master: default_process_limit wasn't actually used anywhere, rather the default was unlimited. Now that it is enforced, you might notice that the default limit is too low and you need to increase it. Dovecot logs a warning when this happens. * mail-log plugin: Log mailbox

I thought I'd write one mail about this, rather than duplicate the whole thing to both v1.2.15 and v2.0.5 release announcements. So, ever since this commit: 2009-11-10 Timo Sirainen <tss at iki.fi> * src/plugins/acl/acl-backend-vfile.c: acl: Merge group rights if user belongs to more than one. [76ff6831c9ae] The ACLs were being merged, rather than fully replaced, a bit too

I thought I'd write one mail about this, rather than duplicate the whole thing to both v1.2.15 and v2.0.5 release announcements. So, ever since this commit: 2009-11-10 Timo Sirainen <tss at iki.fi> * src/plugins/acl/acl-backend-vfile.c: acl: Merge group rights if user belongs to more than one. [76ff6831c9ae] The ACLs were being merged, rather than fully replaced, a bit too

Nut shut down a machine last night when there was no power outage. When I came in this morning, the UPS was turned off, but it turned on cleanly and passed its self-test. The battery was at 62% when I first checked it, and it's up to 63% now, about 20 minutes later. The UPS is a Tripp-Lite AVR550U. I'm running nut version 2.0.3. I expect to be told to update to a newer version and to