On Tue, Jan 09, 2024 at 03:46:41PM +, Edd Barrett wrote:
> On Tue, Jan 09, 2024 at 03:26:48PM +, Klemens Nanni wrote:
> > README can always be read in advance, is easy to maintain and, imho, one
> > of the first places to look at if you run into ports/package problems.
> >
> > This just
On Tue, Jan 09, 2024 at 03:46:41PM +, Edd Barrett wrote:
> In that case, here is the first patch I wrote :)
OK kn
On Tue, Jan 09, 2024 at 03:26:48PM +, Klemens Nanni wrote:
> README can always be read in advance, is easy to maintain and, imho, one
> of the first places to look at if you run into ports/package problems.
>
> This just makes more sense to me.
In that case, here is the first patch I wrote
On Tue, Jan 09, 2024 at 03:10:13PM +, Edd Barrett wrote:
> On Tue, Jan 09, 2024 at 03:04:39PM +, Klemens Nanni wrote:
> > Does XOAUTH2 appear in the list of available mechanisms once you install
> > that package?
>
> I assume so. The error goes away once the package is installed.
>
> >
On Tue, Jan 09, 2024 at 03:04:39PM +, Klemens Nanni wrote:
> Does XOAUTH2 appear in the list of available mechanisms once you install
> that package?
I assume so. The error goes away once the package is installed.
> Either way, you can also hint at that package in DESCR or README in case
>
On Tue, Jan 09, 2024 at 02:48:11PM +, Edd Barrett wrote:
> Hi,
>
> On a couple of occasions now I've wasted time deciphering this error message
> from `mbsync`:
>
> ```
> IMAP error: selected SASL mechanism(s) not available;
>selected: XOAUTH2
>available: SCRAM-SHA-512 SCRAM-SHA-384
Hi,
On a couple of occasions now I've wasted time deciphering this error message
from `mbsync`:
```
IMAP error: selected SASL mechanism(s) not available;
selected: XOAUTH2
available: SCRAM-SHA-512 SCRAM-SHA-384 SCRAM-SHA-256 SCRAM-SHA-224
SCRAM-SHA-1 DIGEST-MD5 EXTERNAL OTP CRAM-MD5 NTLM
