similar to: mdbox + sis + altstorage: error in attachments-connector (file not found)

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 >

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

Andreas, > I am interested in finding out your experiences with using the dbox > format (especially mdbox) if you use this format. mdbox is THE reason why I am trying Dovecot. With mailboxes of several (tens of) GB with several k of messages I hope mdbox will speedup backups. Also SIS for attachments sounds very good, but still doesn't follow the altstorage rules (while messages go to

The mdbox-format with the altstorage-feature is quite nice and important. But we're having much more then >> 30 TB of maildata and doing an fsck on huge partitions takes too much (down-) time for our mailsystem. It would be much easier, if Dovecot would be able to use at least THREE storage-paths for his m-Files (and not just TWO like now). Having an altstorage1 and altstorage2, we

Ok I played around a bit and activated debugging correctly (Thanks to Steffen) Now I try to log in with the user johndoe (that is his cn and his uid) and i get the following message in syslog: Mar 2 11:03:32 mailserver dovecot: auth: Debug: master in: REQUEST#0111283457025#0117428#0111#011d139b5d372d882643bc995003c615c89 Mar 2 11:03:32 mailserver dovecot: auth: Debug:

Hi, since migration to Dovecot 2.2 I have troubles with lazy_expunge as soon as a user shares a folder. The user the folder is shared to cannot login anymore, dovecot logs Fatal: lazy_expunge: Unknown namespace: '.EXPUNGED/' - When no folder is shared lazy_expunge is working fine, deleted mails are moved to the expunged namespace and can be recovered without any problems. - Sharing

Hello, our dovecot mailservice was running smoothly for a long time. Since last week we get the following error message when connecting from the horde/imp webmailer to the public namespace: Panic: file acl-cache.c: line 294 (acl_cache_update): assertion failed: (obj_cache->my_current_rights != &negative_cache_entry) Dovecot and horde/imp are running on seperate hosts. There are no

Hello, I've downloaded the metadata plugin from http://hg.intevation.org/kolab/dovecot-metadata-plugin compiled it without errors, made the entries as described in README in dovecot.conf. Only ANNOTATEMORE or anything else additional doesn't show up in the capabilties. Is there anything wrong with my configuration? What I see is: telnet localhost 143 Trying 127.0.0.1... Connected to

Hi, we are thinking about storing older mails (eg. safed before 6 months) to an alternative storage mounted via NFS from an external storage box. Some technical details - the storage will be connected via 1 gbit ethernet. Access will be allowed from different dovecot servers, but only to divided directories for each dovecot. - storage has the option to use RAID 5 or 6. Max. amount of Disks are

Hi, User's mailbox is failing to sync. Log: Error: read(attachments-connector(/path/storage/m.217)) failed: read(/path/attachments/a5/b0/a5b01f595205522593c27457ea51094872f1f2b42b01e90d27d3f9237bc8a2ab-dbf7460d4778b152ec6e00000d189396[base64:18 b/l]) failed: Stream is larger than expected (256088 > 256087, eof=1) (FETCH BODY[] for mailbox INBOX UID 29925) Sounds like issue here:

Hi, Here is a crash that's happening using the latest Dovecot version (v2.2.27 on CentOS7 x86_64): We are using replication. Judging by the second server's logs, I believe this has something to do with the fact that we're using the lazy_expunge plugin. Every night after midnight, we purge the lazy_expunge namespace by running a command similar to following one on the main server

I am interested in finding out your experiences with using the dbox format (especially mdbox) if you use this format. I am contemplating changing my maildir setup to mdbox but I still need to make a case for it against maildir which has become a de-facto standard and provides sort of a secure basis in case of software changes. Your input will be appreciated. -- Andreas Kasenides Senior IT

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

Hello List, with dovecot version 2.2.13.9, I actually have a problem using lazy_expunge and acl together. Shared/Public Folders work fine with lazy_expunge disabled. If lazy_expunge is enabled and userA got a shared folder form userB, then there is the error shown in subject. My test case to reproduce the error. doveadm mailbox list -u userA at domain --> Output Fine. doveadm acl set -u

Hello, I have a problem importing messages since I have configured lazy_expunge. My lazy_expunge configuration (that is correctly working when a message is expunged) is: plugin { lazy_expunge = BORRADOS. } namespace { hidden = yes list = no location = maildir:~/Maildir/expunged prefix = BORRADOS. separator = . } but when I try to import messages I get: amateo_adm at

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

Hello everybody, I have a question about lazy_expunge plugin. I set up Dovecot with lazy_expunge plugin on a Debian Wheezy machine; I setup also a global acl to keep .expunged namespace readonly for all users. Imap client is Horde Webmail Edition 5.2.3 When I try to delete folders containing subfolders, lazy_expunge copies into expunged private namespace only the upper level folder. The subfolder

Hello, I wanted to test the lazy expunge plugin together with mdbox. It seems to me that the folder subscriptions file in the mdbox directory was overwritten with only a few folder names every time I added or removed something in the list of subscribed folders, or even if I turned the imap folder subscription feature off and on. Here is my setup: # 2.0.16:

Hi all, Using Dovecot 1.0.3 on RedHat Enterprise 5 (kernel 2.6.18-8.1.6.el5PAE), and NFS storage, we symlinked a Maildir folder: /mailstore/user/Maildir/.Junk -> /junkstore/user/Junkmaildir Everything works fine, until we try to expunge, which produces: A04 NO BUG: Unknown internal error This only happens if "lazy_expunge" is enabled: mail_plugins = quota imap_quota acl

Hi, it seams that the lazy_expunge plugin doesn't work for me after the upgrade... 2.2.32 cry's about plugin { lazy_expunge_only_last_instance=no } is most likely handled as 'yes' - remove the setting completely to disable it. If this is intentional, add quotes around the value: lazy_expunge_only_last_instance="no" I changed it to