users cannot login

[Timotheus Pokorra]

Hello Andy,

perhaps you need to configure postfix for a domain name with triplet?
By default, I think it only works for mydomain.org, but not mydomain.co.uk.

Perhaps this helps, even if you are not running in multidomain:
https://docs.kolab.org/administrator-guide/configuring-the-kolab-server.html#configuration-considerations-for-multiple-domain-namespaces
Search for triplet...

On the other hand, I am not sure if that would affect the log in procedure.

Timotheus

On 13 July 2015 at 14:46, McDade, Andy <andy at 117net.co.uk> wrote:
> I need some help tracking down an issue where my first setup user can log in
> to roundcube, but any new users I set up cannot.
> I get a login denied error can the following in the maillog (this is a
> Centos 7 system with the latest Kolab 3.4).
>
> Jul 13 13:34:34 kolab imap[20634]: starttls: TLSv1 with cipher
> ECDHE-RSA-AES256-SHA (256/256 bits new) no authentication
> Jul 13 13:34:34 kolab imap[20634]: SASL Password verification failed
> Jul 13 13:34:34 kolab imap[20634]: badlogin: localhost [::1] PLAIN
> [SASL(-13): authentication failure: Password verification failed]
>
>
> and this in the roundcube logs:
>
> [13-Jul-2015 13:34:37,000000 +0100]: <8eo5e7v4> Failed login for
> user at domain.co.uk from X.x.x.x(X-Real-IP: x.x.x.x,X-Forwarded-For: x.x.x.x)
> in session 8eo5e7v42vu7h78qi3o3ulrkn4 (error: 0)
>
> [13-Jul-2015 13:34:37,000000 +0100]: <8eo5e7v4> IMAP Error: Login failed for
> user at domain.co.uk from x.x.x.x(X-Real-IP:  x.x.x.x,X-Forwarded-For:
> x.x.x.x). AUTHENTICATE PLAIN: authentication failure in
> /usr/share/roundcubemail/program/lib/Roundcube/rcube_imap.php on line 198
> (POST
> /roundcubemail/4651062b87170bb3/?_task=login?_task=login&_action=login)
>
>
> Where do I start? The ldap contains an SSHA encrypted password, and checking
> this using Apache Studio seems to confirm it correct. I have tried changing
> the password in the Kolab web admin and directly in ldap, to no avail.
>
> I see there was a problem with kolab 3.2 that had these symptoms, but It was
> fixed in that version and shouldn't be in 3.4, at least that's how I read
> it.
>
> Any help appreciated,
> Andy
>
> --
> from kolab
> _______________________________________________
> users mailing list
> users at lists.kolab.org
> https://lists.kolab.org/mailman/listinfo/users