Turns out imclient (at least in the latest RHEL7 pkg) is hardcoded to
use TLSv1. Since we're building binary RPMs from Source RPMs anyway we
modified imclient.c, rebuilt the RPMs, reinstalled the cyrus-imapd-utils
package: Here's the patch we used:
--
Hi All,
We're hoping to find some help on the list...
We are running Cyrus-IMAP on RHEL7, using an RPM pkg
(CYRUS-IMAPD-2.4.17-13.EL7) built from the Red Hat SRC RPM. We also
have SASL, Utils, devel etc pkgs all from RH.
Now we're looking to finally move Cyrus completely off insecure TLS
ver
notably:
http://blog.fastmail.fm/2007/09/21/reiserfs-bugs-32-bit-vs-64-bit-kernels-cache-vs-inode-memory/
Anyone have any specific thoughts? Is there any other benefit we might
see from large memory allocation in 64-bit architecture?
Thanks,
John Widera
Oakton Community College
Des Plaines an
Thanks all, for the input. My post had a typo - we aren't currently on
RHEL 5. We're on RHEL 3. RHEL 3/i386 to RHEL 5/x86_64 is the exact path
we are going.
We're already running skiplist across the board so based on what we've
read/heard we don't expect any trouble in that regard.
Our plan is
> Hello,
>
> I'm searching for months without success for either one of these solutions
> :
>
> a) Out-of-office (away) plugin for Outlook that would use Sieve ?
>
> b) Web interface to manage an out-of-office message in Sieve ?
Websieve? Easysieve?
>
> If someone could give me some advice, it w
tion experience with running Cyrus in
a virtual (ESX?) env., and/or experience with running Cyrus (Simon
Matter's RPMs, optimally) in a 64-bit Linux OS?
We'd really appreciate hearing from people before we go much further in
the planning stage. Thanks.
John Widera
jwidera #at# oakton #dot