[weiminliou]

I'm using Processmaker3.2.1-Community on Windows Server2012.
I used hotmail as my email server,and it works fine.
But When I change to company mail account built on gmail,it doesn't work.

Hotmail settings:
smtp.live.com
port:25
sender account:*****_Ming@hotmail.com
sender email:*****_Ming@hotmail.com
sender name:Ming
use TLS

Gmail settings:
smtp.gmail.com
port:465
sender account:bpm@***.com.tw
sender email:bpm@***.com.tw
sender name:bpm
use TLS

I've tried port:587+TLS or port:465+SSL,and it just spined and nothing happened,but when I tried port:465+TLS,I got the error message as title.
I also change the gmail setting:allow low-security program...,but it still doesn't work.

Please give me some advices.Thank you for your watching and really sorry for my poor English.

[amosbatto]

Have you configured your Gmail account to Enable IMAP and use Access for Less Secure Apps?

These settings worked for me:

EmailConfigurationGmail.png (31.57 KiB) Viewed 19024 times

[weiminliou]

Yes,I've configured my Gmail account to Enable IMAP and use Access for Less Secure Apps,but I got the same error message.

465+SSL:

465+ssl.JPG (47.28 KiB) Viewed 19021 times

465+TLS:

465+tls.JPG (42.18 KiB) Viewed 19021 times

P.S. When I used my personal hotmail account,it works normally.

hotmail settings.JPG (56.04 KiB) Viewed 19013 times

hotmail.JPG (42.93 KiB) Viewed 19013 times

Thank you for your immediate response.

[amosbatto]

Try setting up Gmail 2-Step Verification as explained on the wiki.

Is your email bpm@xxxxxxx.com.tw a business account from Google? That is what we are using at ProcessMaker and it works. You should check that your firewall isn't blocking port 465. Do pings and the other tests listed on the wiki from your ProcessMaker server verify that you can connect to smtp.gmail.com.

[weiminliou]

I've tried setting up Gmail 2-Step Verification,but the problem still remains.

Yes,bpm@XXX.com.tw is a business account from google,and I also checked that my firewall isn't blocking port 465,port 587 and port 25.
(I've done the test listed on the wiki.I also set bpm@XXX.com.tw as my Outlook mail account,and mails can be sent correctly.)

[amosbatto]

What operating system is your PM server using? If you are using Linux, then you can enter this command to verify that nothing is blocking the connection:
openssl s_client -starttls smtp -connect smtp.gmail.com:587 -crlf -ign_eof

You should see output like the following:

Code: Select all

CONNECTED(00000003)
depth=1 C = US, O = Google Trust Services, CN = Google Internet Authority G3
verify error:num=20:unable to get local issuer certificate
verify return:0
---
Certificate chain
 0 s:/C=US/ST=California/L=Mountain View/O=Google Inc/CN=smtp.gmail.com
   i:/C=US/O=Google Trust Services/CN=Google Internet Authority G3
 1 s:/C=US/O=Google Trust Services/CN=Google Internet Authority G3
   i:/OU=GlobalSign Root CA - R2/O=GlobalSign/CN=GlobalSign
---
Server certificate
-----BEGIN CERTIFICATE-----
MIIEgjCCA2qgAwIBAgIIS/fVM8cWjU8wDQYJKoZIhvcNAQELBQAwVDELMAkGA1UE
BhMCVVMxHjAcBgNVBAoTFUdvb2dsZSBUcnVzdCBTZXJ2aWNlczElMCMGA1UEAxMc
R29vZ2xlIEludGVybmV0IEF1dGhvcml0eSBHMzAeFw0xNzEyMTMxNDExNTRaFw0x
ODAzMDcxMzAzMDBaMGgxCzAJBgNVBAYTAlVTMRMwEQYDVQQIDApDYWxpZm9ybmlh
MRYwFAYDVQQHDA1Nb3VudGFpbiBWaWV3MRMwEQYDVQQKDApHb29nbGUgSW5jMRcw
FQYDVQQDDA5zbXRwLmdtYWlsLmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC
AQoCggEBAIgP1KzV9wr79IyAn5YV4APTkEPNKUGRgYFq3mZMPKn/ozFG0h7W2WU7
dQyij8b97bbqvEm8N1wQKmbGA8TIeKBpTZ/wGwnBbLzVRj9gN+FxicfmQzG+8gYR
4RW1BlmhSATDNLraujWLLsklrkVfRTz7MLgkAz8MpNES6kIZl3+TS8eTVtPYrHuJ
WhrvYFfW6JnPP/nc+cGRw4CZa4BdCeFwaLT/7WkHkpPS0Ru+uajdp2yxdBpZVVvY
s/JNUztaq6Mb8zhytq4zD4PeHItes1vMKpTx7rCGcrmS/2ZdGBX9y874XXBlfaE1
FQuUxrWQd4/c96Al7fbBXyx4W9uTs/MCAwEAAaOCAUIwggE+MBMGA1UdJQQMMAoG
CCsGAQUFBwMBMBkGA1UdEQQSMBCCDnNtdHAuZ21haWwuY29tMGgGCCsGAQUFBwEB
BFwwWjAtBggrBgEFBQcwAoYhaHR0cDovL3BraS5nb29nL2dzcjIvR1RTR0lBRzMu
Y3J0MCkGCCsGAQUFBzABhh1odHRwOi8vb2NzcC5wa2kuZ29vZy9HVFNHSUFHMzAd
BgNVHQ4EFgQUuZBA91aNuL9nta8ljMfvOueLliEwDAYDVR0TAQH/BAIwADAfBgNV
HSMEGDAWgBR3wrhQmmd2drEtwobQg6B+pn66SzAhBgNVHSAEGjAYMAwGCisGAQQB
1nkCBQMwCAYGZ4EMAQICMDEGA1UdHwQqMCgwJqAkoCKGIGh0dHA6Ly9jcmwucGtp
Lmdvb2cvR1RTR0lBRzMuY3JsMA0GCSqGSIb3DQEBCwUAA4IBAQA3lnti511iKlP+
Kz7yCLfE3RVH0xG6JU99XRdy+tPPP4+in9H7GpW6cyzu7Wx7XLr9qx3f6QWera08
T37Zneuf0gYNPvPlfmYw+mi3DpRZR4YCDxQgRqXr08RPtS9jdyAC7uWD2lhptTrj
eF1qqHgcHsycnxximPW3KIFjS8PJ1Lckc3oNRQw8SRfUXxSXkmGasTraqiF2Ha3O
NZuPBvQ/9f+kk06i4+ceJ/FUXE9v5EQHK6+oVSXJE1/vUBxgn8GyNPaa+mF8cPHv
1kCi4kfKl7YYs8AhaNJ4mtMP1V1wDVzRZdNOYunXtwyuioMKTzJAniETwUdEhCym
xXc3dZUu
-----END CERTIFICATE-----
subject=/C=US/ST=California/L=Mountain View/O=Google Inc/CN=smtp.gmail.com
issuer=/C=US/O=Google Trust Services/CN=Google Internet Authority G3
---
No client certificate CA names sent
---
SSL handshake has read 3236 bytes and written 450 bytes
---
New, TLSv1/SSLv3, Cipher is ECDHE-RSA-AES128-GCM-SHA256
Server public key is 2048 bit
Secure Renegotiation IS supported
Compression: NONE
Expansion: NONE
SSL-Session:
    Protocol  : TLSv1.2
    Cipher    : ECDHE-RSA-AES128-GCM-SHA256
    Session-ID: E9CF97AE7F324605B4CDC6EABEF270C7CDE7A2386F17E0A2A8835CBDD265BD44
    Session-ID-ctx: 
    Master-Key: 9DA65E69FAED86F313A5C88E2AB9EFEF680E322CC85CA93CDF83D09438E2EBA93FAEE267692B3833BD86C11A004AD4ED
    Key-Arg   : None
    PSK identity: None
    PSK identity hint: None
    SRP username: None
    TLS session ticket lifetime hint: 100800 (seconds)
    TLS session ticket:
    0000 - 00 86 4f e1 38 49 21 e8-f7 7e 9a 44 4a 31 bb 28   ..O.8I!..~.DJ1.(
    0010 - f9 9e a5 ef 5a ad 53 f7-a1 00 e6 bc e3 21 f6 16   ....Z.S......!..
    0020 - ed 1d 12 fb c0 23 91 79-62 73 3e 3f d3 d8 ea 6f   .....#.ybs>?...o
    0030 - 92 a1 d1 d7 89 2c 68 6b-4e a6 58 30 07 c3 0b 2c   .....,hkN.X0...,
    0040 - 5e 77 c7 c1 94 13 ea e6-66 e6 56 14 cd 05 c0 09   ^w......f.V.....
    0050 - 62 0c 38 ee 4d 83 31 62-bc d9 58 aa 21 56 03 06   b.8.M.1b..X.!V..
    0060 - ed 62 4b 7c fd d4 86 e7-44 a7 c9 bb 0b 9c 09 27   .bK|....D......'
    0070 - e7 7e 68 ba 29 26 38 a6-58 4c 6f 1c 30 6d ea 78   .~h.)&8.XLo.0m.x
    0080 - 82 8b 74 f3 6c 65 33 1d-a0 c7 59 bb 46 1d 37 e9   ..t.le3...Y.F.7.
    0090 - 9d 67 b0 85 a7 84 f3 51-fe 54 1e d3 ff f1 bc 38   .g.....Q.T.....8
    00a0 - ab 48 5d 27 21 40 8a db-13 4a 07 c4 50 69 a8 ae   .H]'!@...J..Pi..
    00b0 - 4d 9b 0a d2 23 4a 29 b0-67 35 a8 82 91 55 39 9f   M...#J).g5...U9.
    00c0 - 9b 8c 3f 86 67 90 11 50-a8 6c 74 40 a1 49 0e a7   ..?.g..P.lt@.I..
    00d0 - 4c cc 4d fe ef                                    L.M..

    Start Time: 1516167319
    Timeout   : 300 (sec)
    Verify return code: 20 (unable to get local issuer certificate)
---
250 SMTPUTF8

Then enter: quit

If you are using PM on a Windows machine, then you can probably use the same command by first downloading and installing openssl:
https://wiki.openssl.org/index.php/Binaries
(I've never tried this, but let me know if it works.)

[weiminliou]

This is the output when I enter the command(I am using windows server2012):

C:\Users\Administrator>openssl s_client -starttls smtp -connect smtp.gmail.com:5
87 -crlf -ign_eof
WARNING: can't open config file: /usr/local/ssl/openssl.cnf
CONNECTED(000001D0)
depth=1 C = US, O = Google Trust Services, CN = Google Internet Authority G3
verify error:num=20:unable to get local issuer certificate
---
Certificate chain
0 s:/C=US/ST=California/L=Mountain View/O=Google Inc/CN=smtp.gmail.com
i:/C=US/O=Google Trust Services/CN=Google Internet Authority G3
1 s:/C=US/O=Google Trust Services/CN=Google Internet Authority G3
i:/OU=GlobalSign Root CA - R2/O=GlobalSign/CN=GlobalSign
---
Server certificate
-----BEGIN CERTIFICATE-----
MIIEgjCCA2qgAwIBAgIIS/fVM8cWjU8wDQYJKoZIhvcNAQELBQAwVDELMAkGA1UE
BhMCVVMxHjAcBgNVBAoTFUdvb2dsZSBUcnVzdCBTZXJ2aWNlczElMCMGA1UEAxMc
R29vZ2xlIEludGVybmV0IEF1dGhvcml0eSBHMzAeFw0xNzEyMTMxNDExNTRaFw0x
ODAzMDcxMzAzMDBaMGgxCzAJBgNVBAYTAlVTMRMwEQYDVQQIDApDYWxpZm9ybmlh
MRYwFAYDVQQHDA1Nb3VudGFpbiBWaWV3MRMwEQYDVQQKDApHb29nbGUgSW5jMRcw
FQYDVQQDDA5zbXRwLmdtYWlsLmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC
AQoCggEBAIgP1KzV9wr79IyAn5YV4APTkEPNKUGRgYFq3mZMPKn/ozFG0h7W2WU7
dQyij8b97bbqvEm8N1wQKmbGA8TIeKBpTZ/wGwnBbLzVRj9gN+FxicfmQzG+8gYR
4RW1BlmhSATDNLraujWLLsklrkVfRTz7MLgkAz8MpNES6kIZl3+TS8eTVtPYrHuJ
WhrvYFfW6JnPP/nc+cGRw4CZa4BdCeFwaLT/7WkHkpPS0Ru+uajdp2yxdBpZVVvY
s/JNUztaq6Mb8zhytq4zD4PeHItes1vMKpTx7rCGcrmS/2ZdGBX9y874XXBlfaE1
FQuUxrWQd4/c96Al7fbBXyx4W9uTs/MCAwEAAaOCAUIwggE+MBMGA1UdJQQMMAoG
CCsGAQUFBwMBMBkGA1UdEQQSMBCCDnNtdHAuZ21haWwuY29tMGgGCCsGAQUFBwEB
BFwwWjAtBggrBgEFBQcwAoYhaHR0cDovL3BraS5nb29nL2dzcjIvR1RTR0lBRzMu
Y3J0MCkGCCsGAQUFBzABhh1odHRwOi8vb2NzcC5wa2kuZ29vZy9HVFNHSUFHMzAd
BgNVHQ4EFgQUuZBA91aNuL9nta8ljMfvOueLliEwDAYDVR0TAQH/BAIwADAfBgNV
HSMEGDAWgBR3wrhQmmd2drEtwobQg6B+pn66SzAhBgNVHSAEGjAYMAwGCisGAQQB
1nkCBQMwCAYGZ4EMAQICMDEGA1UdHwQqMCgwJqAkoCKGIGh0dHA6Ly9jcmwucGtp
Lmdvb2cvR1RTR0lBRzMuY3JsMA0GCSqGSIb3DQEBCwUAA4IBAQA3lnti511iKlP+
Kz7yCLfE3RVH0xG6JU99XRdy+tPPP4+in9H7GpW6cyzu7Wx7XLr9qx3f6QWera08
T37Zneuf0gYNPvPlfmYw+mi3DpRZR4YCDxQgRqXr08RPtS9jdyAC7uWD2lhptTrj
eF1qqHgcHsycnxximPW3KIFjS8PJ1Lckc3oNRQw8SRfUXxSXkmGasTraqiF2Ha3O
NZuPBvQ/9f+kk06i4+ceJ/FUXE9v5EQHK6+oVSXJE1/vUBxgn8GyNPaa+mF8cPHv
1kCi4kfKl7YYs8AhaNJ4mtMP1V1wDVzRZdNOYunXtwyuioMKTzJAniETwUdEhCym
xXc3dZUu
-----END CERTIFICATE-----
subject=/C=US/ST=California/L=Mountain View/O=Google Inc/CN=smtp.gmail.com
issuer=/C=US/O=Google Trust Services/CN=Google Internet Authority G3
---
No client certificate CA names sent
Peer signing digest: SHA256
Server Temp Key: ECDH, P-256, 256 bits
---
SSL handshake has read 3238 bytes and written 468 bytes
---
New, TLSv1/SSLv3, Cipher is ECDHE-RSA-AES128-GCM-SHA256
Server public key is 2048 bit
Secure Renegotiation IS supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
SSL-Session:
Protocol : TLSv1.2
Cipher : ECDHE-RSA-AES128-GCM-SHA256
Session-ID: 7B7B3A8AF50193546B52A19B926B391AE99D487F72D6A9EF37505D1D1E9627C6

Session-ID-ctx:
Master-Key: 41D4E87F701A4E76ED6E1634309535524CB4EDA32E52B47D634556FBEF91517E
7598225B68AEDD70D63944C6EE2E4928
Key-Arg : None
PSK identity: None
PSK identity hint: None
SRP username: None
TLS session ticket lifetime hint: 100800 (seconds)
TLS session ticket:
0000 - 00 1a a8 78 c3 2e 20 3c-ef 93 f7 fb d7 de c0 92 ...x.. <........
0010 - 09 77 be 0b b7 14 27 6f-e7 02 61 5b 28 af 31 da .w....'o..a[(.1.
0020 - 8b a7 98 e6 18 92 23 c6-3f 34 ea 64 e8 de 23 55 ......#.?4.d..#U
0030 - 65 57 68 96 92 57 a3 b1-0b 35 fe 60 57 a4 cf 2e eWh..W...5.`W...
0040 - 98 d4 45 44 c3 af 5b 29-8e 41 f7 bf d2 60 be 09 ..ED..[).A...`..
0050 - fb 51 47 fd ff f9 80 63-cd f6 b6 42 c6 f4 fd 08 .QG....c...B....
0060 - 4a 06 7f b4 1e f0 08 98-5e 2a 1a d7 86 b3 eb 10 J.......^*......
0070 - 04 5b 95 b2 15 d4 4f f9-bb 02 ba de a2 fb 8c 1d .[....O.........
0080 - 04 6d b0 68 b9 88 8b 29-06 3d 6c c5 22 bc 95 d1 .m.h...).=l."...
0090 - 57 b3 52 ea ef 1e a2 12-95 49 e3 7b 73 fe d1 cb W.R......I.{s...
00a0 - b0 93 c1 1e cd 58 fa 20-14 8b 0e 8c 64 71 b4 46 .....X. ....dq.F
00b0 - 96 a2 55 60 ff ee 77 03-f8 84 99 1c 10 f2 dd df ..U`..w.........
00c0 - 39 28 89 90 8b 47 fa ec-e3 85 c0 da 35 8c ea 96 9(...G......5...
00d0 - 18 25 95 74 1a .%.t.

Start Time: 1516235433
Timeout : 300 (sec)
Verify return code: 20 (unable to get local issuer certificate)
---
250 SMTPUTF8
quit
221 2.0.0 closing connection k62sm8547056pga.42 - gsmtp
read:errno=0

[amosbatto]

Nothing is blocking you, so TLS and port 587 should work. I don't know anything else to recommend, so you need to ask Google or in a forum for experts in email.

[weiminliou]

OK,I will ask google or experts in email. Thanks for your reply. If anyone has another suggestions,I will really appreciate.

[weiminliou]

Is there any configuration I have to change with my company mail admin account? Does anyone try this before?

[amosbatto]

weiminliou, I recommend that you sign up for a Free ProcessMaker Trial and see if you can connect to your Gmail account from the ProcessMaker servers. If you can connect, then you know it is a configuration problem on your server or network. If you can't connect, then you need to configure your Gmail account. That will help you narrow down what is the problem.

[lazlo92]

Well-well, I'm not a chosen one who experienced that issue with gmail, I see. Actually, I hadn't found any solution to that, so I've just call it a day with google (I was trying to switch client for my own needs, so I was able to choose anything else), but suggestions here are completely puzzled me, because I thought that the key problem was that I had 2 step verification enabled on my account. Nevertheless, now I have to work with Outlook only and SMTP works fine here. It's quite another matter that Outlook is pretty bad with syncing data out of the box - it was torturing me for something about a week, before I've got to know that there are another tools to import mail to outlook here So I've got over this problem. But seriously, I may get it wrong, because I have only experience I had under my belt, but for me the very one solution is to migrate your company mail to another client, maybe Outlook for instance

[amosbatto]

This problem might be because you haven't made one of the cache files writable. I encountered this problem today. The error "Failed to connect to server" disappeared when I switched the port from 465 to 587.

The "SMTP Error: Could not connect to SMTP host." message disappeared when I changed the file permissions on my Linux installation, according to the instructions on the wiki:
http://wiki.processmaker.com/3.1/Proces ... ermissions

weiminliou, you should double check the file permissions of your ProcessMaker installation.

[petergroft]

How to fix issues with sending an email (SMTP)
Open the settings for your email in the application or device you are using.
Locate the outgoing SMTP server and its settings.
Check the current outgoing port and change it to 26 or 587.
Make sure any username and password fields are filled in if shown.
Save changes and test.

Regards,
Peter

[rachelgomez123]

Tips to fix -
Open the settings for your email in the application or device you are using.
Locate the outgoing SMTP server and its settings.
Check the current outgoing port and change it to 26 or 587.
Make sure any username and password fields are filled in if shown.
Save changes and test.

Regards,
Rachel Gomez