https & email

[Beefeater]

Hi,

4.5.1
CentOS 4.4
PHP 5.1.6
MySQL 5.0.27

I'm running https with a selfsigned Cert.
I got most of the things to work out nicely.
However.
I try to setup my email with IMAP. Enter all the information, no ssl (deal with ssl later). Then run Test settings.
I takes around 3 min and then I get my folders.
So it's kinda working but takes forever.
Its a SBS2k3 with Exchange 2003 that I try connect to.
So what's up?
Well I see whats happening but how to solve it?

Wed Mar  7 15:04:44 2007,314 [17344] DEBUG SugarCRM - ---------------STARTING FINDOPTIMUMS LOOP----------------
Wed Mar  7 15:04:44 2007,315 [17344] DEBUG SugarCRM - 1: I-E testing string: {HOST:143/service=imap}INBOX
Wed Mar  7 15:05:04 2007,325 [17344] DEBUG SugarCRM - 1: I-E found good connect using [{HOST:143/service=imap}INBOX]
Wed Mar  7 15:05:04 2007,326 [17344] DEBUG SugarCRM - 1: I-E clearing error and alert stacks.
Wed Mar  7 15:05:04 2007,326 [17344] DEBUG SugarCRM - 2: I-E testing string: {HOST:143/service=imap/secure}INBOX
Wed Mar  7 15:05:24 2007,330 [17344] DEBUG SugarCRM - 2: I-E failed using [{HOST:143/service=imap/secure}INBOX] - error: Can't do secure authentication with this server
Wed Mar  7 15:05:24 2007,330 [17344] DEBUG SugarCRM - 2: I-E clearing error and alert stacks.
Wed Mar  7 15:05:24 2007,330 [17344] DEBUG SugarCRM - 3: I-E testing string: {HOST:143/service=imap/notls}INBOX
Wed Mar  7 15:05:44 2007,336 [17344] DEBUG SugarCRM - 3: I-E found good connect using [{HOST:143/service=imap/notls}INBOX]
Wed Mar  7 15:05:44 2007,337 [17344] DEBUG SugarCRM - 3: I-E clearing error and alert stacks.
Wed Mar  7 15:05:44 2007,337 [17344] DEBUG SugarCRM - 4: I-E testing string: {HOST:143/service=imap/notls/secure}INBOX
Wed Mar  7 15:06:04 2007,340 [17344] DEBUG SugarCRM - 4: I-E failed using [{HOST:143/service=imap/notls/secure}INBOX] - error: Can't do secure authentication with this server
Wed Mar  7 15:06:04 2007,340 [17344] DEBUG SugarCRM - 4: I-E clearing error and alert stacks.
Wed Mar  7 15:06:04 2007,341 [17344] DEBUG SugarCRM - 5: I-E testing string: {HOST:143/service=imap/novalidate-cert}INBOX
Wed Mar  7 15:06:24 2007,348 [17344] DEBUG SugarCRM - 5: I-E found good connect using [{HOST:143/service=imap/novalidate-cert}INBOX]
Wed Mar  7 15:06:24 2007,348 [17344] DEBUG SugarCRM - 5: I-E clearing error and alert stacks.
Wed Mar  7 15:06:24 2007,349 [17344] DEBUG SugarCRM - 6: I-E testing string: {HOST:143/service=imap/novalidate-cert/secure}INBOX
Wed Mar  7 15:06:44 2007,351 [17344] DEBUG SugarCRM - 6: I-E failed using [{HOST:143/service=imap/novalidate-cert/secure}INBOX] - error: Can't do secure authentication with this server
Wed Mar  7 15:06:44 2007,352 [17344] DEBUG SugarCRM - 6: I-E clearing error and alert stacks.
Wed Mar  7 15:06:44 2007,352 [17344] DEBUG SugarCRM - 7: I-E testing string: {HOST:143/service=imap/notls/novalidate-cert}INBOX
Wed Mar  7 15:07:04 2007,359 [17344] DEBUG SugarCRM - 7: I-E found good connect using [{HOST:143/service=imap/notls/novalidate-cert}INBOX]
Wed Mar  7 15:07:04 2007,360 [17344] DEBUG SugarCRM - 7: I-E clearing error and alert stacks.
Wed Mar  7 15:07:04 2007,360 [17344] DEBUG SugarCRM - 8: I-E testing string: {HOST:143/service=imap/notls/novalidate-cert/secure}INBOX
Wed Mar  7 15:07:24 2007,363 [17344] DEBUG SugarCRM - 8: I-E failed using [{HOST:143/service=imap/notls/novalidate-cert/secure}INBOX] - error: Can't do secure authentication with this server
Wed Mar  7 15:07:24 2007,363 [17344] DEBUG SugarCRM - 8: I-E clearing error and alert stacks.
Wed Mar  7 15:07:24 2007,364 [17344] DEBUG SugarCRM - ---------------end FINDOPTIMUMS LOOP----------------

[rodsingleton]

Hi beefeater,

I'm getting this but with latest version of CE and Exchange 2003 server but only for a couple of users. Most people can connect ok using IMAP with the exception of 2 people. We've been through everything in Exchange and Active Directory to see if there's any difference.

Did you get this sorted? How?

Rod

[Beefeater]

Hi Rod,

I'm sorry mate but I left the company using SugarCRM two years ago and haven't used it since.
Can't remember if I ever figured this one out as we moved on to a proprietary software solution shortly after my post, to my dismay.

As SugarCRM is open source it shouldn't be too hard to pinpoint the error source by enabling debug mode and maybe add a few of your own print statements.

Best of luck

[rodsingleton]

Hi Beefeater,

Thanks anyway. No probs.

I figured it out eventually. The fix (if I can call it that) I figured out seems odd to me given other Exchange 2003 accounts in the same Active Directory OU all worked without this quirky work around. But for anyone else getting this problem I'll describe the scenario and the fix I stumbled upon by accident which solved it for us.

Environment:
Exchange 2003 with IMAP enabled, and a self signed certificate published (not that this had anything to do with the problem but the error message led me down a path investigating SSL). Sugar CE 5.2.0j on Centos 5.3.

Problem:
Connecting users email using the Sugar Email client and using IMAP. Most users connected and validated ok and were able to pull in their INBOX into Sugar. User names were entered as just [username] without mentioning the domain, but a few in our company failed to authenticate to Exchange saying that either the username or password is incorrect, which we knew was not right as we could log into the Exchange web interface with the offending accounts.

Debugging:
Switched on Sugar logging at DEBUG level and found the following in the debug log file:

Wed Sep 23 15:36:57 2009 [15887][dbed3868-e7a5-550a-7f9f-4ab9ad21058c][DEBUG] ---------------STARTING FINDOPTIMUMS LOOP----------------
Wed Sep 23 15:36:57 2009 [15887][dbed3868-e7a5-550a-7f9f-4ab9ad21058c][DEBUG] 1: I-E testing string: {think-ex01.think.internal:143/service=imap/notls/novalidate-cert/secure}INBOX
Wed Sep 23 15:36:57 2009 [15887][dbed3868-e7a5-550a-7f9f-4ab9ad21058c][DEBUG] 1: I-E failed using [{think-ex01.think.internal:143/service=imap/notls/novalidate-cert/secure}INBOX] - error: Can't do secure authentication with this server
Wed Sep 23 15:36:57 2009 [15887][dbed3868-e7a5-550a-7f9f-4ab9ad21058c][DEBUG] 1: I-E clearing error and alert stacks.
Wed Sep 23 15:36:57 2009 [15887][dbed3868-e7a5-550a-7f9f-4ab9ad21058c][DEBUG] 2: I-E testing string: {think-ex01.think.internal:143/service=imap/notls/novalidate-cert}INBOX
Wed Sep 23 15:36:58 2009 [15887][dbed3868-e7a5-550a-7f9f-4ab9ad21058c][DEBUG] 2: I-E failed using [{think-ex01.think.internal:143/service=imap/notls/novalidate-cert}INBOX]
Wed Sep 23 15:36:58 2009 [15887][dbed3868-e7a5-550a-7f9f-4ab9ad21058c][DEBUG] 2: I-E ERROR: $ie->findOptimums() failed due to bad user credentials for user login: noel

The bit that threw me was the error "Can't do secure authentication with this server" but we hadn't selected SSL, so why was this error being thrown.

Research and Solution:

We tried entering the usernames as [domain]\[username] but to no avail either.

Googling the log error didn't really give me any solutions, but i eventually googled this and found this wiki article
So just for a laugh I though I'd try entering the username as [username]@[internal_domainname]. eg username@company.local or username@company.internal and low and behold it worked.

I have no idea why a handful of A/D accounts needed to be setup for IMAP authentication in this way but it certainly worked.

Hope this helps someone.

Rod

[roblaus]

Being a bit sarcastic here: I tend to believe that exchange is the problem. I have given up on MS's security concepts after trying to connect to mssql via jst on the same physical machine as local admin and mssql sa and I am getting "not a trusted connection" no matter what I am doing (and I spent almost half a day researching the issue on the net just to find out that the driver is definitely not the problem).