I’ve run the same setup and have run into the same problem.

IMAP requiring SSL and requiring CRAM-MD5 for authentication.
SMTP use SSL and requiring CRAM-MD5 for authentication (except for relaying accepted from hosts within my internal IP range).

I’ve configured SquirrelMail’s IMAP setting to use CRAM-MD5 and have changed the port number to 993. I’ve tried combinations of using ‘cyrus’ and ‘macosx’ as the server type, as well as TLS on and off. (All this done via config.pl, of course.)

I always get the following error:
[QUOTE] Bad request: IMAP server does not appear to support the authentication method selected. Please contact your system administrator.[/QUOTE]

What am I missing? I’m surprised no one had a response for the previous poster.

Basically, I switched to CRAM-MD5 authentication and SSL encryption for IMAP & SMTP because we have many employees who have PowerBooks for workstations and are using them internally on Ethernet or WiFi and often from home or on the road. Previously those employees had to remember to use their home ISP’s SMTP server or a .Mac (or similar) account to send from the road.

This was far from ideal and not really great for business communication, so when I set up our new mail server I went for stronger authentication and encryption all around.

This setup has been working fine for us, but a few part-time employees have joined our team and share the same handful of computers which only have a single user account running retail software. There’s been a push from management to set them up with webmail so they can do their e-mail during slow periods.

I was just going to configure SquirrelMail on the mail server as a short term fix and was hoping to do so without compromising security by opening up less secure means of communication. It sounds like this is not possible, correct?

I know it’s pointless to encrypt the traffic which never leaves the box, but I’m happier doing that for a couple of people than opening up the potential for an employee to copy their mail settings to a new machine, accidentally set it up insecurely, and have private company e-mail going out over the Internet.

In case someone searches the forums for this:

Changed the server’s Mail service Security settings to USE SSL (instead of REQUIRE SSL) for IMAP (it was already set to USE SSL for SMTP).

Ran /etc/squirrelmail/config/conf.pl to change the IMAP settings to not use Secure IMAP (TLS) and made sure it was connecting to localhost:143.

Then verified that non-SSL IMAP and POP connections from the outside do not work after modifying the FireWall settings.

Worked like a charm. Very quick fix.