[horde] Strange fix, sort of...

Michael M Slusarz slusarz at horde.org
Mon Jul 22 19:42:03 UTC 2013


Quoting Michael Robinson <plug_1 at robinson-west.com>:

> On Mon, 2013-07-22 at 09:37 +0200, Ralf Lang wrote:
>> On 22.07.2013 01:08, Michael Robinson wrote:
>> > <?php
>> >         $servers['imap']['hostspec'] = 'mail.robinson-west.com';
>> >         $servers['imap']['hordeauth'] = full;
>> >         $servers['imap']['disabled'] = false;
>> >         $servers['imap']['protocol'] = 'imap';
>> >         $servers['imap']['port'] = 143;
>> >         $servers['imap']['secure'] = false;
>> > ?>
>> >
>> > The above php file is backends.local.php and it is under imp/config.
>> > The odd change is going from hordeauth = false to hordeauth=full.
>> > No longer do I have to log in twice to use IMP.  Well, that isn't
>> > exactly what I was after, I just wanted to stop the not authorized
>> > for IMP messages and not being able to get past the IMP login.
>> >
>>
>> For the record: Which problem thread is this solution referring to?
>>
>>
> Horde 5.1.2 (final)

Why are you using imap authentication?  If using imp, there is 0  
reason to not be using 'app' authentication (see imp/docs/INSTALL).

IMAP authentication has *nothing* to do with IMP.  You are thus  
creating two separate IMAP connections when only one is needed.

michael

___________________________________
Michael Slusarz [slusarz at horde.org]



More information about the horde mailing list