On 2013-11-28 10:38 AM, Héctor Moreno Blanco hmor...@gmv.com wrote:
When I try to set acl to a folder:
a02 setacl inbox.test1 user1 lr
a02 BAD Error in IMAP command SETACL: ACLs disabled.
In the logs, I can see:
dovecot: imap(testing_ddfr): Debug: acl: No acl setting - ACLs are disabled
Hi
After upgrading the kernel, everything is fine, except dovecot authentication.
I get this trange thing (data after REQUEST? changed just in case it
contains anything sensitive):
Nov 29 16:56:01 volanges dovecot: auth: Error: BUG: Authentication client sent
unknown handshake command:
On 28.11.2013, at 12.22, Kai Hendry hen...@dabase.com wrote:
Hi there,
Whilst trying to come up with a minimal configuration for Dovecot:
http://dabase.com/blog/Minimal_Dovecot/
I noticed the configuration syntax is a bit admin unfriendly. It's easy
to get an infamous Error code 89.
If
On Wed, 2013-11-27 at 14:43 +0800, Trent Lloyd wrote:
I am seeking to understand if there is any significant reason
proxy_maybe is handled during the auth section, it would seem better
to simply always set ‘proxy=yes’, and then optionally have proxy_maybe
passed all the way through to the
This seems to fix the issue
--- a/dovecot-antispam-plugin/src/antispam-storage-2.0.c
+++ b/dovecot-antispam-plugin/src/antispam-storage-2.0.c
@@ -91,15 +91,6 @@ antispam_copy(struct mail_save_context *ctx, struct mail *mai
int ret;
bool src_trash, dst_trash;
- if
