sugar 5.5.1.rc2 on windows and exchange 2007 sp1 outgoing emails

[rterren]

help.. I run an exchange 2007 sp1 environment, recently i was asked to set up a new windows server and install sugar crm 5.5.1.rc2, i didnt see any errors during the installation. Now I have been asked to get the "Email Settings - Outgoing Mail Configuration" to work. I can click the GMail option and enter my gmail account information and it works fine. From the command line on the Windows Sugar CRM machine I can telnet to the mail server on port 25 and manually send a message no problem.

When I try and configure the SugarCRM settings to use the exchange server, it never works. I have tried multiple accounts, with and without TLS, with and without Authentication (usernaqme specified as user@domainname.com), I have run Wireshark and seen many different results, ranging from:

504 5.7.4 Unrecognized Authentication Type
Alert Message : Encrypted Alert
550.5.7.1 Client does not have permissions to send as this sender

i have tried the internal server, and our edge server, ports 25,465,587.
I created a special Receive connector for the IP of the Windows Sugar CRM server, and from looking at Wireshark I noticed that during the initial handshake the machine identifies itself as Hello and the ip number so i added the IP as an accepted authoritative domain

I never see any error in SugarCRM, or in the Windows logs. Since this is an internal protected network I COULD CARE LESS if the communication goes in the clear, I just need it to work

Any thoughts?

Thanks very much

Ron

[jbarrett]

I am having the same issue. Any updates?

[salesagility]

RC releases are not designed for production use ... you should upgrade from 5.5.1 RC to 5.5.1 using the upgrade here

[Mystech - Jason]

There are a couple of changes that are necessary in Exchange 2007 to be able to send mail through the Exchange 2007 server unauthenticated as well. Your best bet is to start by determining where the problem is (on the Sugar side or on the Exchange side).

The best way to do this is (from the box that Sugar is running on) through a telnet test. If you don't have telnet on the Exchange Server, you can use Putty or install the client (not server) through add/remove features.

An example of what you should do is below.
-Replace exchangeserver.example.com with your exchange server name.
-Replace toaddress@example.com with the address you're trying to send to as a test.
-Replace fromaddress@example.com with the address you're trying to send from (configured in Sugar)
-Replace sugarserver.example.com with the name your sugar server reports itself as.
-Items with >> are what you type, the rest is a response close to what you should get. In case it's not obvious, don't type the >>

From the command line:
>>telnet exchangeserver.example.com 25
220 exchangeserver.example.com ESMTP
>>ehlo sugarserver.example.com
250-excahngeserver.example.com at your service
250-SIZE 35651584
250-8BITMIME
250 ENHANCEDSTATUSCODES
>>mail from:<fromaddress@example.com>
250 OK
>>rcpt to:<fromaddress@example.com>
250 OK
>> DATA
354 Go ahead
>>Subject:Test
>>This is a test.
>> <just hit enter>
>>.
250 OK
>>quit
221 closing connection

================================================== ================
If you get an error back from that at any point and you typed the correct commands, it means you need some changes on the Exchange side to make it work. Otherwise the problem is on the sugar side. Let me know what you get and we can troubleshoot from there.

FYI, the >> <just hit enter> part is a line where you just hit enter, followed by a line with a period (then enter). This is the signal that the message is done.