similar to: Homedir permissions problems with LDAP

Hi Charles I receive the Timo's reply. thanks for send me again Use the option that i said, but the problem persists. userdb static { args = uid=500 gid=500 } userdb prefetch { } Jan 2 23:50:08 michel dovecot: auth(default): new auth connection: pid=18374 Jan 2 23:50:20 michel dovecot: auth(default): client in: AUTH 1 PLAIN service=POP3 secured lip=127.0.0.1

Dovecot version dovecot-1.0.rc14-7 (opensuse) Postfix is using Dovecot LDA. I'm getting this error message, and I guess it's going to be a problem on my next task, which is to set up sieve scripts. Is there something wrong/contraditory on my config or I forgot something? I want: /var/dovecot-tests/: where user's inbox resides /var/dovecot-tests/home/: home dir (users will not be

Hi list, I have both lazy_expunge and fts_autoindex activated (with fts-xapian), as follows: plugin { lazy_expunge = EXPUNGED/ } plugin { fts = xapian fts_xapian = partial=2 full=20 attachments=1 verbose=0 fts_autoindex = yes fts_enforced = yes fts_autoindex_exclude = EXPUNGED fts_autoindex_exclude2 = EXPUNGED/* } However, I still see "indexer-worker...: Info: Indexed 1 messages in

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

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

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, 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

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

Hi, I think I found a bug in Dovecot 2.1.17 and 2.2.13. In our setup, sometimes ACLs stop working because "dovecot-acl-list" is replaced by an empty file. We found that lazy_expunge is connected to this. To reproduce, create ACLs for "user1" in a folder. Put a mail in that folder and expunge it, so that the folder will be created in the "expunged" namespace.

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

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

Hi! I'm trying to use an ACL to avoid deletion of messages that are inside .Trash folder, the ACL is already working very well, the problem that I'm facing is that even if the message is not deleted, mail_log logs that it has been deleted. Also, in some cases part of the lazy_expunge code is executed too, but sometimes I just dont know where the message is, thats weird. I erased

Hello everyone. I have a problem using Dovecot 2.2.26 with ACL plugin and deleting e-mails from a shared mailbox. My user doesn't have the "expunge" permission on the shared mailbox, but it has the "write-deleted" permission. So, when I delete a message from the shared mailbox using a client that implements the IMAP MOVE command, it tries to move the message to my Trash

Hi, I tried to migrate my dovecot 2.2 to a new server with a other storage configuration and dovecot 2.3. New (and old) Server uses mysql for user information I use the following storage settings mail_home = /storage1/vmail/%{userdb:path} mail_location =

On Tue, Jan 3, 2017, at 06:14 PM, Aki Tuomi wrote: > > > On 12/27/2016 06:35 PM, Daniele Barresi wrote: > > Hello everyone. > > I have a problem using Dovecot 2.2.26 with ACL plugin and deleting e-mails > > from a shared mailbox. > > > > My user doesn't have the "expunge" permission on the shared mailbox, but it > > has the

Hi! I'm using lazy_expunge to backup that are deleted/expunged, but I would like it to be visible to the user. I tried something like: namespace private { prefix = .EXPUNGED/ separator = / location = maildir:~/Maildir/.Apagadas } namespace private { prefix = .DELETED/ separator = / location = maildir:~/Maildir/.Apagadas } namespace private { prefix = .DELETED/.EXPUNGED/

Hi, I tried the plugin but it is not working. Am using virtual mailboxes. I added the following in dovecot.conf then restarted dovecot. Please guide me to the correct configuration. ############################## namespace private { prefix = separator = / inbox = yes } # namespace for lazy_expunge plugin: namespace private { prefix = .EXPUNGED/ separator = / location =

Hello, So i had this email in my inbox, i moved it to Folder1/tickets/ folder, then i decided to move the same email back to my inbox and when i went to the inbox it wasnt there nor in Folder1/tickets/ folder... I opened a SSH session to the mail server and went to /srv/mail/ vmail/DOMAIN.COM/rventura/Maildir There i did "ll expunged/.INBOX/cur" and it showed me 300+ emails

Today I tried to import mail directly on the server's home directory on the server. I copied it directly. I didn't use the imap protocol. Dovcot didn't recognize these emails. I didn't display these imported emails on my page, recalculating disk quotas. It will not increase the used capacity. I try to send an email to this user, dovcot recognizes all the emails, and recalculates

Hello List, do some tests with lazy_expunge i have 2 short questions. is it possible to set folder for expunged messages to read-only so no user is possible to really delete them? i can use mdbox for expunged-folder. but would'nt it be more functional to use maildir to have possibility to delete separate mails? when using mdbox the clean up by cron would effect always multiple messages