We are running Cyrus 2.2.13, and I recently noticed that we have many
imapd processes on the server, dating back to the day that the server
was last booted, which was over 3 months ago.
The entries for many of them in /var/imap/proc look like this:
> 249.sub-174-253-10.myvzw.com [174.253.10.24
Just wondering if work is still being done on Cyrus.
I have sent repeated messages to cyrus-bugs without an answer; there
seem to be serious flaws with the integration of SASL 2.1.1 with cyrus
2.1.1, but without help from the CMU folks I don't have any idea.
We are getting ready to cut over a 10
I have my 2.0.9 sendmail 8.11.1 test server up and running, and happily
serving me my mail so far for about a week without problems.
My cohorts have cold feet about moving our user database over there,
though, because of the additional complexity of managing the SASL
username/password pairs as "y
"William K. Hardeman" wrote:
>
> Brian,
>
> Cool. Someone else that's using a Slackware system. Mine is
> Slackware-current. :)
>
That's an easier (but not yet quite painless) system to do an install on
than S/W 7.0, which is what this machine is running. I am, I think, the
"original user fro
I just finished installing cyrus 2.0.9 on a Slackware Linux system. I
had the same problems reported earlier today getting cyradm to install
properly; I finally resorted to going to another machine running an
earlier beta (2.0.7) and then manually copying files out of the ~/perl
directory into th
I'm testing out the latest Slackware distribution with the 2.0.7 version
of Cyrus, along with the latest version of SASL.
I have tested and verified that sasl is working all right, at least
through the ability to add users to the sasldb and see them, etc.
I can start the master just fine, but wh
