similar to: core in lazy_expunge plugin

others have found this problem ? this possible bug can be used by user in that way that one password login can use 2 maildirs in filesystem effitively give them all space qoutas and lost of other goodies so to speak: foo at example.com with a password can login with fOO at example.com and fOo at example.com add more chars to get more mailbox :/ confirms ? i found the problem when i had

Hello all. I have strange problem. As I understand IMAP use server2client command to tell what new email is arrived. So - all was good, but few weeks ago I notice what my thunderbird not show new messages. I think it was local problem(I switch distro what day) but soon my email clients what uses mostly Outlook-2007-SP1 start to confirm this problem. What can it be and how can I fix it? I

I have set up postifx and dovecot (1.1) with virtual users and delivery via LDA. I am very pleased with the results so far but have this problem with quotas. ? Setting a global quota using plugin { } I initially used maildir to set quotas, but they seem to apply to all folders apart from INBOX. ? For debugging I switched maildir to dict using mysql. The table populates as it should with sizes and

Hello all, I am struggeling to get my Dovecot SASL to work within postfix. I have used the configuration example listed on the main-site of dovecot and it basically isn't giving me any success at all. I am probably missing something easy, but after spending a few days testing and walking through everything I could think about I thought figured it was better to ask :) Hope someone can point me

Hi All I have not been able to get per user quotas going. A general quota works fine. My LDAP server is windows 2000. Here is my config mail# dovecot -n # 1.1.3: /usr/local/etc/dovecot.conf log_path: /var/log/dovecot.log protocols: imaps pop3s lda managesieve listen(default): * listen(imap): * listen(pop3): * listen(managesieve): *:2000 ssl_cert_file: /usr/local/etc/dovecot/ssl/certs/dovecot.pem

Hi All, Relatively new to Dovecot - converting from courier-imap. So far, I've got it working with virtual users (postfixadmin tables), and it seems to be working. I'm trying to get sieve working. It's not, so I tried turning up the logging, and putting it into a separate log file to get it out of the syslog for now. I can get the main dovecot to log, but I cannot get any log

I've been using 1.1.8 successfully but tried out 1.1.10 this morning. I have a combination of system and virtual users. The system users were unaffected by the change, but the virtual users all lost access to their mail because their home directories, as interpreted by dovecot, moved from user at domain to user at user@domain. The location of the home directory is given to dovecot for

Hi, Since the 23rd of March, we encounter mailbox corruption for some users (15 out of 5000) using POP mainly via Thunderbird. Symptoms are : -users can login but fail to receive new mails and fail to read their inbox -Dovecot.log : ar 29 11:00:06 Error: POP3(user_login): Couldn't init INBOX: Mailbox isn't a valid mbox -The mailbox start with either 'FFrom or

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've spent the past couple of hours trying to figure this out by checking the wiki and googling, but haven't come up with anything that works yet. I just installed dovecot 1.0.14 with the quota-rewrite (1.09) patch and i'm trying to get the quota overridden via a passwd-file type userdb. I had 1.0.13 without the new quota style patched

I'm having the most frustrating issue, and I'm at a loss for what is happening. I'm not even sure it is with Dovecot, but that's why I'm posting this here... if it isn't a dovecot issue, maybe someone can get me headed in the right direction? I've posted relevant dovecot and config info at the bottom of this post. Here's the scenario: We recently migrated our

My mail server consumed all of its configured file table slots and started returning ENFILE ("Too many open files in system") for many operations. This wreaked havoc with dovecot-1.1.13. Here are some areas where dovecot should detect and more gracefully handle ENFILE error returns: 1. Deliver should report an error more helpful than "Unknown internal error" when

Hi, I am trying to get dovecot working with postfix, and am coming up against this error message. I have this setting configured in the 'protocol lda' section. I am running v1.1.11 dovecot -n -c /etc/dovecot/dovecot-postfix.conf # 1.1.11: /etc/dovecot/dovecot-postfix.conf # OS: Linux 2.6.31-14-generic x86_64 Ubuntu 9.10 reiserfs log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap

> On 13 Aug 2019, at 15.37, Jean-Daniel via dovecot <dovecot at dovecot.org> wrote: > > > >> Le 13 ao?t 2019 ? 14:16, Sami Ketola via dovecot <dovecot at dovecot.org> a ?crit : >> >> >> >>> On 13 Aug 2019, at 14.58, James Brown via dovecot <dovecot at dovecot.org> wrote: >>> >>> I?m thinking of getting Solr

I'm currently trying out 1.2.beta1 and get the following error in 'mail.err' log file as soon as I stop dovecot: Feb 11 20:28:30 server dovecot: Fatal: io_loop_handle_add: epoll_ctl(1, 11): Bad file descriptor Is that anything critical? Thanks, e-frog -------------------------------------------------------------------------------- >: dovecot -n # 1.2.beta1:

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

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).

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

Hi Timo, hi all, we want to use the "lazy_expunge" plugin (from dovecot 2.1.10) and had configured it in a test environemnt like described in "http://wiki2.dovecot.org/Plugins/Lazyexpunge" (1 namespace) There are some subfolders from "INBOX" (like "INBOX/SPAM") in a "maildir++" configuration. All actions on first level directories

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