On Wed, 2005-02-02 at 07:28 -0700, Craig White wrote: > On Tue, 2005-02-01 at 13:07 -0500, Bob Chiodini wrote: > > On Tue, 2005-02-01 at 09:03 -0700, Craig White wrote: > > > On Tue, 2005-02-01 at 09:35 -0600, Aleksandar Milivojevic wrote: > > > > Craig White wrote: > > > > > put the following line in /etc/imapd.conf > > > > > #sieveusehomedir: 1 > > > > > > > > > > and restarted cyrus-imapd and this didn't go over very well > > In /usr/share/doc/cyrus-imapd-2.2.10/install-sieve.html there is a > > mention that sieveusehomedir is incompatible with timsieved. Other > > references in that directory mention running sieve to possibly compile > > the script into byte code. I think something other than timsieved would > > have to run to process the script. Possibly from deliver. > > > > Otherwise I see the same errors as you. I'll look more into it when I > > get some free time. > > > ---- > yeah - I have pretty much given up on the sieveusehomedir option since > just putting the file there doesn't do much - it still has to be > processed by sieveshell or some sieve process to bytecode it. This makes > the location of the file less relevant - but since you can script the > sieveshell stuff, I suppose you could put a script in the users home > directory and run a shell script that invokes sieveshell in the users > name, put (pulls it in in sieveshell lingo) activates it and bails > > Craig > Craig, That's pretty much how I'm doing it. What about the password prompt, when running from a script? Bob...