I first reported this on the forum after this @willrennie suggested to report this on Github.
Tried multiple mailboxes on different SMTP servers and different web servers to see if it was a server related issue.
However none of the mailboxes work with SuiteCRM.
For me this worked in the hotfix before 7.5.2 was released, after that all clean installs failed, also 7.5.3
Example when i try to reset a users password i get the message
System is unable to process your request. Please check: -Recipient Email Address -Your server status
This is what i can find in the suitecrm.log:
Fri Mar 18 01:43:46 2016 [13347][1][FATAL] SugarPHPMailer encountered an error: An outgoing mail server is not configured to send emails. Please configure an outgoing mail server or select an outgoing mail server for the mail account that you are using in Settings >> Mail Account.
Fri Mar 18 01:43:46 2016 [13347][1][FATAL] SugarPHPMailer encountered an error: SMTP connect() failed. https://github.com/PHPMailer/PHPMailer/wiki/Troubleshooting
When i check the Email settings: Outgoing mail configuraiton all fields are filled.
If i press "Send Test Email" i get the message:
Error:SMTP connect() failed. https://github.com/PHPMailer/PHPMailer/wiki/Troubleshooting
It's a new 2015 updated version of PHPMailer so probably the legacy Sugar code from 2009 isn't fully updated to handle it smoothly, or, your settings or server or network are not configured right.
From this troubleshooting page: https://github.com/PHPMailer/PHPMailer/wiki/Troubleshooting
You can see from that page, there's about 50 reasons why sending email could fail.
To find out the exact reason,
include/SugarPHPMailer.phpthis->SMTPDebug = 2;Thanks for the reply @chris001 i tried to add the line SMTPDebug = 2, after i clicked again on Send test email and get the "normal message" ->
Error:SMTP connect() failed. https://github.com/PHPMailer/PHPMailer/wiki/Troubleshooting
However when i try to reset some users password i get a more detailed message.
2016-03-18 23:08:01 SERVER -> CLIENT: 220 mail.idevelopment.be ESMTP Postfix (Ubuntu)
2016-03-18 23:08:01 CLIENT -> SERVER: EHLO secure.idevelopment.be
2016-03-18 23:08:01 SERVER -> CLIENT: 250-mail.idevelopment.be 250-PIPELINING 250-SIZE 10240000 250-ETRN 250-STARTTLS 250-AUTH DIGEST-MD5 CRAM-MD5 PLAIN LOGIN
250-XFORWARD NAME ADDR PROTO HELO SOURCE PORT IDENT 250-ENHANCEDSTATUSCODES 250-8BITMIME 250 DSN
2016-03-18 23:08:01 CLIENT -> SERVER: STARTTLS
2016-03-18 23:08:01 SERVER -> CLIENT: 220 2.0.0 Ready to start TLS
2016-03-18 23:08:01 SMTP Error: Could not connect to SMTP host.
2016-03-18 23:08:01 CLIENT -> SERVER: QUIT
2016-03-18 23:08:01 SERVER -> CLIENT: KGAJVE3Q�-j��/n�~֗�����n�?̪[��Z,/8�G� ��yS<)�P ���QE�7u��'y���{�����@�c�!4���'p�_�14=��.��z��q� N� ~z�\�G�~�s�Coa�߄]�d� Ef{A N�*`3NN�;ݗ��,��!a}�fF�7���J&�����}��P�PΈB�Tx�4�o�T���k`"��e��D�}���վڃ3�-�����ʬ�9^����TO*�a��&�$9�Y4Z�d���-�P���,��Ǐ)��g���_��['m����=z���X��%2�����3z
2016-03-18 23:08:01 SMTP ERROR: QUIT command failed: KGAJVE3Q�-j��/n�~֗�����n�?̪[��Z,/8�G� ��yS<)�P ���QE�7u��'y���{�����@�c�!4���'p�_�14=��.��z��q� N� ~z�\�G�~�s�Coa�߄]�d� Ef{A N�*`3NN�;ݗ��,��!a}�fF�7���J&�����}��P�PΈB�Tx�4�o�T���k`"��e��D�}���վڃ3�-�����ʬ�9^����TO*�a��&�$9�Y4Z�d���-�P���,��Ǐ)��g���_��['m����=z���X��%2�����3z
2016-03-18 23:08:01 SMTP connect() failed.
If i get this error correct SuiteCRM is trying to send true TLS, while i have SMTP over SSL or TLS set to none.
Hi,
I think, my issue is too in the same bug.
On VPS Centos 7 fresh install 7.5.3.
I don't use authentification.
In terminal :
echo "This is the body of the email" | mail -s "This is the subject line" [email protected]
is send and OK.
With SuiteCRM "Send test email",
Mar 19 17:37:59 www postfix/smtp[2060]: 5732A4839D87: to=
Mar 19 17:37:59 www postfix/cleanup[2109]: 893E34839D88: message-id=<[email protected] >
Mar 19 17:37:59 www postfix/qmgr[1916]: 893E34839D88: from=<>, size=2920, nrcpt=1 (queue active)
Mar 19 17:37:59 www postfix/bounce[2118]: 5732A4839D87: sender non-delivery notification: 893E34839D88
Mar 19 17:37:59 www postfix/qmgr[1916]: 5732A4839D87: removed
Mar 19 17:37:59 www postfix/smtp[2060]: 893E34839D88: [email protected], relay=none, delay=0.03, delays=0.01/0/0.02/0, dsn=5.4.4, status=bounced (Host or domain name not found. Name service error for name= blabla.com type=A: Host not found)
Some one can do :
tail -f /var/log/maillog
and try to send a email for see if we have same " said: 552 sorry, your envelope sender domain must exist mail461 (in reply to MAIL FROM command))"
Regards
i tried to replicate this and get the same error(different hostnames) on different servers.
when i performed tail -f /var/log/maillog on different servers i get the same output (also tried different SMTP server):
Mar 20 18:09:17 mail postfix/smtpd[8174]: connect from mail.idevelopment.be[::1]
Mar 20 18:09:17 mail postfix/smtpd[8174]: SSL_accept error from mail.idevelopment.be[::1]: 0
Mar 20 18:09:17 mail postfix/smtpd[8174]: warning: TLS library problem: error:14094418:SSL routines:SSL3_READ_BYTES:tlsv1 alert unknown ca:s3_pkt.c:1262:SSL alert number 48:
Mar 20 18:09:17 mail postfix/smtpd[8174]: lost connection after STARTTLS from mail.idevelopment.be[::1]
Mar 20 18:09:17 mail postfix/smtpd[8174]: disconnect from mail.idevelopment.be[::1]

Maybe you can try to disable TLS. I had that problem because the new version of phpmailer does not accept self signed certificates.
Around line 257 of include/phpmailer/class.phpmailer.php :
public $SMTPAutoTLS = false;
For my fedora 21:
add line in etc/php.ini
extension=openssl.so
fixed problem
@gunnicom indeed setting public SMTPAutoTLS to false did the trick, even when you just use sendmail.
@martinrusevbg i have openssl already configured in php.ini. so that didn't work.
@ghermans
@gunnicom
The new 2016 version of phpmailer is behaving in accordance with the internet's move toward default enabling TLS encryption automatically for SMTP email transmission, when the destination SMTP mail server supports TLS, even when the user asked to send the email unencrypted.
Clear text unencrypted email is to be avoided.
You should try turning on TLS in the Email Settings as follows:
"SMTP Port": 587
"Enable SMTP or SSL or TLS". TLS.
It should work just fine for you with these settings. Tested here and it works fine.
SMTP port 25 is to be only used for communication between internet mail servers. SMTP clients, such as SuiteCRM, are to submit new outgoing mail to port 587 TLS only.
Managed to fix it @ghermans
In SuiteCRM folder go to /modules/Emails and find Email.php file
In there change
$mail->Mailer = "smtp";
to
$mail->Mailer = "Sendmail";
Should work.
Hi.
@vivasergei i changed the lines
353 to: if($mail->Mailer == 'sendmail')
1958 to: $mail->Mailer = "sendmail";
And it works for me.
What about when the server doesn't have sendmail, like Postfix or other agents.
Thanks.
Hi.
@jpilldev nice to meet you
Unfortunately I found this by reading similar issue some one had in sugarcrm.
I am very happy that i didn't pay for some paid solutions on the market when found SuiteCRM which can be customized in different ways.
Can you please kindly advise where to create the new thread about some features which I can not figure out how to implement.
I have an excel file in cvs with multiple contacts, companies and emails. Some companies have more than one contact. Can any one kindly please advise on how to import this file, so contacts and companies merged together..I guess it requires some type of coding. At the moment I can only upload contacts and companies/accounts separately.
Look forward to contribute to the community with testing the bugs.
Thanks.
@jpilldev
@vivasergei
You should be able to leave the file Email.php as it was. $mail->Mailer = 'smtp';
Then go into the Admin page.
Email Settings.
Outgoing mail configuration.
Use SMTP Authentication: check this box on.
Then fill in the username and password for an account which has the right to send mail on your SMTP outgoing mail server.
Hit Save.
Hit Send test email.
@chris001
i get this in the pop up window
Error:SMTP connect() failed. https://github.com/PHPMailer/PHPMailer/wiki/Troubleshooting
and from the log file it is
LogFileSuiteCRM fresh install.txt
@vivasergei
Do you have an account in Suite CRM Forum?
EMHO, is better that you create the thread here: https://suitecrm.com/forum/suitecrm-7-0-discussion
We can help you with your problems.
What is the status of this issue? I cannot get 7.5.3 fresh install to work with Gmail. Getting the SugarPHPMailer encountered an error: An outgoing mail server is not configured to send emails.
Inbound does not work either.
~eric
Same issue using gmail for outgoing mail config. Simply turning off TLS did not work for me. I am currently bypassing SMTP and using sendmail by commenting out lines 140-159 in /include/SugarPHPMailer.php and on line 160 adding $this->Mailer = "sendmail";
Hi @abeo and @rspeedy , not sure if I am answering the right question here but I am on SuiteCRM 7.5.3 which is on top of a LAMP stack and in my case, Gmail as the outgoing mail config works(I am able to send a test mail). To use Gmail as the outgoing mail config, you have to turn ON "Allow less secure apps" in your Gmail's account security. Google thinks PHPMailer/SugarPHPMailer does not meet modern security standards(or google's standards) and therefore blocks attempts to connect to it. You should receive an alert telling you this btw when you try to send the test mail. If this answers your question, cool otherwise sorry for the long post. Good luck!!
@KipchirchirIan Yes, I have "Allow less secure access" turned on. I have also found that you cannot send a test email from a different account SuiteCRM account, even it that account has Administrative rights. Hopefully we can get this resolved soon. Gmail connectivity is standard for most clients.
Hi @KipchirchirIan, your solution worked for me, thanks!
We run two instances of SuiteCRM on 7.6.3. One works and the other doesn't. Gmail is the weapon of choice, and both servers are configured using the same details. The only difference is that the domain of one of the servers is not the same as the primary Google Apps domain. Could this be a factor? I must add that both domains are set up under Google Apps, but one is an alias.
@sigreer83
Which instance works for sending email, the one using the actual, canonical domain, or the one using the alias domain? I can guess but have to ask...
@ghermans this issue shouldn't be closed until it resolved. Still cannot get SuiteCRM to work with Gmail...
@abeo and others having a problem sending mail via gmail. I did an upgrade of existing system to WAMP 3.0.4 64bit, PHP 5.6.19, SuiteCRM 7.5.1 fresh install to which I just restored the DB - Mails would not send via smtp.gmail.com anymore. Our mail is Google Apps. I have a self signed certificate on the SuiteCRM server, so when I got below error in log I thought I would need to purchase a cert, but that is not the problem. Just keep reading.
I had the following error in php log :: Warning: stream_socket_enable_crypto(): SSL operation failed with code 1.
OpenSSL Error messages: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed.
I started the troubleshooting tips from this bug, suite forums, google and https://github.com/PHPMailer/PHPMailer/wiki/Troubleshooting that all pointed to my self signed certificate being the issue.
The thing that eventually got me the information I needed was :
openssl s_client -starttls smtp -crlf -connect smtp.gmail.com:587
from https://github.com/PHPMailer/PHPMailer/wiki/Troubleshooting#testing-ssl-outside-php
Which initially gave me errors due to mismatched Apache and OpenSSL binaries. Once I got those resolved, running "openssl s_client -starttls smtp -crlf -connect smtp.gmail.com:587" again (I am only listing the relevant part of the result :

Notice the Certificate chain and the verify error:num=19 just above the Certificate chain. That information had nothing to do with my self signed certificate.
I turned off my Avast Web/Mail Shield and everything works as before. I have not gone any further with the troubleshooting to see how to get past the issue without disabling Mail shield.
running "openssl s_client -starttls smtp -crlf -connect smtp.gmail.com:587" again, this was the result

error:num=20 is not a problem as per PHPMailer troubleshooting.
My first post here on GitHub so apologies if things aren't clear.
Update :
After my changes mentioned, when a user with admin rights, not the Admin user itself try to send the test mail in email settings, they get Error:SMTP connect() failed. https://github.com/PHPMailer/PHPMailer/wiki/Troubleshooting. even though mail fetching and sending is working.
When logging in as the Admin user I do not get the error. I am not able to spend more time at this stage as mail is currently working except for the Test message when executed by other user with admin rights.
I'm absolutely affected by this.
Everything was working dandy ho and then I moved web hosts and everything stopped working. I thought that might be the problem...
Now I think it might be my Let's Encrypt SSL certificate on the domain?
I"m on shared hosting, I get this
Error:SMTP connect() failed. https://github.com/PHPMailer/PHPMailer/wiki/Troubleshooting
i've tried Gmail (used to work when others failed) and I've tried my preferrable non-gmail email. Neither work. All kick back same error.
I have done this: public $SMTPAutoTLS = false;
No go.
Any help on this would be awesome as it's mission critical to our company. Thanks!
I should clarify the following details:
-i was using 7.4 when I wrote the post above
-i upgraded to 7.6 (today's version) to try to fix (didn't work)
-I have a let's encrypt verified ssl cert but I will admit that 'parts of the page are not secure' but it's not a fault of the certificate and I dont see that would be the issue...
I really badly need this working so whatever you need me to do to help get you what you need to fix, I am your man! :)
@ghermans We tried all the above stated fixes but its not working anymore. Its very difficult to manage crm without notifications. can you please check with this issue on priority. like there are many persons reporting the same here as well as on forum itself.
Yes, it has been six days with a fully 'dead' crm and the company is now looking at me as if I had made a bad decision. I am ready and willing to help you with anything you need for testing. I'm ready and willing. Just tell me what to do and I will do it. Nothing I have tried is working. I also posted this this morning over at the suitecrm forum and it looks like some guy has found a solution by mucking with the code. I am not capable of this and I cannot risk killing our business crm...
Thanks!!
@opensourcecrm i will check this right now.
Thanks guys! I just had some weird thing happen today which may or may not help. I contacted our shared hosting provider and they did some tweaks to the cron job and suddenly I got a flood of email notifications in my inbox but the same problem (above) remains and it kicks back the smtp error. So I was wondering if the issue lies somewhere in the cron settings. But I don't know crap so just toss this if it's crap. ha.
Now I'm getting this:
Tue Jul 26 16:52:36 2016 [856234][1][FATAL] SugarPHPMailer encountered an error: SMTP connect() failed. https://github.com/PHPMailer/PHPMailer/wiki/Troubleshooting
Tue Jul 26 16:52:38 2016 [856234][1][FATAL] SugarPHPMailer encountered an error: An outgoing mail server is not configured to send emails. Please configure an outgoing mail server or select an outgoing mail server for the mail account that you are using in Settings >> Mail Account.
Tue Jul 26 16:52:38 2016 [856234][1][FATAL] SugarPHPMailer encountered an error: SMTP connect() failed. https://github.com/PHPMailer/PHPMailer/wiki/Troubleshooting
Tue Jul 26 16:52:40 2016 [856234][1][FATAL] SugarPHPMailer encountered an error: An outgoing mail server is not configured to send emails. Please configure an outgoing mail server or select an outgoing mail server for the mail account that you are using in Settings >> Mail Account.
Tue Jul 26 16:52:40 2016 [856234][1][FATAL] SugarPHPMailer encountered an error: SMTP connect() failed. https://github.com/PHPMailer/PHPMailer/wiki/Troubleshooting
Tue Jul 26 16:53:00 2016 [858388][1][FATAL] could not load RHS in Task
Tue Jul 26 16:53:01 2016 [858577][1][FATAL] Job runs too frequently, throttled to protect the system.
Tue Jul 26 16:53:02 2016 [858388][1][FATAL] could not load RHS in Task
Tue Jul 26 16:53:04 2016 [858388][1][FATAL] could not load RHS in Task
Tue Jul 26 16:53:06 2016 [858388][1][FATAL] could not load RHS in Task
Tue Jul 26 16:53:07 2016 [858388][1][FATAL] could not load RHS in Task
Tue Jul 26 16:53:09 2016 [858388][1][FATAL] could not load RHS in Task
Tue Jul 26 16:53:11 2016 [858388][1][FATAL] could not load RHS in Task
Tue Jul 26 16:53:13 2016 [858388][1][FATAL] could not load RHS in Task
Tue Jul 26 16:53:15 2016 [858388][1][FATAL] could not load RHS in Task
Tue Jul 26 16:53:18 2016 [858388][1][FATAL] could not load RHS in Task
Tue Jul 26 16:53:20 2016 [858388][1][FATAL] could not load RHS in Task
Tue Jul 26 16:53:22 2016 [858388][1][FATAL] could not load RHS in Task
Tue Jul 26 16:53:24 2016 [858388][1][FATAL] could not load RHS in Task
Tue Jul 26 16:53:26 2016 [858388][1][FATAL] could not load RHS in Task
Tue Jul 26 16:53:27 2016 [858388][1][FATAL] could not load RHS in Task
Tue Jul 26 16:53:30 2016 [858388][1][FATAL] could not load RHS in Task
Tue Jul 26 16:53:32 2016 [858388][1][FATAL] could not load RHS in Task
Tue Jul 26 16:53:34 2016 [858388][1][FATAL] could not load RHS in Task
Tue Jul 26 16:53:36 2016 [858388][1][FATAL] could not load RHS in Task
Tue Jul 26 16:53:38 2016 [858388][1][FATAL] could not load RHS in Task
Tue Jul 26 16:53:40 2016 [858388][1][FATAL] could not load RHS in Task
Tue Jul 26 16:53:42 2016 [858388][1][FATAL] could not load RHS in Task
Tue Jul 26 16:53:44 2016 [858388][1][FATAL] could not load RHS in Task
Tue Jul 26 16:53:46 2016 [858388][1][FATAL] could not load RHS in Task
Tue Jul 26 16:53:47 2016 [858388][1][FATAL] could not load RHS in Task
Tue Jul 26 16:56:40 2016 [861938][1][FATAL] Job runs too frequently, throttled to protect the system.
Tue Jul 26 16:57:02 2016 [862265][1][FATAL] Job runs too frequently, throttled to protect the system.
Tue Jul 26 17:03:39 2016 [866191][3d21a5e4-2642-3747-d41f-565012ad11bc][FATAL] SugarPHPMailer encountered an error: The outbound mail server selected for the mail account you are using is invalid. Check the settings or select a different mail server for the mail account.
Tue Jul 26 17:03:39 2016 [866191][3d21a5e4-2642-3747-d41f-565012ad11bc][FATAL] SugarPHPMailer encountered an error: SMTP connect() failed. https://github.com/PHPMailer/PHPMailer/wiki/Troubleshooting
Tue Jul 26 17:04:21 2016 [869421][3d21a5e4-2642-3747-d41f-565012ad11bc][FATAL] SugarPHPMailer encountered an error: The outbound mail server selected for the mail account you are using is invalid. Check the settings or select a different mail server for the mail account.
Tue Jul 26 17:04:21 2016 [869421][3d21a5e4-2642-3747-d41f-565012ad11bc][FATAL] SugarPHPMailer encountered an error: SMTP connect() failed. https://github.com/PHPMailer/PHPMailer/wiki/Troubleshooting
Tue Jul 26 17:04:58 2016 [869910][3d21a5e4-2642-3747-d41f-565012ad11bc][FATAL] SugarPHPMailer encountered an error: The outbound mail server selected for the mail account you are using is invalid. Check the settings or select a different mail server for the mail account.
Tue Jul 26 17:04:58 2016 [869910][3d21a5e4-2642-3747-d41f-565012ad11bc][FATAL] SugarPHPMailer encountered an error: SMTP connect() failed. https://github.com/PHPMailer/PHPMailer/wiki/Troubleshooting
Same issue , don't have the solution right now.
The only good news here is that there is company in the misery! I thought I was alone for the longest time so this is actually promising. Again, let me know how I can help you smart people.
I would love to see this resolved so that I can recommend SuiteCRM to clients...
well, apparently I couldn't figure out how to add a post to this github stuff and faile above but here is a direct link to a fine chap who made it work. He admits it's a band aid fix but I think if I post this right here someone will be able to 'really fix it' quickly:
Here is the link
I was having the same problem, and looked like crazy trying to fix it. None of the solutions worked. I use Google Apps for Work, which used smtp.gmail.com. After almost giving up I realized the problem is not with PHPmailer, but with the Admin->Email Settings GUI page. It was working all along. The problem is that when you enter this page the password is not set, so when you click the test button it fails. If however, you click on "Change password" and then (WITHOUT CLICKING SAVE FIRST) click the test button, it works. so there must be a bug where the settings are taken from the page, but the password is not right, but once you enter it is ok. At least this was my problem.
I tried what you say here and it's not working for me as much as I wish it was. However, it kind of does 'feel' like it is someting wiht the GUI and the order in which these credentials are written to the system. Ive tried many different combos of saving and re-entering and SSL and TLS and 24.7 million other options but I'm left still pulling my last hair out...sucker won't come out.
I tried @gitnito 's suggestion and it does not work for me.
I know it would be offtopic, but if you want to save your time and money, just buy new domain and establish new mail, redirect all mail from gmail and keep using CRM with new mail server. forget about gmail.
Or go back to an older Version of suitecrm. It will take too long until there is a fix for any bug.
I have a non-gmail email set up, @humanistas and it also does exactly the same thing - not work. I would also like to report that the whole reason I _upgraded_ to the most recent version of suitecrm (i'm pretty dang busy) is because it was also _not_ working in the older version I was using. This is why I have started to wonder if the bug is in fact a bug related to how suite crm works on shared hosting. Are all of the victims on shared hosting? Is it working perfectly on non-shared hosting? There was one day two days ago at 9:53am when 25 emails from suite crm dumped rapidly into my inbox so for a flash, it was working. Explain _that_!
Hey I am not sure if the same thing work with you or not. Still its a bug with the outbound email configuration. I tried all the code level corrections suggested by the other contributors. but there is no success.
I just made one change with the password. I just created a password with Letter and number (Password123) its get configured and working fine. But when i change the password with some regular expression (Password=&123$%^) it repeat the same error message. if anyone would like to try with simple password with letters and number hopefully it will work. But ultimately its a bug need to be fix.
great idea! My passwords are like yours so maybe that's it I'll test. stand by for 30 minutes
ok, team. i can now confirm that it seems to be a combination of @gitnito and @opensourcecrm most recent post. When I had my first password, it was a _very_ secure password generated by my password generated. It contained symbols, numbers, special characters - everything. When I had this password, I could _not_ do @gitnito suggestion above with entering the password _without saving_ and have the test email send. However, when I followed @opensourcecrm 's suggestion to change the password to something more simple, _now_ I could perform the test email successfully, but only if I do not click save. If I click 'save' it exits me from the email settings screen and then when I go back in and simply do the test email (without touching the password change) it did _not_ work (again). So it appears the bug is related to:
a) the system not being able to handle special characters in the password correctly and
b) some problem in the page itself where password changes are not writing correctly and saving permanently (some problem with the 'save' feature).
I feel like we are close. A few more testers trying this out and we might find it and confirm it?
update: I also can now confirm that gmail does _not_ work at all with the tests above and I'm 99% sure that this is because my shared hosting company said that gmail _cannot_ act as a mail relay service on their shared hosting. When I use the regular non-gmail it works as per my post 2 minutes ago. So if anyone is having issues just with gmail it's probably because your host isn't allowing it. My former host, before migrating, probably did allow it....
update 3: i also have confirmed that exactly the same bug exists in the 'admin/outbound email' section. If you run the same tests, the same results exist. If you create an outbound mail server in this section, try to write the changes with the save button, nothing saves - including the most recent email to which you sent the test email. Also, you get the github smtp error fail message as per usual in the other section. However if you do the 'password change' method and _before pressing save_ send the test email after entering the correct password, the email sends. So same issue(s) here too. It seems like with this information now someone who programs should be able to figure it out....
update 4: just for fun I went into cpanel and changed my php versions from 5.5 to 5.4 to 5.3 and 5.6 and 7.0 and none of that helped. I read in some post that might help and that new PHP affects this somehow but I was unable to find a victory. My previous updates to this post all work the same no matter which version of PHP is running on the shared host.
update #5 - crazy! at 9:53am, just exactly the same minute as yesterday, a bunch of suitecrm emails came out to my inbox! what in the world is going on?
attached is a screenshot of the suitecrm error logs (fatal setting) for that moment when the emails cam through successfully

@humanistas your solution is not working, since i don't use gmail.
I don't know if this spew from my hosting provider will lead to any new ideas to anyone but while I was trying to fix this on the hosting side, they sent this:
2016-07-27 09:53:05 1bSS4v-003shR-IM [email protected] R=barracuda_route T=remote_smtp H=barmail1.idig.net [64.34.111.254] X=TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256 CV=yes C="250 Ok: queued as ED26E2FB0F"
they said before this they noted a problem with 'barracuda email'. They said 'it's resolved now' but when I went to try all the above steps in this bug, it still did not save and work properly sending the test email...
hey everyone. I have some good news I think. It looks like I have discovered two things that have made my system work. I haven't had enough time to a) get all the detailed answers from my hosting company and b) test my system thoroughly but i wanted to get this up ASAP for everyone else to start trying.
I hope this leads others back to victory and look forward to reporting back that everything is working but I'm still having an issue with one workflow notification not working but it might be my own problem...
Thanks @wayneoutthere, this is exactly what I said 10 days ago, my apologies if it was not clear.
I think everyone having this problem should:
Report their findings as it would seem that we are trying to debug 2 different issues here
Closing this one, if you still have a problem create a new issue
I was having the same problem as most people (SMTP connect() failed. https://github.com/PHPMailer/PHPMailer/wiki/Troubleshooting) on this thread and found nothing worked (I notice that some of the suggestions have already been implemented into suitecrm) however when I used a different gmail account (no other accounts worked either) with no special characters just numbers and letters it work with not issues. This seems to be an issue that could do with being sorted
SOLVED:
i had the same issue, Version 7.7.5
i was using Gmail for connection,
Solved by "Less secure apps to TURN ON" in the gmail settings.
go here:
https://www.google.com/settings/security/lesssecureapps
For those requiring email security, many industries which mandate full security, for instance, the financial industry, competitive fields, govts, health care industry, standards mandating full encryption to maintain privacy of all patient related communications, there's a way to solve this gmail issue without the use of enabling "less secure apps" ("LSA"). With LSA, SuiteCRM is providing a cleartext password to login to gmail (trying to login with mechanism "LOGIN-PLAIN"), however gmail has disabled login-plain by default because of the high risk. When an app tries to login with a cleartext password, it's because the app has saved the password, and indeed, SuiteCRM app has saved your email cleartext password on the SuiteCRM server. Doing so is highly discouraged by security standards because of the risk of complete google account theft or full data leakage by evil sysadmins and hackers who get in and take a full backup the app files and database including all clear password and keys.
The solution is to use XOAUTH2 mechanism to login to gmail. Much php code exists to do this.
https://github.com/PHPMailer/PHPMailer/wiki/Using-Gmail-with-XOAUTH2
https://github.com/PHPMailer/PHPMailer/wiki/Gmail-XOAUTH2-Using-Google-API-Client
gunnicom trick :
public $SMTPAutoTLS = false;
Worked for me on Community Edition 6.5.25
Some one Find Solution??? I need To configure SMTP gmail setting in suitecrm
@karthik5595 are you on shared hosting or self-hosting?
@wayneoutthere I'm using my local wamp server (Self Hosting)
I not idea the configuration suiteCRM and elastisk please help me.!!!!
Hi,
I am having a problem with mail on clients server.
When I try to send test mail, I get after 5min error:
Error:SMTP connect() failed. https://github.com/PHPMailer/PHPMailer/wiki/Troubleshooting
Globally problem is noticed when Assigned To user is changed. Then system tries to send a mail, and the whole saving process takes 5 min.
The worst part is that there is nothing in log (apache/error.log or suitecrm.log).
I tried adding debug line but got nothing.
The only clue that I have is that server telnet to smtp.gmail.com or any other mail server is not working. Can this be the only thing that is wrong, and how to confirm that?
Br,
Filip
SuiteCRM: 7.7.8
DB: MySQL
PHP: PHP 5.6.33-0+deb8u1
i cant get your issue .. can you explain breafly!!!
On Tue, Apr 17, 2018 at 4:51 PM, Filip Ćorluka notifications@github.com
wrote:
Hi,
I am having a problem with this mail on clients server.
When I try to send test mail, I get after 5min error:—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/salesagility/SuiteCRM/issues/1123#issuecomment-381954728,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Af04KF7B5mvoDDcHm4F35f-tFTFuNWAIks5tpdA8gaJpZM4H0BOS
.
--
Thanks & Regards,
Karthik.K.S,
9659843493
I get into Admin->Email Settings, and click on Send Test Email.
Popup for performing task comes out, and stays for 5min.
After that I get : Error:SMTP connect() failed. https://github.com/PHPMailer/PHPMailer/wiki/Troubleshooting
Nothing is written in logs (apache log or suitecrm log).
I have tried from a server console ping to my mail server, that is OK; but telnet won't do.
Because of this mail sending, when a user is assigned to record (user should be notified when assigned), saving of that change lasts 5 min (same as sending mail).
ok..What can i do?
On Tue, Apr 17, 2018 at 10:48 PM, Filip Ćorluka notifications@github.com
wrote:
I get into Admin->Email Settings, and click on Send Test Email.
Popup for performing task comes out, and stays for 5min.
After that I get : Error:SMTP connect() failed.
https://github.com/PHPMailer/PHPMailer/wiki/Troubleshooting
Nothing is written in logs (apache log or suitecrm log).I have tried from a server console ping to my mail server, that is OK; but
telnet won't do.Because of this mail sending, when a user is assigned to record, saving of
that change lasts 5 min (same as sending mail).—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/salesagility/SuiteCRM/issues/1123#issuecomment-382073082,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Af04KCM6arH07eFFyGM1sz4LXdNVMEbjks5tpiQBgaJpZM4H0BOS
.
--
Thanks & Regards,
Karthik.K.S,
9659843493
Is there some way to verify that sending mail is broken because of server connection and not because of SuiteCRM?
i dont know the exact reason .. time to off .. can u remember me tommorow..
Sorry
On Tue, Apr 17, 2018 at 10:51 PM, Filip Ćorluka notifications@github.com
wrote:
Is there some way to verify that sending mail is broken because of server
connection and not because of SuiteCRM?—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/salesagility/SuiteCRM/issues/1123#issuecomment-382074021,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Af04KJr9wM6-YaZjko4r4qjYnkYX26Gkks5tpiSvgaJpZM4H0BOS
.
--
Thanks & Regards,
Karthik.K.S,
9659843493
Hi All,
I got the same (An email error occurred:SMTP connect() failed. https://github.com/PHPMailer/PHPMailer/wiki/Troubleshooting ) issue the version of my SuiteCRM is 7.11.18 .
Is anyone can resolved it?
Thanks
Most helpful comment
Same issue using gmail for outgoing mail config. Simply turning off TLS did not work for me. I am currently bypassing SMTP and using sendmail by commenting out lines 140-159 in /include/SugarPHPMailer.php and on line 160 adding $this->Mailer = "sendmail";