PHPJunkyard support forum

Script URL:
Version of script:
Hosting company:
URL of phpinfo.php:
URL of session_test.php:
What terms did you try when SEARCHING for a solution:

Write your message below:

I have updated to latest version: 2.7.5 and upgrades PHP to 7.1.2 and SQL to 10.2.11 and everything seems to work on all our helpdesks, except for den one that uses a Exchange server.

POP3 is working, but sending via SMTP has failed with this:

Resolving SMTP server domain "w*****.m**.dk"...
Connecting to SMTP server "w******.m**.dk" port 587...
Connected to SMTP server "w*****'.m**.dk".
S 220 M*******.m******.local Microsoft ESMTP MAIL Service ready at Fri, 5 Jan 2018 09:08:03 +0100
C EHLO help*****.m****'.dk
S 250-M*******.******.local Hello [***.***.***.***]
S 250-SIZE 83886080
S 250-PIPELINING
S 250-DSN
S 250-ENHANCEDSTATUSCODES
S 250-STARTTLS
S 250-AUTH GSSAPI NTLM
S 250-8BITMIME
S 250-BINARYMIME
S 250 CHUNKING
C STARTTLS
S 220 2.0.0 SMTP server ready
Starting TLS cryptograpic protocol

It looks like the same problem I had, when sending via Gmail, but that is still working normally, after I changes the line in PHP.ini to point at a specifik CAcert.pem file.

Any idea why Exchange is having problem now? it have been a problem since I updated the complete HESK system and SQL/PHP.

What is the exact error message (the one in the red box)?

The error message is this:

Resolving SMTP server domain "w*****.m**.dk"...
Connecting to SMTP server "w******.m**.dk" port 587...
Connected to SMTP server "w*****'.m**.dk".
S 220 M*******.m******.local Microsoft ESMTP MAIL Service ready at Fri, 5 Jan 2018 09:08:03 +0100
C EHLO help*****.m****'.dk
S 250-M*******.******.local Hello [***.***.***.***]
S 250-SIZE 83886080
S 250-PIPELINING
S 250-DSN
S 250-ENHANCEDSTATUSCODES
S 250-STARTTLS
S 250-AUTH GSSAPI NTLM
S 250-8BITMIME
S 250-BINARYMIME
S 250 CHUNKING
C STARTTLS
S 220 2.0.0 SMTP server ready
Starting TLS cryptograpic protocol

I have just redacted the IP and DNS info.

That's the log in the text box leading to the error, what does the error ABOVE the text box say?

It is fixed now. I found a temp solution, and forgot about it

We have some other connection problem with the exchange server, that was similar and they ende up being caused by certificate that was't correctly added into the Exchange server.

This fixed also the problem I had with HESK connecting to the server.

Thanks for the update. Are you able to share more details about your solution please in case others have the same problem?

Sorry for the late response.

The fix was done by a Exchange consultant. As far I can remember, he reimplemented the certificate to the exchange server, and that did the trick.

Thanks for the info, I hope it helps others with the same issue.