On Wed, 2005-02-02 at 11:08 -0600, Aleksandar Milivojevic wrote: > Craig White wrote: > > On Wed, 2005-02-02 at 10:26 -0600, Aleksandar Milivojevic wrote: > > > > > >>>me scratches head and thinks it's time for coffee > >> > >>The arguement for '-e' is the script itself, not the file containing the > >>script: > >> > >>sieveshell localhost -u craig -e "delete lists; put > >>/home/craig/lists.script lists; activate lists" > > > > --- > > afraid coffee has let me down today... > > > > # /usr/bin/sieveshell localhost -u craig -e "delete lists; \ > > put /home/craig/lists.script lists; activate lists" > > connecting to localhost > > Please enter your password: > > delete <name> - delete script. > > > > #was all on one line and I manually added \ because of mail wrap. > > > > but script is definitely there... > > > > # sieveshell localhost -u craig > > connecting to localhost > > Please enter your password: > > > >>list > > > > .sieve > > lists <- active script > > lists_pseudo > > > >>quit > > My bad, again... ";" isn't command separator... Don't know what is (if > anything is). But if you type it multiline (as shown below), it worked: > > smartsieve localhost -u craig -e "delete lists > put /home/craig/lists.script lists > activate lists" ---- indeed it does... # cat test #!/bin/sh /usr/bin/sieveshell localhost -u craig -e "delete lists put /home/craig/lists.script lists activate lists" boy - that's clumsy... now - on to automation to get sieve scripts automatically imported into new users... Thanks Craig
