|
Wolfgang Hennerbichler wrote: > On Tue, Feb 15, 2011 at 07:33:41AM -0500, Dave McMurtrie wrote: > > > * does notifyd need to be running in order to make the notify-socket > > > readable, or is the notify-socket filled by the cyrus-master process? > > > * where would I find instructions on that? > > > > You want to set the notify_external option in imapd.conf and point that > > at a program (script, binary, whatever) that you write. notifyd will > > fork/exec your program and pass it -c, -p, -u and -m command line > > arguments. Your program can then to whatever custom notification you > > want it to. > > > > This was added in the 2.4.x series. The imapd.conf option is documented > > in the imapd.conf manpage ... > > thanks! too bad I do still have 2.2 running (debian squeeze), and I was too > lazy for now to find a good package maintainer or compile by myself. So I > guess I'm stuck by now. > I have some vanilla packaging effort for Debian ongoing on http://git.kolabsys.com/apt/cyrus-imapd/log/?h=cyrus-imapd-2.4, in case you're interested. Though I'm dealing with a small backlog, compiled packages may be found at http://mirror.kolabsys.com/pub/debian/kolab-3.0/pool/development/c/cyrus-imapd/ Kind regards, Jeroen van Meeuwen -- Senior Engineer, Kolab Systems AG e: vanmeeuwen@xxxxxxxxxxxx t: +316 42 801 403 w: http://www.kolabsys.com pgp: 9342 BF08 |
---- Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
