Hi Don, On Fri, Jun 21, 2024 at 05:13:44PM -0700, Don Armstrong wrote: > On Fri, 21 Jun 2024, Vincent Lefevre wrote: > > On 2024-06-20 20:28:16 -0700, Don Armstrong wrote: > > > On Thu, 20 Jun 2024, Vincent Lefevre wrote: > > > > Reopening since after more than 2 hours, I still haven't received the > > > > "Please confirm subscription" e-mail. > > > > > > Looks like you had some non-ascii characters which triggered a bug; can > > > you try again now? [Python 3 is much more strict than python 2, and I've > > > tried to be as minimal with the changes as possible, so we're probably > > > handling utf-8 incorrectly. Hopefully it isn't an issue.] > > > > I've tried again with > > > > Date: Fri, 21 Jun 2024 09:56:17 +0200 > > From: Vincent Lefevre <vinc...@vinc17.net> > > To: 1073053-subscr...@bugs.debian.org > > Subject: subscribe > > Message-ID: <20240621075617.ga6...@qaa.vinc17.org> > > MIME-Version: 1.0 > > Content-Type: text/plain; charset=iso-8859-1 > > > > and a non-ASCII character as usual, i.e. not UTF-8. > > Still the same problem. > > Hrm. Looing at this more closely, the version of EOC that we're using > doesn't handle encodings at all, and just happened to work correctly, > but modern python with bytes->string coercion is causing all sorts of > issues. > > I'll dig back into this and get a real solution implemented.
For me it neither work yet with subscribing to bugs. But I hope this counts not simply as "me too" reply. I noticed that in my case even if I just trigger a subscription mail with 'bts subscribe' command I do not get any subscrbtion request challenge reply. | From: car...@debian.org | To: 1071576-subscr...@bugs.debian.org | Subject: subscription request for bug #1071576 | Date: Tue, 25 Jun 2024 21:59:25 +0200 | User-Agent: devscripts bts/2.23.7 | Message-ID: <1719345565-2799-bts-car...@debian.org> | | thanks Does this gives any further insights in what goes wrong? Regards, Salvatore
