Article ID: 114154, created on Jun 20, 2012, last review on Feb 9, 2016

  • Applies to:
  • Plesk 12.0 for Linux
  • Plesk 11.0 for Linux
  • Plesk 11.5 for Linux
  • Plesk 10.4 for Linux/Unix


When attempt to log in Horde webmail interface, the login screen clears and prompts again for credentials; it is not possible to log in. The credentials have been checked via telnet:

    # telnet domain.tld 143
     AD=REFERENCES SORT QUOTA IDLE AUTH=PLAIN ACL ACL2=UNION STARTTLS] Courier-IMAP ready. Copyright 1998-2004 Double Precision, Inc. See COPYING for distribution information.
     . LOGIN "mailname@domain.tld" "testpassword"
     . OK LOGIN Ok.

The account exists within the domain's control panel in Plesk and appears to be set up correctly.

Horde debug log contains the following error:

    NOTICE: HORDE [horde] Login success for to horde ( [pid 10577 on line 182 of "/usr/share/psa-horde/login.php"]
    NOTICE: HORDE User is not authorized for imp [pid 10577 on line 324 of "/usr/share/psa-pear/pear/php/Horde/Registry.php"]

Also php can show session_save_path different from /var/lib/php/session:

# php -r 'echo session_save_path() . "\n";'


PHP extension memcache has been enabled on the server, but Horde does not work with memcache extension.


  1. Disable module memcache in php configuration as below:

    # grep -ir memcache /etc/php.d/*

    or move memcache.ini:

    # mv /etc/php.d/memcache.ini /root/
  2. Additionally make sure that session.save_handler value is set to files in Horde php.ini file:

    # grep -ir session.save_handler /etc/psa-webmail/horde/horde/php.ini
    session.save_handler = files

Search Words

horde login page

User is not authorized for imp

login webmail

unable to login to horde

on line 324 of "/usr/share/psa-pear/pear/php/Horde/Registry.php"

Unable login in Horde

Webmail redirect to login screen

Login success for



dd0611b6086474193d9bf78e2b293040 56797cefb1efc9130f7c48a7d1db0f0c a914db3fdc7a53ddcfd1b2db8f5a1b9c 29d1e90fd304f01e6420fbe60f66f838 0a53c5a9ca65a74d37ef5c5eaeb55d7f 2a5151f57629129e26ff206d171fbb5f e335d9adf7edffca6a8af8039031a4c7 e8756e9388aeca36710ac39e739b2b37 01bc4c8cf5b7f01f815a7ada004154a2 aea4cd7bfd353ad7a1341a257ad4724a

Email subscription for changes to this article
Save as PDF