Login Fails POP3 and IMAP

[bazza]

Hi,
I'm trialling ISPCONFIG 3.0.1.4 Beta on Debian Lenny. I'm testing on an internal network.
I've set up one user called 'test' with the domain 'testing.com' and a mail box with the alias 'tester' and configured the DNS with A,MX, NS and PTR records pointing to 192.168.1.100. The client machine (ie the one connecting to the server) has 192.168.1.100 set as the primary DNS address and an entry in /etc/hosts pointing to 192.168.1.100.
The server has been set up for secure login and monitor reports all systems are go. So far so good.
Fire up a browser on the client machine and go to https://testing.com.8080 and we get the login page, good. Login ok, logout again.
Try http://testing.com:8080 and we get an error page,good.
Try http://testing.com and we get the default web page, good.
Try http://www.testing.com, default page again, good.
Try ftp://testing.com and we get an ftp connection, good.
Attempt to connect using Evolution and it fails to login. I am watching the server log as we do this and we can see the incoming connection being logged by the pop3d and then it comes up with Login Failed. Doubled checked user names and passwords were entered correctly by typing them in again on both server and client still no luck.
So we tried webmail (https://testing.com/webmail) the squirrelmail page pops up but again the login credentials fail to work and again I can see the events being logged on the server.
I am at loss as to why the mail server is rejecting these logins. Can any one please point me in the right direction to look for a solution. Thanks

[till]

Make sure that you use the correct login details. The login username is the email address of the mailbox.

[bazza]

ROFL!!
I've spent hours investigating this, It never occurred to me that the login schema would have deviated from the 'norm'.
Thanks heaps for your reply, problem solved, testing continues.

[till]

Most modern email systems use the email address as username as its easier to remember for the clients then using a prefix number. If you run a server at a provider that hosts hundreds of different email domains, you can not simply use the part in front of the @ as username as many accounts might want to use the username "info" then.

[bazza]

Yes I realise that now. My problem arose because I deal with single domain mail servers for private networks where the user name suffices so that is my normal schema and I just got stuck in a mind set without thinking about what I was doing. Thanks for you help once again.