Re: [PATCH v6 1/1] send-email: retrieve Message-ID from outlook SMTP server

From: Erik Huelsmann <ehuels@gmail.com>
Date: Apr 25, 2025, 19:05 UTC
Message-ID: <CACOoB6hh_jWqC3pxiVVAkKN9+mPVUeUodKqFRmMe_Da65a6Bdw@mail.gmail.com>
In-Reply-To: <xmqqtt6ctbim.fsf@gitster.g>

On Fri, Apr 25, 2025 at 7:08 PM Junio C Hamano <gitster@pobox.com> wrote:

Show 10 quoted lines

> >> Authen::SASL now finally supports XOAUTH2 and OAUTHBEARER thanks to Erik
> >> and Julian! (Link: https://github.com/gbarr/perl-authen-sasl/commit/958a3aa165d30cf4e3cbb36dc45306de627aa13f)
> >
> > And it's official: https://metacpan.org/release/EHUELS/Authen-SASL-2.1800
>
> Wonderful.
>
> We tend to, however, try to cater to those whose distros are slow to
> adjust to upstream changes.  What's the ETA for the updated module
> to major distros?

To be honest, I have *no* idea. I think Debian is stabilizing Trixie now, so maybe it's in the one that will be after that (in 2 years?).

You could however decide to support XOAUTH2 and OAUTHBEARER only when they are available? Then you don't need to increase the minimum library requirement: there's no API difference between 2.1700 (the current version until today) and 2.1800 (the newly released version). So if you were to probe existence of Authen::SASL::Perl::XOAUTH2 and/or Authen::SASL::Perl::OAUTHBEARER, you could conditionally disable the feature if the probe fails. (Using "eval { require Authen::SASL::Perl::XOAUTH2; 1 }" should do what you need: return false if the probe fails; true if it succeeds.)

-- 
Bye,

Erik.

http://efficito.com -- Hosted accounting and ERP.
Robust and Flexible. No vendor lock-in.