similar to: expire tool - individual user/folder?

Hello, is the expire plugin usable to delete mails with different settings for each individual user? If i view sample config at http://wiki.dovecot.org/Plugins/Expire it looks like expire-data are related to foldernames. Is it possible to let each user "activate" the expire-plugin for different folders with different settings? Thanks, Andre

Hi folks, when I run expire-tool, I often see messages like the following: # dovecot --exec-mail ext /usr/libexec/dovecot/expire-tool Info: user/Trash: stop, expire time in future: Fri May 22 17:42:23 2009 the server's dovecot.conf contains the following line: expire = Trash 2 Junk 7 */News 30 */Reports 7 >From what I observe, an error of "expire time in future" in one

Hi! I'm using Dovecot 1.1.15 on OpenBSD 4.4. How can I debug this? # /usr/local/sbin/dovecot --exec-mail ext /usr/local/libexec/dovecot/expire- tool Segmentation fault (core dumped) # gdb /usr/local/sbin/dovecot (gdb) run --exec-mail ext /usr/local/libexec/dovecot/expire-tool Starting program: /usr/local/sbin/dovecot --exec-mail ext /usr/local/libexec/dovecot/expire-tool Program received

Thanks Buddy, I got it working. It was giving error when running make 'undefined reference to `request_init' etc' then I ran it with gmake LDFLAGS+=-lwrap and it worked and everything is working fine. Thanks again for your help Thankyou Tahir Riaz Assistant Director (Systems) COMSATS Internet Services COMSATS Headquarters Building 9, Shahrah-e-Jamhuriat, G-5/2 Islamabad.

Hello, I'm using dovecot and I want to use the "expire" plugin. However, it doesn't work, i.e. mails do not get deleted. I ran `/usr/sbin/dovecot --exec-mail ext /usr/libexec/dovecot/expire-tool --test` and besides printing Info: stef/Trash: no messages left Info: stef/Spam: no messages left it doesn't do anything (especially not deleting e-mails). Obviously, in

Hi! Here is the problem: passdb: daniell:*::::::user=daniell2 userdb: daniell2::uid:gid:gecos:home:: dovecot.conf: plugin { expire = SA.* 1 # (There are SA.HAM and SA.SPAM directories) } When copying a message to eg. the SA.HAM directory, then dovecot inserts this into my expires table: dovecot=# select * from expires ; username | mailbox | expire_stamp

Expire plugin / expire-tool seems annoyingly inflexible currently, so I was thinking about a more generic redesign: The expire plugin keeps track of the oldest message in configured mailboxes. Its only configuration is the list of tracked mailboxes. There's no configuration like what the expire timeouts are or anything. There will be a new doveadm command: doveadm expunge [-u user | -A]

Hi, I'm running dovecot 1.2.11 on Centos and have the expire plugin enabled. I've had this in place for some time but until now never actually ran the expire-tool. I'm now trying to put this to use. The expire plugin as such is working fine and also the tool is working fine - up to a point. When I run it with --test it goes through a bunch of boxes and lists the messages it

Hi, I try to get expire working, with the BDB backend and mbox mailboxes. If I try to invoke the expire-tool like /usr/local/sbin/dovecot --exec-mail ext /usr/local/libexec/dovecot/expire-tool --test I get [root at m ~]# /usr/local/sbin/dovecot --exec-mail ext /usr/local/libexec/dovecot/expire-tool --test Error: read(/var/run/dovecot/dict-server) failed: Remote disconnected Hmm. I searched

Hi - Though I'm not sure whether anyone will be interested in such tool (other than a possible SO user [1]). Here is a small tool to delete files at specific time in future. https://github.com/Lakshmipathi/expirer https://github.com/Lakshmipathi/expirer/blob/master/misc/ISSUES [1] http://programmers.stackexchange.com/questions/149824/automatically-delete-files-after-they-expire -- ----

Hi, I'm having some trouble getting the expire plugin to work, and I'm not sure where to turn for troubleshooting. This is on 1.2rc3. To my dovecot.conf, I've added: mail_plugins = expire under the protocol imap and lda sections. I also added: dict { expire = mysql:/etc/dovecot/dovecot-dict-expire.conf } plugin { expire = Trash 30 Trash/* 30 Spam 30 expire_dict =

Hi, I am on dovecot 1.1.11 trying to figure out the expire tool .... The thing is that when I had confed the exp tool there where a bunch of mails inside the mail boxes. Thus it seems as if the database is not updated about them. Is there a way to update it from command line to include the old mails ??? Thanks Harry

Trying to implement expire plugin. expire-tool works fine. This delete expunged messages but not all of them. I have duplicate messages in appropriate folder. These messages are from expanding postfix aliases (e.g. postmaster@, hostmaster@, abuse@ etc. points to same mailbox and spam often sent to all of them. If duplicate message is received only one entry in dovecot-uidlist is created and only

$ /usr/sbin/dovecot --exec-mail ext expire-tool --test Info: Trash: timestamp 1243963680 (Tue Jun 2 19:28:00 2009 ) -> 1244307774 (Tue Jun 2 19:28:00 2009 ) Both human readable timestamps are equal as ctime() returns a pointer to a static buffer. In addition there are some newline characters added by ctime(). The following patch is a try to fix this for 1.2.rc5. --- expire-tool.c.orig

Hi! I've upgrade from 1.1 to 1.2, and one thing I noticed, that when running expire-tool, I get this error: # /usr/local/sbin/dovecot --exec-mail ext /usr/local/libexec/dovecot/expire- tool Info: Loading modules from directory: /usr/local/lib/dovecot/imap Info: Module loaded: /usr/local/lib/dovecot/imap/lib10_quota_plugin.so Info: Module loaded:

Hi, In order to periodically deal with corrupted index files in Dovecot, we routinely will remove a users .imap folder in order to have the indexes rebuild. This hasn't ever caused a problem previously. However, removing the user's index files seems to break the ability of the expire plugin to update the expire stamp correctly, or expunge mail from the user folder. This seems logical,

Hi Timo, not long ago you fixed a bug regarding the expansion of ~/ in mail_location that prevented expire-tool from working correctly. A similar problem exists if mail_location contains %h: expire-tool will use the wrong path to access the mailbox. After replacing %h with ~, expire-tool works as expected. Why are there two variables for the home directory? Maybe the use of %h could be

Hello, I've just subscribed to the list, as a recent user of Dovecot (1.2.4 by now). I eventually missed a point, so I tried to find other doc or comments about my issue, but failed to. If the following has already been discussed, please simply reply with a URL to the corresponding thread or doc ;-) Now that I have covered my ass, here is the problem I meet. In dovecot.conf, I have the

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

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