Yeah, so tls to localhost is dumb. That's security theatre at its silliest.
Best to turn that off.
Here's some possibilities to make it not required:
imapd.conf:
allowplaintext: yes
sasl_mech_list: PLAIN LOGIN
There used to be a sasl layer thing we did too... "-p 1" in cyrus.conf for the
ima
Rudy,
Entropy is 158 I just looked. And as far as compiling against urandom, to be
honest I'm
not sure.
- Paul
> On Sep 6, 2015, at 9:50 PM, Rudy Gevaert wrote:
>
>
> Quoting signaldevelo...@gmail.com, Mon, 07 Sep 2015:
>
>> Hosts file is fine I checked that, thanks. Kolab uses 389 to
Hey Rudy!
As far as entropy: Probably not, it's brand new. One user (me.. Testing) is
playing on it. This is something I've never touched and know very little about,
can you explain?
And can you explain: Is saslauthd compiled against /dev/urandom?
Thanks again guys..
- Paul
Sent from my
Quoting signaldevelo...@gmail.com, Mon, 07 Sep 2015:
> Hosts file is fine I checked that, thanks. Kolab uses 389 to
> authenticate for everything, so Cyrus is using LDAP as you can see
> above. I think the problem lies in the constant TLS logins into
> Cyrus for every click:
>
> imap[2281]:
Haha hey bron. Sorry, I'm a 24/7 workaholic. :)
I don't think it's IO. It's a VM on a HA cluster. The node its on is 64GB of
RAM, I have 1 user and assigned everything to it for now. Everything else runs
beautifully on it the identical nodes. I have similar setups (non kolab) that
run off of do
On a Sunday night? Not really.
So Cyrus itself isn't this slow unless you have a horrible IO system
under it or so little RAM that you can't fit the entire index into
memory and it goes swapping.
A possible issue would be failed DNS resolution on every connect, so you
could check your hosts file
Anyone have any ideas on this?
On Sat, Sep 5, 2015 at 10:22 PM, Paul Bronson
wrote:
> Okay guys, I have put a lot of research into this so bear with me.
>
> Here's what I am up against. I have been working with RC (roundcube) for a
> long time and I know some awesome mySQL tweaks that work wonde