Plesk HORDE [error] [imp] FAILED LOGIN

We had a small issue with Horde webmail on one of our CentOS Plesk 8.6 server. The problem was we were not able to login into Horde Webmail and were getting login failed error. The logs under /var/log/psa-horde/psa-horde.log showed something like this.

HORDE [error] [imp] FAILED LOGIN xxx.xxx.xxx.xxx to localhost:143[imap/notls] as info@domain.co.uk [on line 258 of "/usr/share/psa-horde/imp/lib/Auth/imp.php"]

Solution.

Make sure you can telnet to port 143 from the server itself. For ex.

[root@server] telnet localhost 143

If you receive connection refused error please Check the /etc/hosts file and make sure that it has localhost entry as shown below.

127.0.0.1 localhost
————————————————————–

If the problem is still not resolved and you still get thos errors then just re-install the IMAP Service on the server. Following are the steps used to re-install IMAP Server:

1) You can find the RPMS used by Plesk in /root/psa/PSA_version directory OR you can download the Tar (Not Autoinstaller) containing RPMS from Parallels website

http://www.parallels.com/en/download/ (need registration it’s free)

2) go to the RPM directory which contains courier Imap RPM’s

#cd [path to the PSA RPM Directory]/dist-rpm-CentOS-4.2-i386/base/

3) Re-install courier-imap-3.0.8-cos4.build81070322.16.i586.rpm and psa-courier-imap-add-8.1.1-cos4.build81070322.16.i586.rpm which will automatically restart the services too

[root@server]# pwd
/root/plesk/dist-rpm-CentOS-4.2-i386/base

[root@server]# rpm -Uvh courier-imap-3.0.8-cos4.build81070322.16.i586.rpm psa-courier-imap-add-8.1.1-cos4.build81070322.16.i586.rpm –force

Preparing… ########################################### [100%]
Reloading configuration: [ OK ]
1:courier-imap ########################################### [ 50%]
Stopping Courier-IMAP server:
Stopping imap [ OK ]
Stopping imap-ssl [ OK ]
Stopping pop3 [ OK ]
Stopping pop3-ssl [ OK ]

Starting Courier-IMAP server:
Starting imapd [ OK ]
Starting imap-ssl [ OK ]
Starting pop3 [ OK ]
Starting pop3-ssl [ OK ]

2:psa-courier-imap-add ########################################### [100%]
Stopping Courier-IMAP server:
Stopping imap [ OK ]
Stopping imap-ssl [ OK ]
Stopping pop3 [ OK ]
Stopping pop3-ssl [ OK ]

Starting Courier-IMAP server:
Starting imapd [ OK ]
Starting imap-ssl [ OK ]
Starting pop3 [ OK ]
Starting pop3-ssl [ OK ]

[root@server]# netstat -nap | grep :143
tcp 0 0 0.0.0.0:143 0.0.0.0:* LISTEN 1657/couriertcpd
[root@server]# telnet localhost 143
Trying 127.0.0.1…
Connected to localhost.
Escape character is ‘^]’.

I hope with the above methods you should be able to resolve the horde login failed error on your plesk server.

pop3d: LOGIN FAILED error on VPS containers

VPS containers running on cpanel sometimes show the following error in /var/log/maillog

pop3d: LOGIN FAILED, user=user@userdomain.net, ip=[::ffff:114.142.142.19]
pop3d: Disconnected, ip=[::ffff:114.142.142.19]
pop3d: Connection, ip=[::ffff:114.142.142.19]
pop3d: LOGIN FAILED, user=user@userdomain.net, ip=[::ffff:114.142.142.19]
pop3d: Disconnected, ip=[::ffff:114.142.142.19]

Trying to login in via webmail, you can login to the first page, where you select between Horde/Squirrelmail but trying to login further to Horde generates this error, Also via Outlook the email account does get authenticated.

Solution.

1.) Possibly you can try to update Cpanel by setting it to release version and doing a /script/upcp –force

2.) nano /etc/xinetd.d/popa3d
change disable = no to
disable = yes

service xinetd restart
service cpanel restart

3.) Check if the domain is present in /etc/localdomains and /etc/userdomains , If not add the domain

4.) /scripts/reseteximtodefaults and /scripts/fixvaliases

Please note the solutions can differ for the problems, In our case we just need to add the domain in  /etc/userdomains file, Maybe it does not work for you so you can try the other solutions given above.

Installing SquirrelMail on Unix and Linux systems

This articler covers installation of SquirrelMail on generic Unix or Linux system. It does not cover installation of operating system or tools required to install web server or PHP. Any version numbers used in examples are specific to the time when this documentation is written. If current version numbers differ, make sure that you are not using old, obsolete or vulnerable software. Guide uses UW IMAP server as example. This IMAP server can be used in generic email setup when incoming mail is stored in /var/spool/mail directory. If you are planning to use webmail with big number of users or with bigger mailboxes, consider using different IMAP server and redesign entire email system.
Download required software

You will need:

* Apache – http://httpd.apache.org/download.cgi
* PHP – http://php.net/downloads.php
* UW IMAP – http://www.washington.edu/imap/
* SquirrelMail – http://squirrelmail.org/download.php

# install -d /usr/local/src/downloads
# cd /usr/local/src/downloads
# wget http://some-apache-mirror-server/apache/httpd/httpd-2.0.54.tar.gz
# wget http://some-php-mirror-server/get/php-4.3.11.tar.bz2/from/this/mirror
# wget ftp://ftp.cac.washington.edu/mail/imap.tar.Z
# wget http://some-sourceforge-mirror/some-path/squirrelmail-1.4.5.tar.bz2

Unpack and install apache

# cd /usr/local/src
# tar -xzvf /usr/local/src/downloads/httpd-2.0.54.tar.gz
# cd httpd-2.0.54
# ./configure –prefix=/usr/local/apache –enable-module=so
# make
# make install

Unpack and install php

# cd /usr/local/src
# tar –bzip2 -xvf /usr/local/src/downloads/php-4.3.11.tar.bz2
# cd php-4.3.11
# ./configure –prefix=/usr/local/php \
> –with-apxs2=/usr/local/apache/bin/apxs
# make
# make install

If you configure PHP compilation with –disable-all option, you must add –enable-session and –with-pcre-regex options.
Add PHP support to apache

<IfModule mod_php4.c>
AddType application/x-httpd-php .php
</IfModule>

Restart apache and check if php is working

/usr/local/apache/bin/apachectl graceful

<?php phpinfo(); ?>

Unpack and install imap server

Unpack UW IMAP archive.

# cd /usr/local/src
# tar -xzvf /usr/local/src/downloads/imap.tar.Z

Compile UW IMAP

cd /usr/local/src/imap-<someversion>
make port-name EXTRADRIVERS=” SSLTYPE=unix

Replace port-name with name that matches your system. Check Makefile for possible values. If you haven’t installed OpenSSL libraries and headers, use SSLTYPE=none instead of SSLTYPE=unix.

Install IMAP server binary

strip imapd/imapd
install -d /usr/local/libexec/
cp imapd/imapd /usr/local/libexec/

Enable IMAP server in inetd.conf

imap2 stream tcp nowait root /usr/sbin/tcpd /usr/local/libexec/imapd

Restart inetd

Prepare SquirrelMail directories

# mkdir /usr/local/squirrelmail
# cd /usr/local/squirrelmail
# mkdir data temp
# chgrp nogroup data temp
# chmod 0730 data temp

Unpack SquirrelMail

# cd /usr/local/squirrelmail
# tar –bzip2 -xvf /usr/local/src/downloads/squirrelmail-1.4.5.tar.bz2
# mv squirrelmail-1.4.5 www

Configure SquirrelMail

Start SquirrelMail configuration utility. Configure SquirrelMail with UW preset. Set data and attachment directories.
Configure access to SquirrelMail in Apache

Modify httpd.conf

Alias /squirrelmail /usr/local/squirrelmail/www
<Directory /usr/local/squirrelmail/www>
Options Indexes
AllowOverride none
DirectoryIndex index.php
Order allow,deny
allow from all
</Directory>

Log into SquirrelMail

After you add alias to SquirrelMail in apache configuration and restart apache, you should be able to access SquirrelMail by going to http://your-server/squirrelmail.