GNU bug report logs - #78366
30.1; auth-source-xoauth2-plugin conflicts with multiple Google accounts

Previous Next

Full log

View this message in rfc822 format

From: Xiyue Deng <manphiz <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>, Robert Pluim <rpluim <at> gmail.com>
Cc: j <at> gnu.org, 78366 <at> debbugs.gnu.org
Subject: bug#78366: 30.1; auth-source-xoauth2-plugin conflicts with multiple Google accounts
Date: Tue, 27 May 2025 10:08:54 -0700

[Message part 1 (text/plain, inline)]

Eli Zaretskii <eliz <at> gnu.org> writes:

>> From: Robert Pluim <rpluim <at> gmail.com>
>> Cc: Eli Zaretskii <eliz <at> gnu.org>,  78366 <at> debbugs.gnu.org,  j <at> gnu.org
>> Date: Tue, 27 May 2025 12:32:22 +0200
>> 
>> >>>>> On Mon, 26 May 2025 21:11:00 -0700, Xiyue Deng <manphiz <at> gmail.com> said:
>> 
>>     Xiyue> Thanks for applying!  As this can also be considered a regression in
>>     Xiyue> smtpmail.el, do you think it's OK to install to 30-branch as well?
>> 
>> For it to be a regression there has to be a version in which it worked
>> previously, which I donʼt think is the case.
>
> Right.
>

Ack.  Should have called it a bug-fix.

>> But as a bugfix I can see that applying it to emacs-30 makes sense,
>> and I think itʼs low-risk. Eli?
>
> Are we absolutely sure the status we correct should never-ever be
> reported as itself?  If we are sure, feel free to backport the fix to
> the emacs-30 branch.
>

I think in the case of smtpmail-try-auth-method, it never handles a
status that requires further input, so status like 334 (where < 400 is
considered a success) is essentially a failure; plus cram-md5 is already
doing something similar.  Hope this helps to confirm that this bug-fix
is low-risk.

> Thanks.

-- 
Regards,
Xiyue Deng

[signature.asc (application/pgp-signature, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.