IMAP client cannot login to SuSe

[asg]

I see similar queries but no substantive answers.

I have a "private" network of a few client machines running M$ XP using Outlook being served by a RedHat (V6) server (that then handles all sendmail traffic with my ISP). The clients are configured to use IMAP and this all works "out of the box".

I am trying to migrate to a new, larger, faster server running Suse ES 10 SP1.

I have the IMAP service up and running (I can 'telnet localhost 143' and get a reply OK).

Problem is my Outlook machines cannot connect/login (they report an authorization failure - I am positive the username/password combo is OK).

Mention is made in other threads of SSL involvement. I guess I need help in understanding how/why this impacts on the client/server exchange and how I can either disable this behaviour by the server (which I'm guessing is expecting scrambled passwords) or how I should configure my clients/server to get this to work.

Any pointers/advice gratefully received.

[whych]

To get mail and imap running correctly with sles, you need to set up ldap and use cyrus imap.
You enable the mailboxes by adding the mail plugin to the ldap user settings (filter ldap) (found in yast>Sec and users)
The user account must be present, or no mail.
If you still have problems, let me know and I'll see what else I can do.

[asg]

Thanks for taking the time to look at my enquiry.
Bit more info...... when I said "Outlook" I should have said "Outlook Express" (I'm not a M$ person (Unix since 1983) - its just an email client AFAIK).
After some more research it appears the Express variant (being 'free') has no ability to handle SSL. So, I've got Mozilla Thunderbird installed now and I found a useful article here http://www.topology.org/linux/imap.html - this describes how you need to create a certificate for imap. Did this and eventually got things working (I had to disable a Virus Checking option when configuring the MTA that seemed to prevent email delivery - don't understand why).

All in all it just appears too complex, too many things require setting up and tweaking to get a very simple thing done. All this added "security" baggage that is not required and just gets in the way (in my case, I just want a linux server (acting as a firewall/router to handle email on a private network for a number of dumb users on XP systems and then pass on to/collect from a smarter host at my ISP). Old version of RedHat and simple email client on M$ worked "out of the box".

Am I correct in assuming that you suggested cyrix imap because it does not enforce use of SSL ?

Also, I'm unsure what LDAP would add to the party ?

[whych]

LDAP gives a unified login and admin model. It means you can manage most user admin tasks from one place on the server.
Remember, sles can be used as a complete server solution for file, print and lamp. I also like suse's easy admin model.
You can disable ssl in sles if you dont't need it. Cyrix imap and ldap is what sles email was built around. (I think it makes it easier to migrate to Novell client and groupwise.
If you are going to stick with sles, have a look at
Deploying Suse Linux Enterprise Server - pcc-services.com
It's well worth the $10 or so as a pdf download and the author will answer questions.
ATM my imap works but I need to delve into fetchmail config - it's not fetching mail from the remote server.