Problem with SMTP EHLO host using Sugar On-Site

I am not sure if this is where it pulls the domain to send, but it sounds like it might be grabbing it from the site_url setting in your config.php file. Check to see if that matches what it is sending in the EHLO handshake and adjust to test. 

Angel,

I'll try, but the documentation from Sugar that talks about migrating On Demand to On Site clearly states that this URL must contain the full qualified name of the instance (not just the host name/IP). Won't it result in unexpected behavior in other points of the system?

Regards!

Yes, you are correct. For example, notification emails won't have the correct URL. Can you adjust it temporarily just to run a quick test on the SMTP connectivity?

Angel,

I changed the site_url parameter but the same error happened. Then I changed the host_name parameter, and when I click "Send test e-mail" in E-mail Definitions, Sugar keeps the "Sending e-mail" forever on the screen.

Behind the scenes, when I clicked this button an error was logged in the php errors file:

[25-Aug-2016 14:22:58 America/Sao_Paulo] PHP Fatal error:  Call to undefined function mb_internal_encoding() in /var/www/html/sugarcrm/include/Localization/Localization.php on line 397

Any clues?

Sounds like your environment may be missing the mbstring PHP extension.

Angel, you solved 2 problems with one solution!

Installing this module solved the problem (and installing another problem solved a second problem with saving Opportunities).

My last question is: will keep the host_name property only with the IP, not the full instance name, cause any other problems?

THANK YOU!

Cool. Glad it helped.

I don't think that will be a problem. I am not sure how (or if) it is used to be honest. I know the site_url setting is definitely used in several places, but I can't think of an example for host. It might only be relevant for environments where multiple instances are hosted on the same web server.

Hi everybody,

the site_url parameter is used when the system need to create links, so it is not always the server SugarCRM runs on (think of load balancers etc.), but instead the URL users use to cennect to the system through their browser. It is also used for campaign tracking functionality.

The hostname parameter is used when the server itself identifies itself to other systems, for example for sending out mails through SMTP. This should always be an IP address or even better, a FQDN for your server.

Example:

Your server is webserver.company.net, you are using https and SugarCRM is in the path /crm

The correct config is:

site_url: https://webserver.company.com/crm

hostname: webserver.company.com

Hope this clears it up.

Greets,

Mark