You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We recently changed our Znuny install to use OAuth2 for fetching due to Microsoft disabling basic auth. for IMAP/POP. At the time we switched over to this, we also tried setting MultiSMTP's accounts to use OAuth2 Tokens. The problem was that MultiSMTP appeared to be trying to authenticate with the wrong token.
We were seeing the following for an auto-response:
As well as the following for a manually sent reply:
It appears that the token named on the NotificationSenderEmail's account was being used regardless of which SMTP mail account the email was being sent as. I'm not sure whether that token was being used because it was associated with the NotificationSenderEmail account or whether that was a coincidence.
I‘d like to push this up a little as we see the exact same behavior in our system with latest Znuny 6.5.x and the latest add-on version.
If from both SMTP servers mails are sent around the same time, often the wrong OAuth token is taken.
We recently changed our Znuny install to use OAuth2 for fetching due to Microsoft disabling basic auth. for IMAP/POP. At the time we switched over to this, we also tried setting MultiSMTP's accounts to use OAuth2 Tokens. The problem was that MultiSMTP appeared to be trying to authenticate with the wrong token.
We were seeing the following for an auto-response:


As well as the following for a manually sent reply:


It appears that the token named on the NotificationSenderEmail's account was being used regardless of which SMTP mail account the email was being sent as. I'm not sure whether that token was being used because it was associated with the NotificationSenderEmail account or whether that was a coincidence.
Install details:
Possibly relevant configuration
[email protected]
Kernel::System::Email::MultiSMTP
No
No
With SMTP accounts configured like this:



To be explicit, the email addresses and token names are examples and have been used in place of the real ones.
The text was updated successfully, but these errors were encountered: