Sage CRM

Trying to figure out what I am doing wrong with the SMTP setup. I have SageCRM in E-Mail Configuration to ""Send Mail Using"" = ""Internal SMTP"". I have configured the Outgoing mail server, smtp port, smtp user name and password. I can send email to internal users but not external users. I thought this was a relaying issue but I must be missing something to allow it to relay. What is needed to send email from SageCRM when using Exchange 2010 to allow external users to get email. The only message I get is ""There was an error sending your E-mail, the E-mail was not sent. Please consult your system administrator.

There are a lot of steps to this and a lot that can go wrong. Are all your users set up with valid email addresses or at least the user you are testing with? (shouldn't matter but I find that it does) Is SMTP Service installed and running on the CRM server box?

Yes it is a valid email address that has a user mailbox. What SMTP service are you referring to on the CRM box? Would it be different for internal and external users?

Some suggestions from the team: make sure his email config is setup with a valid email smtp address and password. maybe tell him to check the server for the mailroot directory and see if the messages are sitting in there

It is a valid email. I have it setup just like I did for the MAS 90 SMTP for paperless. MAS works but CRM doesn't. Local emails work. I removed the user and pass and local emails work. just can not send outside of my domain.Messages never get to the server. I get error on screen and it doesn't close the email screen (i use pop up).

I am trying to test the account with outlook to verify that it is a valid smtp account and that it should be able to send. Thanks @PeterWolf

I got it working. I had to go into the Exchange box and create a Receive Connector for the Server under the Hub Transport. For some reason the default one we created was not allowing the CRM server to send out. So I created a specific one just for that IP address.

That is bizarre Todd. I ran that by the team - we haen't seen that before. I wonder if it's a security thing with the latest version of Exchange?

Not sure. I believe by default Exchange doesn't allow any outbound email outside of the domain. You must add the route before email can go outside.