PDA

View Full Version : email connector with sbs 2011 - exchange 2010


sudogreg
August 17th, 2011, 10:15 AM
we are using

SMTP Host: 127.0.0.1
Port: 25 (also tried 465 & 587)

authentication has been verified, and user can login via owa

we get this error message below
-------------------------------------
Connecting to SMTP server...
< 220 servername.domainname.local Microsoft ESMTP MAIL Service ready at Wed, 17 Aug 2011 11:08:06 -0500
RequestDone Rq=0 Error=0
> EHLO admin@domain.net
< 501 5.5.4 Invalid domain name
RequestDone Rq=10 Error=501 5.5.4 Invalid domain name
Error, Application Stopped
---------------------------------------
using stunnel we are able to get our google apps (gmail) to work properly, but migrating to exchange and trying to get it working here. also tried stunnel with exchange with varions 100## errors.

RequestDone Rq=0 Error=10061

Support Team
August 17th, 2011, 10:43 AM
Please make sure you try to connect directly to your Exchange server, not trough Stunnel (though it should work well with it) and run the test again. If you see the same results then please use the Help > Technical Support menu in RangerMSP to send us your log files, maybe we will be able to find additional information there.

Thanks,
Dina

sudogreg
August 17th, 2011, 10:49 AM
would prefer not to use stunnel, we disabled stunnel and tried all standard ports, and all standard setups as per the guides in the wiki, and nothing is getting past that error, domain name invalid... logs sent. 2mb file. thanks for the quick response as always!!!

sudogreg
August 17th, 2011, 11:33 AM
i should also note that CommitCRM server and the exchange server are on the same physical machine, server.domain.local

swallservices
August 17th, 2011, 11:56 AM
What version of Exchange are you running on your local system? 2003, 2007, 2010? Is this running on SBS or Windows Std?

swallservices
August 17th, 2011, 12:12 PM
Sorry - I just noticed the subject line :) You need to add a new receive connector in Exchange in order for the CommitCRM e-mail connector to work correctly. Also you DO NOT want to authenticate to the SMTP server - no username and password needed.

Instructions can be found here:

http://blogs.technet.com/b/exchange/archive/2006/12/28/3397620.aspx

Do Option 1: Make your new scoped connector an Externally Secured connector

I hope this helps!

sudogreg
August 17th, 2011, 12:29 PM
you sir solved our issue!!

that is exactly the fix.

same setup for pop for incoming?

sudogreg
August 17th, 2011, 12:40 PM
should post your above info in the wiki for exchange 2010. this was very helpful

Support Team
August 17th, 2011, 12:44 PM
Thanks swallservices! Yes, we will definitely add this to our Wiki, thanks sudogreg for recommending this.

sudogreg
August 17th, 2011, 01:04 PM
hey swallservices, we are having the same issue with pop3 incoming, not connecting. also tried various combos, pop3 is enabled on exchange, port 110 and secure port

swallservices
August 17th, 2011, 01:20 PM
I know this is a silly question - but are you certain POP3 is enabled and running on Exchange?

Check these places:
Exchange Management Console > Server Configuration > Client Access > POP3 and IMAP4 > Check Binding and Authentication. Should be plain text.
Services.msc > Ensure that Microsoft Exchange POP3 is started and set to automatic

Once those two are done you can check that the POP3 server is responding by using the CommitCRM ServerConfig POP3 test. If you still have a problem let me know what the test kicks back to you.

I hope this helps.

sudogreg
August 17th, 2011, 02:00 PM
Thanks again.

Plain test logon (basic authentication. No TLS...
or
Plain text authentication logon (integrated windows authentication) no TLS

sudogreg
August 17th, 2011, 02:02 PM
edit...

sudogreg
August 17th, 2011, 02:05 PM
...yep. that did it. service was not running. now getting this...
RqType = 2 POP3 error 500 -ERR Logon failure: unknown user name or bad password.

weird...

sudogreg
August 17th, 2011, 02:11 PM
again, nevermind. pop3 requires username, without the @domain.com...

swallservices
August 17th, 2011, 02:50 PM
I'm glad you got it :) You are correct that a username and password is required when receiving e-mail - it's sending where you don't want to use the credentials.

I'm glad I was able to point you in the right direction.

sudogreg
August 17th, 2011, 02:56 PM
that would probably be a good piece of info to add to wiki as well CommitCRM team. this is all info that is slightly different than the existing guides suggest.

thanks again SWALLSERVICES!!

swallservices
August 17th, 2011, 06:34 PM
You're welcome :)