Juan Leon writes:
>
> I am trying to install a cyrus that works with Mulberry and
>Netscape. I got both 2.0.9 and 1.6.24 working with Mulberry
>with DIGEST-MD5, etc. But none gives me PLAIN for Netscape (or
>Mulberry). SASL's sample-server reports that SASL is offering
>everything except ANONYMOU
I have tried about a million things. I am going to rant a bit
hoping that something rings a bell and some advice miraculously
pours forth. This is with SASL 1.5.24, cyrus 1.6.24 and 2.0.9,
Linux 2.2.16 (RH 7.0). I will be eternally grateful if you can
help.
I am trying to install a cyrus that
I had to go through the same issue. This is what I had to do (if my notes
are correct):
1. cd /usr/local/lib/perl5/site_perl/5.005/i586-linux
2. mv Cyrus /usr/lib/perl5/site_perl/5.005/i586-linux/
3. mv auto/* /usr/lib/perl5/site_perl/5.005/i586-linux/auto
Avi
--On Tuesday, January 16, 2001
Karlheinz
I'm sure about the perl problem. My guess is a missing perl module ;-)
But you can create a user mail box using ( as the cyrus user) >createmailbox
user.freddy
you can then also use >listmailbox user.freddy
The user authentication credentials must be set up for the user to login, how
Cheers Ken,
Thanks for speedy patch.
Regs
Chris
Linux System Admin
Hinterlands Aust.
Ken Murchison wrote:
> John,
>
> Forget about my last message, here is the fix. This was stupid, I don't
> know how I missed this. I must have changed the signal disposition at
> the last minute without test
Hi,
I've successfully (partially) installed Cyrus 2.0.9 on SuSE 7.0. Imtest
is working. But so far I've been unable to execute cyradm.
The following error message appears:
Can't locate Cyrus/IMAP/Shell.pm in @INC (@INC contains:
/usr/lib/perl5/5.00503/i586-linux /usr/lib/perl5/5.00503
/usr/
John Holman wrote:
>
> (Follow up to last message)
>
> In fact the IDLE problem is quite general. If the client has used the IDLE
> command, it seems that the imapd process will be killed and the connection
> closed with "signalled to death by 14"
> whenever more than about 50 seconds passes b
(Follow up to last message)
In fact the IDLE problem is quite general. If the client has used the IDLE
command, it seems that the imapd process will be killed and the connection
closed with "signalled to death by 14"
whenever more than about 50 seconds passes between commands sent by the
client.
My posting yesterday described a bug in Cyrus 2.0.9 that causes loss of
messages in the source mailbox after the server aborts a copy command with
message "signalled to death by 14".
Here is some more information about the circumstances under which the copy
command is aborted in the first place.