View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0030280 | mantisbt | public | 2022-05-17 09:16 | 2022-06-09 07:02 | |
Reporter | mos379 | Assigned To | |||
Priority | normal | Severity | feature | Reproducibility | N/A |
Status | acknowledged | Resolution | open | ||
Summary | 0030280: Implement Google OAuth Authentication for PHPMailer to send notifications with Gmail | ||||
Description | Since Google more or less made simple SMTP unusable it would be great to add the OAuth mechanism to mantis.
EDIT (dregad): fix markdown | ||||
Tags | No tags attached. | ||||
I understand your problem with Google disabling simple password authentication for their SMTP server, but TBH I am reluctant to implement a specific solution for just a single e-mail provider (even if it's Google). Chances are that other providers will also require OAuth2 in the future, so what would be next for us ? Add similar hacks to email_send() and more composer dependencies for Yahoo, Hotmail, etc ? This would turn into a maintenance nightmare. Moreover, the provider-specific composer dependencies would have to be added globally (composer.json), causing overhead for everyone not using Gmail. Ideally, we need to have a more generic solution, that could work for other OAuth2 providers too. In any case, new configs need to be defined and fully documented in config_defaults_inc.php (and in the Admin Guide as well). And please follow our coding guidelines (particularly variable naming). |
|
@dregad Totally agree, I just wanted to share my work as I wanted to continue using mantis instead of switching to a different solution just because it doesn't support a small module. I was hoping that someone from the project would know how to "properly" integrate these items, as I'm not fluent with php and only maintained the changes locally as I saw that the PHPMailer was already used and there was a simple way to introduce the OAUTH mechanism... |
|
Yes, and for each one, an another dependency must be added to composer.json... And potentially some provider-specific code too.
Your contribution is appreciated, but as mentioned not usable in its current form. That being said, if I understand correctly, creating and maintaining a Google Published App may induce costs: As an alternative solution, did you try using an App Password instead ? |
|
I'm facing the same problem, I can't use gmail simple password authentication to send email. Any schedule for the long term solution? |
|