Closed protich closed 1 year ago
@MarcBanyard - After some thinking - we've decided to revert your commit and focus instead on changing how IMAP/POP protocol handles OAuth2 authentication. This is a better approach because;
1) Removes Application logic from Plugin - we leave the Resource Owner as authorized 2) Makes it possible to use same Token for both fetching (imap/pop) and sending (smtp)
Thanks again,
@MarcBanyard - After some thinking - we've decided to revert your commit and focus instead on changing how IMAP/POP protocol handles OAuth2 authentication. This is a better approach because;
- Removes Application logic from Plugin - we leave the Resource Owner as authorized
- Makes it possible to use same Token for both fetching (imap/pop) and sending (smtp)
Thanks again,
No problems, I agree this is a much better way to do this as it simplifies the process for users.
This PR re-implements PR #261 to be inline with changes made upstream to support Strict Matching setting.