After Action Hooks

Ken Murchison ken at
Sat Sep 11 17:18:40 EDT 2004

Drew Morris wrote:
> Hello all,
> I was wondering if it would be possible to add after action hooks into
> Cyrus-IMAP/POP so that upon any change to a mailbox (folder move,
> folder rename, folder deletion, message addition, message deletion,
> message move, etc.) I would be able to fire an action like a perl
> script or some other program. The script would need to know which user
> this was performed on, the command, the element type (folder or
> message), and the unique ID of the element. This feature would be
> extremely useful for mail automation.
> In my case, I want to mainain a cache of message metadata that is kept
> in synch with the Cyrus message store pro-actively without having to
> keep calling synch functions on each mailbox. The idea would be for
> these "after action hooks" to fire off an asynchronous process that
> would be able to update the cache so that if a user looked at the
> cache they would see an up-to-date version of their data.

Is this cache on the same machine, or different machine?

If you're trying to cache data to improve performance, don't bother. 
Cyrus already maintains a cache of message metadata for each mailbox in 
cyrus.index and cyrus.cache.  The full message file is only read when 
part of the body or some obscure header is requested.

Kenneth Murchison     Oceana Matrix Ltd.
Software Engineer     21 Princeton Place
716-662-8973 x26      Orchard Park, NY 14127
--PGP Public Key--
Cyrus Home Page:
Cyrus Wiki/FAQ:
List Archives/Info:

More information about the Info-cyrus mailing list