Automatic removal of messages over NN days present in a folder.
At our site we expire Spamboxes after 45 days. Messages arrive in Spamboxes by auto-triage at delivery time or when a user moves a false negative into it. I was thinking of generalizing the 'Trash' concept with a similar automatic expiry but it appears Cyrus doesn't quite have the necessary tool(s) for this. Imagine the Trash folders being auto-emptied after 45 days. Imagine a message sitting in a user mailbox for 50 days and which now gets moved to Trash. The idea is to not have this message removed from the server the following night but to have the countdown starting at the time of moving it to Trash. Any ideas/suggestions for a neat solution or workaround ? FWIW : this is Cyrus 2.2.13 Thx, Eric. Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Cyrus IMAPd 2.3.13 Released
I am pleased to announce the release of Cyrus IMAPd 2.3.13. This release should be considered production quality. Noteworthy changes: * Added an experimental sql backend for cyrusdb. Currently MySQL, PostgreSQL, and SQLite are supported. * Added support for IMAP [CAPABILITY] response code to client-side of Murder proxies. * Added support for ManageSieve auto-capability response after STARTTLS and after AUTH with a SASL security layer. * Made MAXWORD and MAXQUOTED sizes configurable via imapd.conf * Rewrote cyrusdb_quotalegacy.c to use readir() rather than glob.c. This avoids a potential crash due to conflicts between glibc and Heimdal implementations of glob(). * Added support for fulldirhash to 'ctl_mboxlist -v' * Several skiplist transaction bugfixes. * cyr_expire no longer has a default of 0 (zero) for -X and -D. These options must be used explicitly in order to have the desired effect. * Added sieve_utf8fileinto option. * Added sieve_sasl_send_unsolicited_capability and sieve_sasl_expect_unsolicited_capability options. * Several 32/64-bit compatibility fixes. For full details, please see doc/changes.html and doc/install-upgrade.html which are included in the distribution. URLs for this release: ftp://ftp.andrew.cmu.edu/pub/cyrus/cyrus-imapd-2.3.13.tar.gz or http://ftp.andrew.cmu.edu/pub/cyrus/cyrus-imapd-2.3.13.tar.gz Questions and comments can be directed to info-cyrus@lists.andrew.cmu.edu (public list), or [EMAIL PROTECTED] -- Kenneth Murchison Systems Programmer Project Cyrus Developer/Maintainer Carnegie Mellon University Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Automatic removal of messages over NN days present in a folder.
You're thinking of modifying ipurge to do this? Sounds like a nice idea. Messages are moved to Trash with COPY, and COPY retains the original INTERNALDATE. However, the last_updated is set to NOW on COPY, so that's probably what you want. ipurge currently supports SENTDATE and INTERNALDATE. A cursory review suggests that adding LAST_UPDATED is trivial -- not that I've tested it :) Is there some reason you're not running 2.3.x? I'm not aware of any plans to make new 2.2.x releases, certainly not for feature enhancements. :wes On 20 Oct 2008, at 05:41, Eric Luyten wrote: I was thinking of generalizing the 'Trash' concept with a similar automatic expiry but it appears Cyrus doesn't quite have the necessary tool(s) for this. Imagine the Trash folders being auto-emptied after 45 days. Imagine a message sitting in a user mailbox for 50 days and which now gets moved to Trash. The idea is to not have this message removed from the server the following night but to have the countdown starting at the time of moving it to Trash. Any ideas/suggestions for a neat solution or workaround ? Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
INBOX folder not available
Hi list, under Linux Debian Etch and Cyrus Imap 2.2.13-10, I planned to synchronize ACLs between too IMAP servers, using imap. This works fine for almost mailboxes, except for very few of them. Symptoms : -1- the IMAP command SELECT does not work on the INBOX folder. (when it works for the huge majority). Non working example : 02 SELECT INBOX 02 NO Mailbox does not exist Working example : 02 SELECT INBOX * FLAGS (\Answered \Flagged \Draft \Deleted \Seen) * OK [PERMANENTFLAGS (\Answered \Flagged \Draft \Deleted \Seen \*)] * 6 EXISTS * 0 RECENT * OK [UIDVALIDITY 1114023713] * OK [UIDNEXT 24] 02 OK [READ-WRITE] Completed -2- The same box can be subscribed to, receives mails and so on and seems to be fully functionnal, even XFER works. Reconstruct on the box did no better. -3- With imapsync (Revision: 1.172), the answer for the From folder is [INBOX] when usually [INBOX] Any other solution than recreating it? -- Best regards, - Laurent Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
