Error configuring IMAP - stream_socket_client Unknown Error: Page 2

Error configuring IMAP - stream_socket_client Unknown Error

sakbari

This how my file looks

// Attempt to connect to the mail server
$connect = $setting->getConnectionConfig();
// Let's go Brandon
//parent::connect($connect['host'], $connect['port'],
// $connect['ssl']);
parent::__construct($connect['host'], $connect['port'], $connect['ssl'], true);
parent::connect($connect['host'], $connect['port'],
$connect['ssl']);
// Attempt authentication based on MailBoxAccount settings

but it;s does nog work

KevinTheJedi

sakbari

You can apply my DIFF file above. If you don't know how to apply a diff file you can Google "how to apply a diff file"; it's very simple. Once the changes are applied you should restart the webserver and/or PHP-FPM (to ensure nothing is being cached) and retest.

Cheers.

KevinTheJedi

Chefkeks

After looking into this a little deeper the only changes we need to successfully disable certificate validation for IMAP/POP3 and SMTP are the following:

diff --git a/include/class.mail.php b/include/class.mail.php
index 1e347f5a4..441fcf450 100644
--- a/include/class.mail.php
+++ b/include/class.mail.php
@@ -315,8 +315,8 @@ namespace osTicket\Mail {
             // Attempt to connect to the mail server
             $connect = $setting->getConnectionConfig();
             // Let's go Brandon
-            parent::connect($connect['host'], $connect['port'],
-                    $connect['ssl']);
+            parent::__construct($connect['host'], $connect['port'],
+                    $connect['ssl'], true);
             // Attempt authentication based on MailBoxAccount settings
             $auth = $setting->getAuthCredentials();
             switch (true) {
@@ -657,7 +657,10 @@ namespace osTicket\Mail {
         // Build out SmtpOptions options based on SmtpAccount Settings
         private function buildOptions(AccountSetting $setting) {
             // Dont send 'QUIT' on __destruct()
-            $config = ['use_complete_quit' => false];
+            $config = [
+                'use_complete_quit' => false,
+                'novalidatecert' => true
+            ];
             $connect = $setting->getConnectionConfig();
             $auth = $setting->getAuthCredentials();
             switch (true) {

I would like to thank you again for your input and testing! These changes will be included in the next set of releases, so please stay tuned.

Cheers.

Shlok_Raut_2001

KevinTheJedi

Hi Kevin,

Is this issue fix in 1.18.1 ?

i am hosted OsTicket in Windows using Xampp

KevinTheJedi

Everyone,

Here is the official Pull Request for these changes:

https://github.com/osTicket/osTicket/pull/6618

If anything changes the pull request will be updated.

Cheers.

nor_rem

Where to change the setting in version 1.18

nor_rem

I changed the following lines and certificate verification was disabled
// Set the connection settings $this->connection = [ 'host' => $host, 'port' => $port, 'ssl' => $ssl, 'protocol' => strtoupper($account->getProtocol()), 'name' => self::get_hostname(), 'use_complete_quit' => false, 'novalidatecert' => true ]; oraz private function buildOptions(AccountSetting $setting) { // Dont send 'QUIT' on __destruct() $config = ['use_complete_quit' => false,'novalidatecert' => true]; $connect = $setting->getConnectionConfig(); $auth = $setting->getAuthCredentials();

asadler

Hello
This is my /includes/class.mail.php, where do I change this in osTicket version 1.18 for the emails to work, I am using Gmail

KevinTheJedi

asadler

Install the latest release of v1.18.1 from our website, install the latest build of the OAuth2 plugin from our website, install/enable the URL Rewrite module on your web server, follow the below guide to configure Gmail Modern Authentication (OAuth2):

https://docs.osticket.com/en/latest/OAuth2/Google%20Authorization%20Guide.html

Cheers.

asadler

KevinTheJedi This worked for me, Thanks so much!

asadler

KevinTheJedi Apparently after setting up the 0 Auth for Google, everything worked fine for a few days, (The Token Key Expires today, as per Screenshot) then the same error started happening again, also during ticket creation, It takes even 3-5 Minutes to submit a ticket, anything i should double check?

KevinTheJedi

asadler

Access Tokens expire quickly (same day) and when expires we use the Refresh Token to refresh and get a new Access Token.

What error are you talking about specifically?

If it takes that long on ticket creation it could be different things but it sounds like it’s taking awhile to send an email.

Cheers.

asadler

KevinTheJedi I am not yet familiar with the Refresh Tokens, how do I go about it and what steps can I take to get the refresh tokens? I realized that it takes a while to send an email.!

KevinTheJedi

asadler

The refresh token is already retrieved when you authorize the email. Then every time the access token is refreshed automatically the refresh token is updated as well.

Cheers.

asadler

KevinTheJedi Thanks for the feedback, however still the emails are not yet being received even when the tokens are updated! How do I proceed from There?

KevinTheJedi

asadler

Did you enable email fetching globally (Admin Panel > Emails > Settings > Email Fetching > Enabled) and setup a cron job?

https://docs.osticket.com/en/latest/Getting%20Started/POP3-IMAP%20Settings.html

Cheers.

asadler

KevinTheJedi Yes i do have email fetching enabled globally

asadler

When i do this, I run into the above error!

KevinTheJedi

asadler

Ahh network unreachable is the error. Seems like that host or port is blocked on your server. You need to contact your server admin and/or hosting provider to have them look into why you cannot connect to that host and port from your webserver.

Cheers.

ntozier

If you have a external web hosting company contact them like Kevin suggested.
If you are running your own server (in house or in the cloud) you would want to check logs for any security software you are running on the host.

Or if you have your own firewall it could also blocking.
If you do, check firewall logs to see why its getting blocked.

kkyritsis

Hello,

Unfortunately, we are facing the same issue with our osTicket installation (ubuntu VM):

We cannot connect to the on-premises exchange mail server 2019 (contains trusted, third-party signed SSL certificate) through osTicket:

because we get the exact same error:

which changes when I add the tls:// prefix to the mail server name:

I could not find anything related to the issue in the local log files (web server or php) and I have petitioned and waiting for the mail server logs.

Not sure how to proceed regarding the SSL certificate, any help is welcome.

KevinTheJedi

kkyritsis

Sounds like that port is blocked on your server/firewall or maybe your host doesn't allow external IMAP/POP3? If using Microsoft it's likely you are forced to use Modern Authentication.

Cheers.

« Previous Page Next Page »