Problems authenticating after upgrade

[mglenney]

I have upgraded us from 11.0.2.1 to 11.2. The old server was a VM and I have now moved it to bare metal. I copied the /var/opt/scalix directory and restored on the new server and then installed 11.2.

I had numerous problems but resolved most. My problem now is that we can't seem to authenticate. We are using kerberos against an AD domain. Auth works with sxpamauth and kinit. I am able to get to SAC.

Can't login to webmail. I've tried every possible combination of username. Can't connect via IMAP or Outlook connect either.

I have added the required lines to ual.remote, pop3, smtpd.conf and omslapeng. I have tested those settings with sxpamauth.

I'm lost and I need help badly. Server is down now. Monday morning is approaching. Anyone up at this hour.

MG

[mglenney]

It seems that it isn't a problem with authenticating as I suspected. I can authenticate. It seems the problem is with IMAP. I have run countless tests and generated log after log. I'll post but don't want to overwhelm.

Is there anyone out there who might be able to lead me in the right direction?

I have put IMAP_LOGLEVEL=3 in general.cfg and generated the following:

Code: Select all

10055 02:23:43.602 IMAP4 Server 11.1.0.10849 on xdsmail.xdsinc.corp at Mon Oct 15 02:23:43 2007
10055 02:23:52.287 CMD: a LOGIN "Glenney" <password>
10055 02:23:52.376 RSP: a NO LOGIN failed, internal error
10055 02:23:52.376 IMAP4 Satellite Server exiting.
[root@xdsmail tmp]# more imap.localhost.localdomain
10036 02:23:27.341 IMAP4 Server 11.1.0.10849 on xdsmail.xdsinc.corp at Mon Oct 15 02:23:27 2007
10036 02:23:27.604 CMD: 1 CAPABILITY
10036 02:23:27.632 RSP: 1 OK CAPABILITY completed
10036 02:23:27.689 CMD: 2 AUTH plain
10036 02:23:27.754 RSP: 2 NO AUTHENTICATE failed, internal error
10036 02:23:27.754 IMAP4 Satellite Server exiting.


That output was generated when trying to login to IMAP via telnet. I was able to login via pop. SWA doesn't work (IMAP) and Outlook Connect fails as well.

I thought it was interesting that it generated a "localhost" log file and a "domain name" log file.

MG