"Matthew Hoskins" <[EMAIL PROTECTED]> writes:
> Did you compile with SSL support? If not, you don't need
> the -s option
Yes, I asked for openssl (see below), and would like to have
it. (I am also mildly curious why Fairly Obvious C code
does something entirely different from what I would expe
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Simon Matter
> Sent: Tuesday, May 07, 2002 1:30 AM
> To: jeff bert
> Cc: [EMAIL PROTECTED]
> Subject: Re: saslauthd: /var/state/saslauthd: No such file or directory
>
>
> jeff bert schrieb:
> >
> > Afte
Did you compile with SSL support? If not, you don't need the -s option
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Will Partain
Sent: Tuesday, May 07, 2002 12:17 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: 2.1.4, linux-rh7.2: the "imapd:
I'm running 2.1.4 on a well-patched ia32-linux-rh7.2 box;
the only oddity being that 'master' spits out
"imapd: invalid option -- s" every time it tries to start up
"imapd -s". You get the same message if you go to the
build directory and type 'imap/imapd -s' thusly:
partain$ ./imap/imapd -s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'd like to announce the release of Cyrus SASL 2.1.3-BETA on
ftp.andrew.cmu.edu. This version includes a significant cleanup of all of
the included plugins, some major bug fixes, an LDAP saslauthd module,
support for DIGEST-MD5 reauthentication, and m
On Tue, 7 May 2002, Dor S. wrote:
[ you posted this to the sasl list, I'm cc-ing this to the info cyrus list
instead. ]
> Hey again,
> Now I installed Berkeley DB 3.3.11 and I get a new compiling error:
>
> ### Making all in /root/cyrus-imapd-2.0.16/perl/imap
> make[2]: Entering directory `/
Ok
Will try this week any way and will try write something
P.
> -Original Message-
> From: Lawrence Greenfield [mailto:[EMAIL PROTECTED]]
> Sent: mardi 7 mai 2002 11:53
> To: David Wright
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: Migrate From 2.0 to 2.1.4
>
>
> If some
If someone tries Ken's instructions and finds problems (or it works)
I'd really appreciate them being written up in HTML for inclusion into
the doc/ directory.
thanks,
Larry
After upgrading from 2.1.3 to 2.1.4 I see defunct processes after cyrus
startup. They're going away after the first pop3/imapd access and it
doesn't hurt.
The changelog says:
* master has preliminary code to avoid forking storms.
Is this because of the new feature?
ps shows:
8553 pts/0S
David Wright wrote:
>
> > doc/install-upgrade.html
>
> This information assumes you are upgrading on one box. My situation (and
> I suspect it is the situation of most production systems) is having 2.1
> set up clean (i.e. no mail or metadata) on a second machine, and now I
> want to get all t
Hello !
I've two Cyrus Imapserver both 1.6.22. I've upgraded the first to 2.0.16
(successfully). What will be the easiest way to transfer the second imapserver
to the first in regards of the mailbox.db. I think that I will simply copy the
/var/spool/imap/user/* files to the first server. Als
Simon Matter wrote:
> jeff bert schrieb:
[...]
>>No I use Linux Mandrake 8.1
[...]
> Okay, Mandrake and RedHat differ. If you're running Mandrake you may
> want to use Luca Olivetti's RPMs from
> http://perso.wanadoo.es/olivetti/cyrus/
my packages are made for mandrake 8.2, I didn't test them w
jeff bert schrieb:
>
> After installing cyrus-imapd-2.1.4 and cyrus-sasl-2.1.2 and trying to start
> up saslauthd I get this error message:
>
> saslauthd: /var/state/saslauthd: No such file or directory
Hi,
You really don't give us much info about your system.
It seems your init script for sas
jeff bert schrieb:
>
> > Simon wrote:
> >
> > Did you install on RedHat 7.2? If yes, make sure you have current
> > updates installed, if no, I don't know.
> >
>
> No I use Linux Mandrake 8.1
>
> > This is what I have installed:
> >
> > [root@dhcp-141-104 SRPMS]# rpm -qa | grep cyrus
> > cyrus-
14 matches
Mail list logo
