Fatal error: Uncaught. Is it the form or the 365 server?

[fabydesign]

Hello I have the following errors in trying to send form to Office 365.
I do not have access to MIcrosoft setting, the IT guy does. Before asking I need to know where the errors are coming from. Either a bad customization of the form/scripts (my bad) or the wrong info or bad setup from him (Office 365).
As follow:
Fatal error: Uncaught PHPMailer\PHPMailer\Exception: SMTP Error: Could not connect to SMTP host. Failed to connect to server in /home/xxxxx/public_html/quform/vendor/phpmailer/phpmailer/src/PHPMailer.php:2405
Stack trace:
#0 /home/xxxxx/public_html/quform/vendor/phpmailer/phpmailer/src/PHPMailer.php(2175): PHPMailer\PHPMailer\PHPMailer->smtpConnect()
#1 /home/xxxxx/public_html/quform/vendor/phpmailer/phpmailer/src/PHPMailer.php(1798): PHPMailer\PHPMailer\PHPMailer->smtpSend()
#2 /home/xxxxx/public_html/quform/vendor/phpmailer/phpmailer/src/PHPMailer.php(1615): PHPMailer\PHPMailer\PHPMailer->postSend()
#3 /home/xxxxx/public_html/quform/process-file-uploads-FR.php(427): PHPMailer\PHPMailer\PHPMailer->send()
#4 /home/xxxxx/public_html/quform/process-file-uploads-FR.php(479): process()
#5 {main}
thrown in /home/xxxxx/public_html/quform/vendor/phpmailer/phpmailer/src/PHPMailer.php on line 2405
Thank you.

[Ally]

You don't have permission to view this content. Please log in or register and then verify your purchases to gain access.

[fabydesign]

Hello Ally,
Just got back from talking to the host.
The server does not support OAuth 2.0 for SMTP authentication. OAuth 2.0 is handled on the Microsoft 365 side.
He said, use Microsoft 365’s own SMTP relay or API-based sending (Graph API), not the server’s SMTP service.
Remember that only the IT guy has access to 365.
What can I do on my end, if any?
What customization is possible with your script, if even possible.
Thank you very much.

[Ally]

You don't have permission to view this content. Please log in or register and then verify your purchases to gain access.

[fabydesign]

Hello,
Back again at it.
I will get the info needed (client ID, Token etc.) today from the IT guy. I noticed there is a script hidden far in the vendor folder: get_oath_token.php.
Same I see in PHPMailer doc on GitHub. That means it can actually send through OAUTH2 connection, contrary of what you wrote earlier…Please explain?
Now how do I set it up (probably easy), and attach it to my form (process-file-uploads.php) using your scripts? There is no real indication for a non developer person in your docs.
Since OAUTH2 is the way to go in the very near future, I believe you have or are working on an updated scripts.
Thank you for the help. I am probably not the only one wondering how to make it work.

[Ally]

You don't have permission to view this content. Please log in or register and then verify your purchases to gain access.

[fabydesign]

Hello and thank you again for the answer above.
I have updated the forms (French and English) but I am missing the “refresh token”.
I asked the IT guy for it and his answer was : it is MY job to create it?!?
Lost again….
If I was to ask for a real support where you take care of it, I guess you know what I need by now, how would I do and how much will it cost me?
What will you need?
I have wasted way to much time and the client is getting upset.
Thank you.

[Ally]

You don't have permission to view this content. Please log in or register and then verify your purchases to gain access.

[fabydesign]

Hello again,
I had to install Composer first.
But now when I try to update the files in phpmailer using Composer (composer require greew/oauth2-azure-provider), I get all sort of errors and updated file:
Composer could not detect the root package (phpmailer/phpmailer) version, defaulting to ‘1.0.0’. See https://getcomposer.org/root-version
./composer.json has been updated
Composer could not detect the root package (phpmailer/phpmailer) version, defaulting to ‘1.0.0’. See https://getcomposer.org/root-version
Running composer update greew/oauth2-azure-provider
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.
Problem 1
– phpmailer/phpmailer is present at version 1.0.0+no-version-set and cannot be modified by Composer
– Root composer.json requires roave/security-advisories dev-latest -> satisfiable by roave/security-advisories[dev-latest].
– roave/security-advisories dev-latest conflicts with phpmailer/phpmailer <6.5.

You can also try re-running composer require with an explicit version constraint, e.g. “composer require greew/oauth2-azure-provider:*” to figure out if any version is installable, or “composer require greew/oauth2-azure-provider:^2.1” if you know which you need.

Installation failed, reverting ./composer.json to its original content.

It simply fails

Any idea?

Thank you.

[Ally]

You don't have permission to view this content. Please log in or register and then verify your purchases to gain access.

[fabydesign]

Hello again,
I have done all that was required but now I get a 500 error from the server when I try the get_oauth_token.php script on line.
It just does not work.
A bit out of hope now….
Thanks,
Fabrice

Attachments:

You must be logged in to view attached files.

[Author]

Posts