Re: Cyrus Sieve/Notifications
Jeremy Howard wrote: > > > Try 'denotify' in your sieve script, you can then explicitly call > > 'notify' when you want. I *think* that cmu-sieve has an implicit > > 'notify' unless explicitly turned off. > > > But doesn't the notify daemon get called for every message regardless of > what Sieve says? ...Because that's how it works for Zephyr? I might be wrong > here--corrections welcome. I'm particularly thinking of what happens for > users that have no Sieve script at all (which is 99% of our users). So you want to disable notify for ALL users without a Sieve script? AFAIK you can't right now. We can make this an imapd.conf option. Would you mind filing this in bugzilla, so I (we) don't forget? Actually, would you mind filing a bug for the vacation response From: address as well? Thanks, Ken -- Kenneth Murchison Oceana Matrix Ltd. Software Engineer 21 Princeton Place 716-662-8973 x26 Orchard Park, NY 14127 --PGP Public Key--http://www.oceana.com/~ken/ksm.pgp
Re: Cyrus Sieve/Notifications
> Try 'denotify' in your sieve script, you can then explicitly call > 'notify' when you want. I *think* that cmu-sieve has an implicit > 'notify' unless explicitly turned off. > But doesn't the notify daemon get called for every message regardless of what Sieve says? ...Because that's how it works for Zephyr? I might be wrong here--corrections welcome. I'm particularly thinking of what happens for users that have no Sieve script at all (which is 99% of our users).
Re: Cyrus Sieve/Notifications
Jeremy Howard wrote: > > 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. Try 'denotify' in your sieve script, you can then explicitly call 'notify' when you want. I *think* that cmu-sieve has an implicit 'notify' unless explicitly turned off. Note that the current cmu-sieve implementation does not correspond with the current draft (-03). I think it implements what was -01. Ken -- Kenneth Murchison Oceana Matrix Ltd. Software Engineer 21 Princeton Place 716-662-8973 x26 Orchard Park, NY 14127 --PGP Public Key--http://www.oceana.com/~ken/ksm.pgp
Re: Cyrus Sieve/Notifications
I suppose I should have noted that I DO have the Perl daemon running (simple_notify.pl). I have only seen an entry in my logs one time (aside from the daemon start/stop messages), and one time only. It has not worked since, and I have no idea what was different. In fact, the log entry doesn't seem to have occurred when any e-mail actually arrived, since it has no information regarding the e-mail. Basically, I'm just having problems getting the socket daemon to actually respond when I get e-mail. It seems like nothing is wrong at all with my implementation, or at least there are no logged errors. I suppose what I'm asking is basically some sort of instruction list, pointing out something I may have missed. Thank you for your help. James Jeremy Howard wrote: >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 >> >> >
Re: Cyrus Sieve/Notifications
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 > >
