Displaying 20 results from an estimated 30000 matches similar to: "v1.2.10 released"
2010 Jan 25
1
Released Pigeonhole Sieve v0.1.15 and ManageSieve v0.11.11 for Dovecot v1.2.10
Hello Dovecot users,
It's been a while since the last Pigeonhole Sieve and ManageSieve
releases. That is why this release includes quite a few changes. Most
interestingly, the include extension is updated to match the most recent
specification, the Sieve interpreter now includes plugin support and
ManageSieve now has support for enforcing quota on the size of scripts,
the number of
2010 Jan 25
1
Released Pigeonhole Sieve v0.1.15 and ManageSieve v0.11.11 for Dovecot v1.2.10
Hello Dovecot users,
It's been a while since the last Pigeonhole Sieve and ManageSieve
releases. That is why this release includes quite a few changes. Most
interestingly, the include extension is updated to match the most recent
specification, the Sieve interpreter now includes plugin support and
ManageSieve now has support for enforcing quota on the size of scripts,
the number of
2010 Jul 25
2
using Lazy_Expunge to enforce retention policy
Hi,
I've been experimenting with using Lazy_Expunge as a tool to enforce
document retention policies (by keeping users from deleting emails
forever, instead expiring them after a set time). My problem is, how do
I keep the user from deleting/expunging mails *inside the expunge folder
itself*?
I am using dovecot-1.2.10 built from FreeBSD's ports tree, and I am
using the following
2010 Feb 12
1
dovecot v1.2.10 + unknown mail_uid parameter
hi...
i upgrading dovecot from v1.0.7 to v1.2.10, so i perform some modifications
(http://wiki.dovecot.org/Upgrading/1.1 and
http://wiki.dovecot.org/Upgrading/1.2), but i have the following problem
when i want to test installation:
in dovecot.conf, i set the user mail:
mail_uid= 72940
mail_gid= 72941
but when i try to start dovecot i have the following error:
# sbin/dovecot
2017 Feb 22
0
v2.2.28 release candidate 2 released
http://dovecot.org/releases/2.2/rc/dovecot-2.2.28.rc2.tar.gz
http://dovecot.org/releases/2.2/rc/dovecot-2.2.28.rc2.tar.gz.sig
I'm assuming that most of the bugs are now found and fixed, so the final 2.2.28 should be out in a day or two.
Changes since rc1:
* Reverted [UNKNOWN-CTE] -> [PARSE] change
+ pop3c: Added pop3c_features=no-pipelining setting to prevent using PIPELINING extension
2017 Feb 22
0
v2.2.28 release candidate 2 released
http://dovecot.org/releases/2.2/rc/dovecot-2.2.28.rc2.tar.gz
http://dovecot.org/releases/2.2/rc/dovecot-2.2.28.rc2.tar.gz.sig
I'm assuming that most of the bugs are now found and fixed, so the final 2.2.28 should be out in a day or two.
Changes since rc1:
* Reverted [UNKNOWN-CTE] -> [PARSE] change
+ pop3c: Added pop3c_features=no-pipelining setting to prevent using PIPELINING extension
2017 Feb 24
2
v2.2.28 released
http://dovecot.org/releases/2.2/dovecot-2.2.28.tar.gz
http://dovecot.org/releases/2.2/dovecot-2.2.28.tar.gz.sig
* director: "doveadm director move" to same host now refreshes user's
timeout. This allows keeping user constantly in the same backend by
just periodically moving the user there.
* When new mailbox is created, use initially INBOX's
dovecot.index.cache
2017 Feb 24
2
v2.2.28 released
http://dovecot.org/releases/2.2/dovecot-2.2.28.tar.gz
http://dovecot.org/releases/2.2/dovecot-2.2.28.tar.gz.sig
* director: "doveadm director move" to same host now refreshes user's
timeout. This allows keeping user constantly in the same backend by
just periodically moving the user there.
* When new mailbox is created, use initially INBOX's
dovecot.index.cache
2007 Apr 16
2
lazy_expunge vs mulberry
I've configured the lazy_expunge plugin exactly like it says on the wiki.
I can't seem to configure Mulberry to find the new namespaces. Any hints?
I notice that the wiki says to use / as the separator. Mulberry has a
setting for this, and the default is '.'. Leaving this as '.' in Mulberry
and / in dovecot seems to work fine. (But I still can't access the
2010 Feb 19
2
quota and lazy_expunge plugins both used: quotas go wrong with lazy_expunge'd mails
Hello,
I may have missed a point, but I could have found an issue between plugins
quota and lazy_expunge.
I have noticed that the "lazy_expunge"d mails are counted as part of the
quota, while the documentation says it should not be. I have first tried to
find out if this was a configuration mistake somewhere. Notably, you can
notice that the expunged mails are in directory ~/expunged
2017 Feb 20
9
v2.2.28 release candidate released
http://dovecot.org/releases/2.2/rc/dovecot-2.2.28.rc1.tar.gz
http://dovecot.org/releases/2.2/rc/dovecot-2.2.28.rc1.tar.gz.sig
Pretty large release. Please test before the final v2.2.28, which should be out in a few days.
BTW. Our plan is to start making new releases approximately every month from now on.
* director: "doveadm director move" to same host now refreshes user's
2017 Feb 20
9
v2.2.28 release candidate released
http://dovecot.org/releases/2.2/rc/dovecot-2.2.28.rc1.tar.gz
http://dovecot.org/releases/2.2/rc/dovecot-2.2.28.rc1.tar.gz.sig
Pretty large release. Please test before the final v2.2.28, which should be out in a few days.
BTW. Our plan is to start making new releases approximately every month from now on.
* director: "doveadm director move" to same host now refreshes user's
2011 Sep 16
1
Deleted mailboxes with lazy_expunge
Hello,
I'm trying to configure lazy_expunge plugin (as a way to provide easy
backup for mails). This is my configuration (as explained in dovecot wiki):
# Default namespace
namespace {
prefix =
separator = /
inbox = yes
}
# namespaces for lazy_expunge plugin:
namespace {
prefix = .EXPUNGED/
separator = /
location = maildir:~/Maildir/expunged
}
namespace
2011 Aug 08
1
Error when trying to delete folders
Hi,
I'm using Dovecot 2.0.12 as an IMAP server. I'm using the lazy expunge
plugin (2 namespaces - default and .EXPUNGED).
When trying to delete a folder, I get this error:
"Server Error: DELETE: Can't rename mailboxes across specified storages"
Is that related to the lazy expunge plugin? What does this error means
exactly and how can I fix it?
`dovecot -n` output:
#
2015 Mar 03
2
acl and lazy_expunge plugins are incompatible?
Hello list.
Following two previous unanswered requests
(http://www.dovecot.org/list/dovecot/2014-August/097449.html and
http://www.dovecot.org/list/dovecot/2014-May/096261.html), I fell into the
same problem: ACL and lazy_expunge plugins do not work together.
I had lazy_expunge enabled working OK. Then I activated ACL plugin, and gave
dovecot.2 visibily over paolo.cravero's Inbox: the IMAP
2009 Dec 28
3
disable lazy_expunge for some mailboxes?
How to disable lazy_expunge for certain mailboxes?
My problem is I have a public namespace, whose mail is on a different
filesystem than user mails. Some users are allowed to expunge on this
shared mailbox, but lazy_expunge is stopping that from working since
the mail has to cross a filesystem boundary to make it into the
lazy_expunge namespace (location is under the user's home directory).
2006 Jun 08
2
Running the same application multiple times with different enevironments
Hi!
I have an application that needs to be run on multiple virtual hosts
(Apache2) with each instance having it''s own environment / database.
Using dispatch.cgi I simply configure two virtual hosts pointing to the
same application path and just add a "SetEnv RAILS_ENV
<environment_name>" to each virtual host section in the Apache
configuration. But with FastCGI /
2018 May 23
0
lazy_expunge ...
So digging a little deeper it seems this maybe an issue between
fts/fts_lucene and lazy_expunge .. if I disable the fts plugin
[root at stargate dovecot.rawlog]# doveadm search -u matt at the-bryants.net
mailbox .EXPUNGED/Trash from noreply at apress.com
6156a416748c035b5c0b0000ef794dd1 1
search works ..
so begs the question whats fts_lucene doing ...
rgds
Matt
> Matt Bryant
2015 Apr 24
0
acl and lazy_expunge plugins are incompatible?
Hello.
Before going into deep testing of 2.2.16 (clean install tbd), I would like
to know if someone is using succesfully both ACL and Lazy_expunge plugins.
Perhaps I had a config error?
Thanks,
Paolo
> Il 3 marzo 2015 alle 16.36 Paolo Cravero <paolo.cravero at csi.it> ha
> scritto:
>
>
> Hello list.
> Following two previous unanswered requests
>
2014 Oct 30
0
Bug in the combination of Lazy_expunge and acl plugin
Hello Timo, Hello Dovecot Developers, Hello everyone on the list,
I think I have some bug, because I haven't found a working configuration
till now.
I use latest dovecot 2.2.13 from the dovecot-ee repository, with acl and
the lazy_expunge plugin.
My configuration for shared folders work fine with lazy_expunge disabled.
If I enable lazy_expunge and the user (named userA), which I'm