User is not authorized for horde

horde5 is configured to use imp for login. After login follo

Sat, 08 Sep 2012 17:47:04 +0000

horde5 is configured to use imp for login. After login following appears in syslog: Sep 8 19:40:45 webmail-test HORDE: [horde] Login success for xxx@example.net [192.168.116.22] to horde. [pid 3279 on line 160 of "/var/www/test/login.php"] Sep 8 19:40:45 webmail-test HORDE: User is not authorized for horde [pid 3279 on line 266 of "/usr/share/php/Horde/Registry.php"] backends.local.php: false, 'name' => 'IMAP Server', 'hostspec' => '192.168.116.2', 'hordeauth' => 'full', 'protocol' => 'imap', 'port' => 143, 'secure' => 'false', 'maildomain' => '', 'quota' => array( 'driver' => 'imap', 'params' => array( 'hide_when_unlimited' => true, 'unit' => 'MB' ) ), 'cache' => false, 'acl' => true, ); this backend.local.php works without any problems in a Horde 4 environment.

You cannot use "hordauth" and IMP application authentication

Mon, 10 Sep 2012 09:40:01 +0000

You cannot use "hordauth" and IMP application authentication at the same time. Please use the mailing list to ask for support. http://www.horde.org/mail/ contains a list of all available mailing lists.

> You cannot use "hordauth" and IMP application authenticati

Sat, 15 Sep 2012 14:51:23 +0000

> You cannot use "hordauth" and IMP application authentication at the > same time. > > Please use the mailing list to ask for support. > > http://www.horde.org/mail/ contains a list of all available mailing lists. I have the same problem and I had setup hordeauth = false

same problem here, after upgrade from horde 5.0.2 to 5.0.3 i

Tue, 12 Feb 2013 08:16:06 +0000

same problem here, after upgrade from horde 5.0.2 to 5.0.3 i see only HORDE: User is not authorized for horde [pid 441 on line 259 of ... 5.0.2 was running fine, any hints ?

> same problem here, after upgrade from horde 5.0.2 to 5.0.3

Wed, 27 Feb 2013 07:13:59 +0000

> same problem here, after upgrade from horde 5.0.2 to 5.0.3 i see only > > HORDE: User is not authorized for horde [pid 441 on line 259 of ... > > 5.0.2 was running fine, any hints ? Havee You solved this prob, have the same ....

I got the same behavior after upgrading to 5.0.1 , after try

Wed, 06 Mar 2013 18:04:50 +0000

I got the same behavior after upgrading to 5.0.1 , after trying reinstalling etc I finally discovered that if I change the cookie path by something other than '/' I got the error (Which may not be a bug but IS a big hurdle)

> I got the same behavior after upgrading to 5.0.1 , after t

Wed, 10 Jul 2013 23:20:04 +0000

> I got the same behavior after upgrading to 5.0.1 , after trying > reinstalling etc I finally discovered that if I change the cookie > path by something other than '/' I got the error (Which may not be a > bug but IS a big hurdle) In my case I have $conf[cookie][path] as '/' and I get the error anyway. Horde 5.1.1.

>> I got the same behavior after upgrading to 5.0.1 , after

Thu, 11 Jul 2013 01:58:49 +0000

>> I got the same behavior after upgrading to 5.0.1 , after trying >> reinstalling etc I finally discovered that if I change the cookie >> path by something other than '/' I got the error (Which may not be a >> bug but IS a big hurdle) > > In my case I have $conf[cookie][path] as '/' and I get the error anyway. > > Horde 5.1.1. Just found out this is caused by a google bot crawler trying to access rampage.php on my horde website: http://marc.info/?l=horde&m=137350543201886&w=2