similar to: MailDIR and expire plugin

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

Dear list, I am running dovecot with LDAP. Each account has email in form abc at example.com, and messages are stored at /var/vmail/abc/Maildir. This is an external mail server, and I would like to use a cron job to fetch all messages to an internal server which has slow internet connection. It seems getmail supports multidrop retriever which might fit the bill. However I could not figure out how

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

My global sieve rule is not working and do not compile. But per-user sieve is working. Here is my dovecot -n: log_path: /var/log/dovecot.log protocols: imap pop3 ssl: no login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login mail_uid: 501 mail_gid:

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

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

Hi Timo, Trying 1.2.beta1 with expire plugin currently: When I set mail_location = maildir:~/.maildir the expire plugin doesn't delete messages. #: expire-tool --test Info: auth input: system_user=foo Info: auth input: uid=1000 Info: auth input: gid=1000 Info: auth input: home=/home/foo Info: foo/Trash: no messages left I also noticed that above command creates a new but empty directory

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

I have been running Dovecot 1.2.5 since Sept 14. Beginning at about 03:28 on Sept 21 for no apparent (to me) reason and continuing through the present, I am seeing log messages like the following and am experiencing delays logging in. Sep 22 19:07:15 sbh16 dovecot: dovecot: Temporary failure in creating login processes, slowing down for now Sep 22 19:07:15 sbh16 dovecot: pop3-login: Fatal:

http://dovecot.org/releases/2.0/rc/dovecot-2.0.rc5.tar.gz http://dovecot.org/releases/2.0/rc/dovecot-2.0.rc5.tar.gz.sig Unfortunately v2.0.0 has to be delayed a while longer, because I found that there were still problems in plugin hook handling when using more than 2 plugins. Hopefully it's now finally fully fixed, but I'd like to be sure and wait for one more week to see if people can

http://dovecot.org/releases/2.0/rc/dovecot-2.0.rc5.tar.gz http://dovecot.org/releases/2.0/rc/dovecot-2.0.rc5.tar.gz.sig Unfortunately v2.0.0 has to be delayed a while longer, because I found that there were still problems in plugin hook handling when using more than 2 plugins. Hopefully it's now finally fully fixed, but I'd like to be sure and wait for one more week to see if people can

Hi all, after inserting another sieve-rule, I get the following backtrace on deliver. The mail gets delivered into the Mailbox, but as deliver does not exit with 0, postfix bounces the mail. The additional rule is the same as all others in my .dovecot-sieve: > require ["fileinto", "include"]; > > if header :contains ["From"]

dovecot version 1.1.6 >dovecot -n # 1.1.6: /etc/dovecot/dovecot.conf # OS: Linux 2.6.27-gentoo-r1 i686 Gentoo Base System release 2.0.0 xfs base_dir: /var/run/dovecot/ protocols: imap pop3 listen(default): *:143 listen(imap): *:143 listen(pop3): *:110 ssl_disable: yes disable_plaintext_auth: no login_dir: /var/run/dovecot//login login_executable(default): /usr/libexec/dovecot/imap-login

Hi, all. I upgrade to 1.1.6, but the same config didn't work now. Error message while start dovecot: ----<---- Starting Dovecot Imap: Fatal: userdb didn't return a home directory, but mail location used it (%h): /%Lh/%Ld/%Ln/:INDEX=/%Lh/%Ld/%Ln/ Error: imap dump-capability process returned 89 Fatal: Invalid configuration in /etc/dovecot.conf ----<---- Here is my dovecot.conf

Hello again. I am trying to use a master user. The login works. However, a LIST command gives me only the INBOX. Is this to be expected? When logging in normally, I do get the full list of folders. (using Dovecot 1.1 rc3.) Anders.

Hi all, I'm sure my issues are a result of misconfiguration, but I'm hoping someone can point me in the right direction. I'm getting pressure to move us back to GroupWise, which I desperately want to avoid :-/ We're running dovecot 1.2.9 on Ubuntu 10.4 LTS+postfix. The server is a VM with 1 vCPU and 4GB of RAM. We serve about 10,000 users with anywhere from 500-1000 logged in

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

Dear list, since the distri upgrade to glibc 2.28, i can't build working dovecot binary's. Older with glibc 2.27 are working. The distri is LFS based. MariaDB 10.2.18 and 10.3.11 makes no difference. Having this on different systems. Messages Log: Dec 19 17:10:38 test kernel: traps: auth[30189] general protection ip:7f4b96d6598c sp:7ffef1f31710 error:0 in

Hello, I've configured dovecot to use expire plugin: heres my dovecot -n: --------------------- # 2.1.7: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.1 ext4 auth_mechanisms = plain login dict { expire = mysql:/etc/dovecot/dovecot-dict-expire-sql.conf.ext } mail_location = maildir:/home/mail/vhosts/%d/%n mail_plugins = expire mail_privileged_group = vmail

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