https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38338
--- Comment #41 from Olivier Hubert <[email protected]> --- (In reply to David Cook from comment #37) > Jumping back to Perl... it looks like Email::Sender::Transport::SMTP and > Email::Sender::Transport::SMTP::Persistent connect to the SMTP server only > at the time they're sending the email... so you can't test the > authentication until sending time... > > If there is an auth error, we'd have to create a new transport and re-try > with the new transport... I'm not sure what you mean by having to recreate the transport, but I'm not the most familiar with the way Koha sends email. I thought that having the token created (and refreshed) separately would ensure that the token we have is always valid. Given that we should be reasonably sure that the token is good, why would a transport error necessitate the creation of a new transport? By the way, I was able to get a working version of a test script sending, but as mentioned on Mattermost, the configuration of the instance required that we use the URL https://login.microsoftonline.com/[TENANT_ID]/oauth2/v2.0/token along with the "https://outlook.office365.com/.default"; scope (instead of something like "https://outlook.office365.com/SMTP.Send";). I think the different configuration in Azure instances will increase the variability of scenarios. Certainly compared to using Gmail anyway. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
