similar to: Expire plugin does not delete expired mail

Displaying 20 results from an estimated 12000 matches similar to: "Expire plugin does not delete expired mail"

2009 Feb 04
2
Expire plugin does not work
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
2009 Jan 28
1
Unknown dict module: db with expire plugin
Hello. I use dovecot 1.1.8 in a FreeBSD 6.3 Today, I want to active expire plugin. But it does not work. I made instructions described in http://wiki.dovecot.org/Plugins/Expire for a bdb database. See my dovecot -n: # 1.1.8: /usr/local/etc/dovecot.conf # OS: FreeBSD 6.3-RELEASE-p4 i386 ufs syslog_facility: local6 ssl_cert_file: /etc/ssl/mail/***********.cert ssl_key_file:
2011 Apr 15
1
expire-tool skipping mailbox
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
2009 Oct 15
4
MailDIR and expire plugin
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
2009 Dec 12
4
expire-tool and userdb returned mail location
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
2009 Feb 22
2
1.2.beta1: expire-tool and 'mail_location' setting
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
2009 Oct 28
3
expire plugin + --exec-mail in 1.2.6 version
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
2009 Jan 28
1
Differences when expire plugin and cronjob?
Hello. I would like to see the differnces between the expire plugin and a cronjob which make a find/delete. Is there performances differences? What's the best to use? I use dovecot 1.1.8. Is expire plugin update the maildirsize and other indexes files? Thanks. Regards, -- -Nicolas.
2008 Jul 10
1
Unknown dict module: db with expire plugin
Hello. I upgraded my dovecot to 1.1. I use the FreeBSD port. However, I can't use the expire plugin. See the error: Unknown dict module: db expire plugin: dict_init() failed I see on the mailing list another mail like this problem. And the problem is the imap library is not linked to libdb. Is there a solution? Have I to contact the FreeBSD maintainer to link the binary to the library?
2008 Mar 07
3
User another userdb to sasl
Hello, I use Dovecot 1.0.12 with Postfix on FreeBSD. It works perfectly, but I have a question. My users are virtual (stocked in a MySQL database). I use SASL Dovecot authentification, and SASL uses my userdb (for POP/IMAP access). However, I would like my users have an other login/password to send email with SMTP/SASL. Or, I don't want my users use the same login/password for POP/IMAP
2009 Oct 07
1
is it possible to fetch messages for multiple users using a single account?
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
2009 Sep 23
9
pop3-login: Fatal: io_loop_handle_add: epoll_ctl(1, 5):
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:
2008 Apr 12
2
Master user and missing folders
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.
2008 May 02
2
used_file_size too large
Hi. Just got this error (1.1.rc4), is it something to worry about? Corrupted index cache file /.../Maildir/.Sent/dovecot.index.cache: used_file_size too large This is a shared mailbox with concurrent access. In general, can that usage pattern mess up the index? I am guessing "no", which is why I worry slightly about the warning. Cheers, Anders.
2010 Oct 06
4
Significant performance problems
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
2009 Dec 23
1
Panic: file maildir-uidlist.c: line 1242 (maildir_uidlist_records_drop_expunges): assertion failed
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"]
2007 Mar 13
1
quota - dict - username = '(null)'
I am trying setting up at virtual domain with quota using postfix and dovecut. But I can't get the quota to work, every time I try sending a mail the following queries is run on the database. SELECT home, uid, gid FROM mail_view_tmp WHERE account = 'dummy' AND domain = 'example.com' SELECT current FROM mail_quota WHERE path = 'quota/storage' AND username =
2011 Oct 20
2
Expire plugin not executing for sieve plugin?
Running dovecot 1.2.12 on ubuntu 10.10. Here is the problem: I have mysql backend for expire. I am using the dovecot-postfix package which creates /etc/dovecot/conf.d/01-mail-stack-delivery.conf which looks like this: # Some general options protocols = imap imaps managesieve disable_plaintext_auth = no ssl = yes ssl_cert_file = /etc/ssl/certs/ssl-mail.pem ssl_key_file =
2011 Nov 08
2
Selecting 3 different hours in a day
Hello, I have a csv with 5months of hourly data for 4 years. I would like to get 9am, 12pm and 3pm from each day and create a subset or a new data frame that I can analyze. The time are from hour 0-23 for each day. I am not sure how to create a loop which will take out each of these hours and create a subset. I was thinking of doing a for loop using the row number since: 9am= row 10 12pm= row
2009 Jan 06
3
Problem with opening ports in alpha5 ?
If I leave the "listen" value as the default in /etc/dovecot.conf I'll get a message similar to the following on each port that it tries to open during startup: # dovecot -F Fatal: listen(::, 143) failed: Address already in use If I set either: listen = * or listen = [::] then it will start up fine. Perhaps it is as though the code tries to open the port twice for both