Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.dist > #1198170 > unrolled thread

Bug#1071576: bugs.debian.org: bug subscription no longer possible: no "Please confirm subscription" e-mail

Back to article view | Back to linux.debian.bugs.dist

Contents

  Bug#1071576: bugs.debian.org: bug subscription no longer possible: no "Please confirm subscription" e-mail Vincent Lefevre <vincent@vinc17.net> - 2024-05-21 15:10 +0200
    Bug#1071576: bugs.debian.org: bug subscription no longer possible: no "Please confirm subscription" e-mail Vincent Lefevre <vincent@vinc17.net> - 2024-05-21 15:20 +0200
    Bug#1071576: bugs.debian.org: bug subscription no longer possible: no "Please confirm subscription" e-mail Vincent Lefevre <vincent@vinc17.net> - 2024-05-22 01:10 +0200
      Bug#1071576: bugs.debian.org: bug subscription no longer possible: no "Please confirm subscription" e-mail Don Armstrong <don@debian.org> - 2024-05-22 06:10 +0200
        Bug#1071576: bugs.debian.org: bug subscription no longer possible: no "Please confirm subscription" e-mail Don Armstrong <don@debian.org> - 2024-05-23 06:00 +0200
          Bug#1071576: bugs.debian.org: bug subscription no longer possible: no "Please confirm subscription" e-mail Salvatore Bonaccorso <carnil@debian.org> - 2024-05-28 06:50 +0200
            Bug#1071576: bugs.debian.org: bug subscription no longer possible: no "Please confirm subscription" e-mail Don Armstrong <don@debian.org> - 2024-05-29 06:10 +0200

#1198170 — Bug#1071576: bugs.debian.org: bug subscription no longer possible: no "Please confirm subscription" e-mail

Package: bugs.debian.org
Severity: important

It is no longer possible to subscribe to bugs as
"Please confirm subscription" e-mail messages are no longer sent.

On 2024-05-10, this was working, but since 2024-05-20 at least,
this is no longer working. I had sent:

From: Vincent Lefevre <vincent@vinc17.net>
To: 1071372-subscribe@bugs.debian.org
Subject: subscribe
Date: Mon, 20 May 2024 00:56:07 +0200
Message-ID: <20240519225607.GE2665@qaa.vinc17.org>

The issue remains with attempts today (2024-05-21) at 14:26:56 +0200
and 14:47:15 +0200 for another bug.

-- 
Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

[toc] | [next] | [standalone]

#1198172

On 2024-05-21 15:04:44 +0200, Vincent Lefevre wrote:
> It is no longer possible to subscribe to bugs as
> "Please confirm subscription" e-mail messages are no longer sent.
> 
> On 2024-05-10, this was working, but since 2024-05-20 at least,
> this is no longer working. I had sent:
> 
> From: Vincent Lefevre <vincent@vinc17.net>
> To: 1071372-subscribe@bugs.debian.org
> Subject: subscribe
> Date: Mon, 20 May 2024 00:56:07 +0200
> Message-ID: <20240519225607.GE2665@qaa.vinc17.org>
> 
> The issue remains with attempts today (2024-05-21) at 14:26:56 +0200
> and 14:47:15 +0200 for another bug.

Actually, after a look at the logs on my mail server, this was still
working at the following date:

2024-05-11T11:57:13.575225+02:00 joooj postfix/smtp[74387]: AB7C1812: to=<1070891-subscribe@bugs.debian.org>, relay=buxtehude.debian.org[2607:f8f0:614:1::1274:39]:25, delay=3.9, delays=0.04/0.11/2.8/0.89, dsn=2.0.0, status=sent (250 OK id=1s5jTe-00BPwE-Lt)

with a reply ("Please confirm subscription" e-mail):

2024-05-11T12:00:14.976146+02:00 joooj postfix/qmgr[70857]: E359C13E: from=<1070891-ignore@bugs.debian.org>, size=4289, nrcpt=1 (queue active)

But this was no longer working at the following date:

2024-05-17T15:51:22.974407+02:00 joooj postfix/smtp[164605]: 8556DACB: to=<1071274-subscribe@bugs.debian.org>, relay=buxtehude.debian.org[209.87.16.39]:25, delay=4.4, delays=0.03/0.04/3.4/0.94, dsn=2.0.0, status=sent (250 OK id=1s7xzY-00CaPs-2o)

(I did not get the reply).

-- 
Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

[toc] | [prev] | [next] | [standalone]

#1198213

On 2024-05-21 14:45:02 -0400, David Mandelberg wrote:
> I'm having the same problem. Could it be related to #1071469 which also
> involves mail issues around the same time?

At https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071469
Louis-Philippe Véronneau says

"It seems that a debian.org mail infrastructure breakage happened 
sometime between 2024-05-17 and 2024-05-18"

and

"I dug a little bit more and it seems the outage happened between
2024-05-17 ~2200 and and 2024-05-18 0110UTC."

But since the outage ended on 2024-05-18 (and the issue with bug
subscription seemed to have started before the outage), this seems
to be a different problem... unless someone did a series of changes
in the mail config on 2024-05-17 and early 2024-05-18.

-- 
Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

[toc] | [prev] | [next] | [standalone]

#1198216

On Wed, 22 May 2024, Vincent Lefevre wrote:
> On 2024-05-21 14:45:02 -0400, David Mandelberg wrote:
> > I'm having the same problem. Could it be related to #1071469 which also
> > involves mail issues around the same time?
> 
> At https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071469
> Louis-Philippe Véronneau says
> 
> "It seems that a debian.org mail infrastructure breakage happened 
> sometime between 2024-05-17 and 2024-05-18"
> 
> and
> 
> "I dug a little bit more and it seems the outage happened between
> 2024-05-17 ~2200 and and 2024-05-18 0110UTC."
> 
> But since the outage ended on 2024-05-18 (and the issue with bug
> subscription seemed to have started before the outage), this seems
> to be a different problem... unless someone did a series of changes
> in the mail config on 2024-05-17 and early 2024-05-18.

Thanks for the reports; I note that around this time the systems were
upgraded. It's possible that this finally broke bug mail, which was
using a totally unsupported out of date version of EOC.

Not sure what the right path forward is to fix that without totally
re-implementing bug mailing lists (which probably needs to happen
anyway).

-- 
Don Armstrong                      https://www.donarmstrong.com

He quite enjoyed the time by himself in the mornings. The day was too
early to have started going really wrong.
  -- Terry Pratchet _Only You Can Save Mankind_ p133

[toc] | [prev] | [next] | [standalone]

#1198305

On Tue, 21 May 2024, Don Armstrong wrote:
> Thanks for the reports; I note that around this time the systems were
> upgraded. It's possible that this finally broke bug mail, which was
> using a totally unsupported out of date version of EOC.

Looking at it, this is definitely a casualty of python2->python3. I'm
working with Liw to get the most-recent version of EoC (2010!) and I'll
do the tweaks to make it work on python3.

Look for me to have it working again this weekend.

-- 
Don Armstrong                      https://www.donarmstrong.com

Science is a way of trying not to fool yourself. The first principle
is that you must not fool yourself, and you are the easiest person to
fool.
 -- Richard Feynman "What is and What Should be the Role of Scientific
    Culture in Modern Society"; 1964

[toc] | [prev] | [next] | [standalone]

#1198968

Hi Don,

On Wed, May 22, 2024 at 08:48:38PM -0700, Don Armstrong wrote:
> On Tue, 21 May 2024, Don Armstrong wrote:
> > Thanks for the reports; I note that around this time the systems were
> > upgraded. It's possible that this finally broke bug mail, which was
> > using a totally unsupported out of date version of EOC.
> 
> Looking at it, this is definitely a casualty of python2->python3. I'm
> working with Liw to get the most-recent version of EoC (2010!) and I'll
> do the tweaks to make it work on python3.
> 
> Look for me to have it working again this weekend.

Not the most urgent bit, but a question: Once the issue is fixed, will
the replies for subscription requests to bug be send out for those
falling inbetween the broken phase?

(For context, I have some bugs for which I have issued a subscription
request and would like to monitor the updates there, and wonder if
once fixed need to re-issue those so I can really subscribe to the
bugs).

Regards,
Salvatore

[toc] | [prev] | [next] | [standalone]

#1199103

On Tue, 28 May 2024, Salvatore Bonaccorso wrote:
> Not the most urgent bit, but a question: Once the issue is fixed, will
> the replies for subscription requests to bug be send out for those
> falling inbetween the broken phase?

I suspect you'll have to re-issue them, but I'm not certain.

Just an update, I've gotten the last version from Lars (from 2010!), and
I'm working on finishing up testing it.

Once I've done that, I'll need to port in the patch that makes the
buglists work (automated list creation and some other pieces).

I hope to having it working again sometime this week (but my Debian time
is limited to small 30 minute bits each day, so no real promises).


-- 
Don Armstrong                      https://www.donarmstrong.com

Where I sleep at night, is this important compared to what I read
during the day? What do you think defines me? Where I slept or what I
did all day?
 -- Thomas Van Orden of Van Orden v. Perry

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.bugs.dist

csiph-web