similar to: 1.2.beta1: expire-tool and 'mail_location' setting

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:

Hello all! dovecot 1.1.6 Use lazy_expunge plugin call core on connect. Core: bt full #0 lazy_expunge_mail_expunge (_mail=0x2ac06e9b89e8) at lazy-expunge-plugin.c:103 lt = (struct lazy_expunge_transaction *) 0x2ac06e9b86e0 deststorage = <value optimized out> #1 0x000000000041cefc in imap_expunge (box=0x2ac06e988de8, next_search_arg=0x0) at imap-expunge.c:31 ctx =

I was struggling for a while to get the expire plugin to expunge mail. I was using (and still would like to use) PAM as passdb and passwd as userdb but with this I could not get the expire-tool to delete any mails. For debugging purpose I switch to passwd-file as userdb/passdb and enabled mail_debug=yes. 1. passwd-file contains home directory and userdb_mail (->working!)

Hello list, Sorry, if it has been asked, but searching throught list not give possitive answers. After upgrade to dovecot version 1.2.1 expire-tool stoped working. I have changed database format and config file to appropriative 1.2 version but: expire-tool.sh fails with: # dovecot -c /etc/dovecot/dovecot.conf --exec-mail ext /usr/libexec/dovecot/expire-tool.sh Info: Loading modules from

http://dovecot.org/releases/2.0/beta/dovecot-2.0.beta1.tar.gz http://dovecot.org/releases/2.0/beta/dovecot-2.0.beta1.tar.gz.sig Now that v2.0 is in beta stage I don't expect anything big to change anymore. The configuration and the APIs shouldn't change in non-backwards compatible ways. There are still bugs left to be fixed and some small features to be implemented, but I'd like to

http://dovecot.org/releases/2.0/beta/dovecot-2.0.beta1.tar.gz http://dovecot.org/releases/2.0/beta/dovecot-2.0.beta1.tar.gz.sig Now that v2.0 is in beta stage I don't expect anything big to change anymore. The configuration and the APIs shouldn't change in non-backwards compatible ways. There are still bugs left to be fixed and some small features to be implemented, but I'd like to

Hey guys, got a question about the expire plugin. According to the wiki, the expire plugin "keeps an internal database (Berkeley DB or SQL)". I was wondering what fields in the mysql table are needed for expire to work. I assume it is setup is similar to the quota dict setup, so was just wondering what fields are required (i.e: select_field, where_field, username_field, for quota).

Hi @ll, using sieve dovecot2 rc1 on testing system ubuntu lucid with packs recompiled from http://xi.rename-it.nl/debian/ i have Jul 05 11:48:35 managesieve: Debug: Module loaded: /usr/lib/dovecot/modules/lib01_acl_plugin.so Jul 05 11:48:35 managesieve: Error: dlopen(/usr/lib/dovecot/modules/lib02_imap_acl_plugin.so) failed: /usr/lib/dovecot/modules/lib02_imap_acl_plugin.so: undefined symbol:

Hi, I'm wondering, whether it's possible, to define an ACL on the mailbox itself. We use Dovecot 1.2.15 (included in Debian 6) and maildir filesystem layout: /home/mail01/user1/Maildir/new \ /home/mail01/user1/Maildir/cur Inbox /home/mail01/user1/Maildir/tmp / /home/mail01/user1/Maildir/.folder1/new \ /home/mail01/user1/Maildir/.folder1/cur folder1

Hello. I use expire plugin with dovecot 1.1.10. See my dovecot -n: # 1.1.10: /usr/local/etc/dovecot.conf # OS: FreeBSD 6.3-RELEASE-p9 i386 ufs syslog_facility: local6 protocols: imap imaps managesieve ssl_cert_file: /etc/ssl/mail/mail.domain.net.cert ssl_key_file: /etc/ssl/mail/mail.domain.net.key disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default):

All of the mailboxes on this system are in MailDIR format. None of the users delete mail off of the server after POPing their accounts. This is the present setting: expire = Trash 7 Spam 30 expire_dict = proxy::expire Is that correct for MailDIR style mailboxes? It doesn't appear correct; however, I have not been able to find any specific documentation on expire with MailDIR style

Hello, I have dovecot set up with expire-tool to nuke Junk messages greater than 30 days old. On a server with many user accounts, it seems to work on most of them. However, on my user account, expire-tool skips my Junk folder entirely, despite it containing messages from January of this year. Here is the expire-tool --test output: Info: alex at scienceforums.net/Junk: timestamp 1284027481 (Thu

Hello, I'm having problems with expire-tool in Dovecot 1.2.6 not finding the mailboxes. I had mail_location = mbox:/var/spool/dovecotmail/%d/%n/mails:INDEX=/var/spool/dovecotmail/%d/%n/indexes in dovecot.conf, but that doesn't work with expire-tool. So I commented that out from dovecot.conf, all the data is in a database anyway. A userdb lookup returns the following for userid at

Hi. I test expire plugin for my dovecot 1.1.8. But, it seems to not work. I have 3 mailboxes on my machine. I want my messages in Junk and Trash expire after 1 day. I removed all messages in them before installing expire plugin. See my dovecot.conf: expire: Trash 1 Junk 1 expire_dict: proxy::expire My dabatases in /var/lib/dovecot are used. When I launch /usr/local/sbin/dovecot

Hello, I've been trying to get managesieve to work for our LAN, but when I try to login from a remote host i always get the following line in the log file: dovecot: child 26014 (login) killed with signal 11 When i enable debuging, it just gives me that line, nothing more. I can only login from the localhost through telnet but not from a remote host. My conf: # 1.1.6:

After upgrading from 1.1.3 to 1.1.4 the imap process crashes as soon as moving a mail to the Trash folder. Belows backtrace points to the expire plugin... Backtrace /usr/local/libexec/dovecot/imap: Program terminated with signal 11, Segmentation fault. #0 0x2adbeaa8 in expire_mailbox_transaction_commit (t=0x10045248, uid_validity_r=0x7fff77fc, first_saved_uid_r=0x7fff7800,

Hello all! I tried to add the expire-plugin to my dovecot-installation (CentOS-RPM: dovecot-1.1.1-2_76.el5) and followed the plugin-page from the WIKI (http://wiki.dovecot.org/Plugins/Expire). Unfortunately I have problems with the dictionary: --> dovecot: Aug 05 13:30:25 Error: dict: Unknown dict module: db dovecot: Aug 05 13:30:25 Error: dict: Failed to initialize dictionary

Hi all, I am running Dovecot v1.1.7 in a relatively quiet and calm environment. Suddenly overnight cron job has started throwing out errors like: /usr/sbin/dovecot --exec-mail ext /usr/lib/dovecot/expire-tool Error: userdb(user1 at mail.example) didn't return a home directory Error: userdb(user2 at mail.example) didn't return a home directory Indeed, running this command produces:

Hi, I would like to upgrade my server from 1.2.16 with sieve and managesieve to 2.0.8 with pigeonhole. Will I get all functionality I was having before? Should this migration be painless or will it require some additional work? I've read the Upgrading guide so I know I need to create an additional user. I've migrated the mails from Maildir to dbox in the past (using the convert

Hello list, After upgrade to dovecot version 1.2.6 I have noticed some quota malfunctions(users become often overquota). Looking at logs closely I have found that quota value resets to general dovecot-config( quota = maildir:Mailbox quota quota_rule = *:storage=500M quota_rule2 = Trash:storage=10%% ), after dovecot --exec-mail ext /usr/libexec/dovecot/expire-tool.sh command. The problem that