Hi
> Also worth mentioning in the FAQ is that it's a good idea to kill the
master
> process before running 'make install' to ensure that everything is
replaced
> properly.
Thanks, I've added it.
> PS: Tarjei, could you please adjust your mailer so that it wraps your
lines
> to 72 chars or thereab
Ken Murchison wrote:
> Tarjei Huse wrote:
> > One last question, I know I've asked it before, but I realy want an
answer (it's for the faq). If I download cyrus 2.0.16 and build it with the
same config as the last time. Then a make install will only overwrite
binarys and libs, and not the .conf fi
Two questions:
1. Sieve listening on a port, that is just for administrative work, the sieve service
does not have anything to do administratively. And so I can set
sieve cmd="/usr/cyrus/bin/timsieved" listen="localhost:sieve" prefork=0
And let my users use websieve, right?
Also, the
Tarjei Huse wrote:
>
> Two questions:
> 1. Sieve listening on a port, that is just for administrative work, the sieve
>service does not have anything to do administratively. And so I can set
>sieve cmd="/usr/cyrus/bin/timsieved" listen="localhost:sieve" prefork=0
> And let my users
Amos Gouaux wrote:
>
> th> What I am wondering about, is the imaps line. How can I say: "bind to these two
>interfaces ip1,ip2"? is is listen=(192.168.1.2,195.204.129.18):imaps os should I have
>to imaps:
> th> imaps cmd="/usr/cyrus/bin/imapd -s" listen="192.168.1.2:imaps"
>prefork
> On Sun, 12 Aug 2001 16:19:20 +0200,
> Tarjei Huse <[EMAIL PROTECTED]> (th) writes:
th> Hi All.
th> Pardon me, but new cyradm?
th> I this a new cyradm for 2.0x? or +??
2.x (actually a recent CVS pull of cyrus-imapd). In 1.x the cyradm
interactive utility was a Tcl extension. With 2
