>>> The other option I ran into some time ago... and it had to due to
>>> defining multiple authentication schemes in the SASL configuration.
>>> When you define multiple, it will try each one in order. I stripped
>>> it down to just PLAIN, which is what I wanted to use, and it was
>>> much quicke
On 25.02.2009, at 01:15, Iv Ray wrote:
> On 25.02.2009, at 00:28, Raymond T. Sundland wrote:
>
>> The other option I ran into some time ago... and it had to due to
>> defining multiple authentication schemes in the SASL configuration.
>> When you define multiple, it will try each one in order. I
On 25.02.2009, at 00:28, Raymond T. Sundland wrote:
> I have two possible fixes, not sure if either will work...
>
> The first possible is if your system is configured for IPv6, but
> Cyrus is not opening a port on any IPv6 addresses, if you just type
> 'localhost', it will likely try the IPv6
On 25.02.2009, at 00:02, Andrew Morgan wrote:
> Are all operations slow, or only authentication?
Only the coming of the localhost> prompt.
I assume this is the authentication...?
> Your best tool for testing is imtest. You can issue raw IMAP
> commands and see how long they take.
Oh, I'll
I have two possible fixes, not sure if either will work...
The first possible is if your system is configured for IPv6, but Cyrus
is not opening a port on any IPv6 addresses, if you just type
'localhost', it will likely try the IPv6 address first and the timeout
is probably in the 20-25 second
On Tue, 24 Feb 2009, Iv Ray wrote:
> Hello everyone,
>
> A few weeks ago I wrote to the list about slow Cyrus IMAP, and I
> received a couple of answers, however I am still struggling.
>
> What I noticed now is that even the command line login -
>
> cyradm -u cyrus localhost
>
> takes about 25 sec
