The little Perl scripts are Unix socket daemons. You need to run one of them (start with the one that just does logging) and then check that stuff appears in your logs when you deliver mail. Also make sure that the directory exists that the Unix socket daemon is using (there are constants at the top of the Perl code that specify the directory), and that Cyrus has read/write permissions there.
BTW, although I contributed that code I've never used it in production, and it has a known problem if headers are >2k (just fix the printf() in unix_notify.c if this is a problem for you). I'm planning on finally rolling out something that uses this in a couple of months, so it will be more actively supported then. *** And now a question to anyone who's actually using this... How do I get notify() called only when requested in a Sieve script, rather than every time like happens with Zephyr. I know that I can just check in my Perl daemon how it's been called, but this is a lot of extra overhead when the fast majority of users will not have any notification set up in their Sieve script. ----- Original Message ----- From: "Jewfish" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, October 19, 2001 6:05 AM Subject: Cyrus Sieve/Notifications > Hello. > > I am new to this -info list, but I have been using Cyrus IMAPD for > several months now, and really enjoy it. Just a few days ago, I was > able to work on getting Sieve working, and it works quite well. The > only problem is that I wish to get notifications working. I compiled > cyrus --with-notify=unix, but I have no idea where to go from here! I > have the "simple perl scripts" from the contrib/notify_unix directory, > also, but whenever I send an e-mail to myself, I don't see any > notification happening. Any hints/suggestions/solutions/sample code? I > am quite lost right now, and I hope some of you can be helpful. > > Thanks in advance! > James > >
