You could try running sieveshell, which may have better diagnostics. Also,
depending on whose RPMs you are playing with, there may be a separate
perl-Cyrus-2.0.16 RPM to keep in sync (check with " rpm -qf
/usr/lib/perl5/site_perl/5.6.0/i386-linux/Cyrus/SIEVE/managesieve.pm"). We
may be using different RPMs, so our experiences will vary.
Another thing: my experience was that sieve tries to write into
/usr/sieve/<letter>/user by default, and will get upset if
/usr/sieve/<letter> is absent (<letter> is a-z). You can change the
directory by adding a sievedir entry in /etc/imapd.conf.
Chris
On Wed, 26 Dec 2001, Matt Kenigson wrote:
> Yeah, we've got an exactly identical entry in our /etc/cyrus.conf file. I'm
> stumped.
>
> Matt
>
> ----- Original Message -----
> From: "Christopher Wong" <[EMAIL PROTECTED]>
> To: "Matt Kenigson" <[EMAIL PROTECTED]>
> Sent: Wednesday, December 26, 2001 10:32 AM
> Subject: Re: Fw: cyrus info list
>
>
> > I forgot to mention that you check /etc/cyrus.conf to make sure Sieve is
> > enabled. The following is my own /etc/cyrus.conf file. Yours may vary
> > depending on the paths of the binaries, but you would want some sort of
> > entry for Sieve in the SERVICES section below.
> >
> > Chris
> >
> > ---------------------------------------------------
> >
> > # standard standalone server implementation
> >
> > START {
> > # do not delete these entries!
> > mboxlist cmd="ctl_mboxlist -r"
> > deliver cmd="ctl_deliver -r"
> > }
> >
> > # UNIX sockets start with a slash and are put into /var/imap/socket
> > SERVICES {
> > # add or remove based on preferences
> > imap cmd="/usr/cyrus/bin/imapd" listen="imap" prefork=0
> > imaps cmd="/usr/cyrus/bin/imapd -s" listen="imaps" prefork=0
> > pop3 cmd="/usr/cyrus/bin/pop3d" listen="pop3" prefork=0
> > pop3s cmd="/usr/cyrus/bin/pop3d -s" listen="pop3s" prefork=0
> > sieve cmd="/usr/cyrus/bin/timsieved" listen="sieve" prefork=0
> >
> > # at least one LMTP listener is required for proper delivery
> > # lmtp cmd="lmtpd" listen="lmtp" prefork=0
> > lmtpunix cmd="/usr/cyrus/bin/lmtpd" listen="/var/imap/socket/lmtp"
> > prefork=0
> > }
> >
> > EVENTS {
> > # this is required
> > checkpoint cmd="ctl_mboxlist -c" period=30
> >
> > # this is only necessary if using duplicate delivery suppression
> > #delprune cmd="ctl_deliver -E 3" period=1440
> > }
> >
> > On Fri, 21 Dec 2001, Matt Kenigson wrote:
> > > Howdy,
> > >
> > > I'm forwarding this message for a colleague.
> > >
> > > Incidentally, this is an RH7.2 system with the cyrus-imapd-2.0.16-5 RPM
> > > installed.
> > >
> > > Does anyone have any ideas on how to proceed, or some documentation we
> could
> > > look up? We're running out of ideas over here.
> > >
> > > Thanks,
> > >
> > > Matt Kenigson
> > > president (at) sheergenius.com
> > >
> > > ----- Original Message -----
> > > From: "Allen Minix" <[EMAIL PROTECTED]>
> > > To: "Matt Kenigson" <[EMAIL PROTECTED]>
> > > Sent: Friday, December 21, 2001 3:38 PM
> > > Subject: cyrus info list
> > >
> > >
> > > > I tried subscribing to the info-cyrus list, and still have as of yet
> to
> > > > get a confirmation. Here is what I'm getting when trying to run
> > > > installsieve to list the current sieve scripts. Any function that I
> try
> > > > to invoke with installsieve produces this error.
> > > >
> > > >
> > > > [root@vcch243 sieve]# installsieve -l -u cyrus localhost
> > > > Please enter your password: blahblah
> > > > Unable to connect to server at /usr/bin/installsieve line 121, <STDIN>
> > > > line 1.
> > > >
> > > >
> > > > Thanks,
> > > >
> > > > -Allen
> > > >
> > > >
> > >
> > >
> >
> >
>
>
