[horde] Authentication issues

Michael M Slusarz slusarz at horde.org
Tue Jul 23 07:55:58 UTC 2013


Quoting Steven Swarts <steven at swartsit.com>:

> On 23/07/2013 3:17 PM, Steven Swarts wrote:
>>
>> On 23/07/2013 3:05 PM, Ralf Lang wrote:
>>>> Surprisingly I don't have a imp/config/backends.local.php yet. How do I
>>>> go about configuring that? Why would the admin account work if it can't
>>>> authenticate due to no local backends?
>>> Read the info in the backends.php file how to create one.
>>> Especially read on "full" and "true" options for authentication.
>>>
>>> I have no idea why the admin account worked though. Did you actually get
>>> to read mail?
>>>
>>>
>>>
>> Yeah I'm doing that now.
>> Yep works like always, I only provide Horde really for myself but  
>> every now and again a client needs to use it and now it doesn't  
>> work. It did prior to Horde 5. I wonder if I had a setting that  
>> wasn't to standard and now it doesn't work due to compliance.
>> So i'm going digging.
>
> Ok so I have set this in my /imp/config/backends.local.php
>
> // IMAP server
> $servers['imap'] = array(
>     // ENABLED by default; will connect to IMAP port on local server
>     'disabled' => false,
>     'name' => 'Server',
>     'hostspec' => 'localhost',
>     'hordeauth' => full,
>     'protocol' => 'imap',
>     'port' => 993,
>     // Plaintext logins are disabled by default on IMAP servers (see RFC 3501
>     // [6.2.3]), so TLS is the only guaranteed authentication available by
>     // default.
>     'secure' => 'tls',
> );

You almost certainly don't want TLS on port 993. TLS is normally on  
port 143 (the standard IMAP port).

michael


___________________________________
Michael Slusarz [slusarz at horde.org]



More information about the horde mailing list