[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: BTS not archiving Bcc: mails? [was: Re: inconsistent mailgraph settings]G



On Mon, 23 Aug 2021, Holger Wansing wrote:



Am 23. August 2021 07:19:26 MESZ schrieb Tomas Pospisek <tpo2@sourcepole.ch>:

The thing is, if you close a bug report via `Bcc:
999999999999-close@bugs.debian.org` then the mail that arrives at the
BTS does *not* have the 999999999999-close@bugs.debian.org address in
the email header but only in the mail envelope - that is, when
connecting the sending MTA will tell the BTS MTA "RCPT TO:
999999999999-close@bugs.debian.org"
and that's it. This will close the bug, but the address
999999999999-close@bugs.debian.org will not be visible in the email
that's archived...

Funny, just some minutes before your mail I have filed
bug #992755 as a place to test and document this
behaviour.

It's indeed as you stated.

Thus, I will reopen and rename that bug accordingly.


When I toggle "show useless messages" I think I do see the closure. And
I see the one for 989734 too.


https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992755;msg=14
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989734;msg=14

(Pasted below in case those links don't work as I expect)

Tim.


MIME-Version: 1.0
X-Mailer: MIME-tools 5.509 (Entity 5.509)
X-Loop: owner@bugs.debian.org
From: "Debian Bug Tracking System" <owner@bugs.debian.org>
To: Holger Wansing <hwansing@mailbox.org>
Subject: Bug#992755 closed by Holger Wansing <hwansing@mailbox.org> (Re:
 Bug#992755: [BTS] Bcc'ed close mails not archived in bug log ?))
Message-ID:
<handler.992755.D992755.162969662730356.notifdone@bugs.debian.org>
References: <9F3CF53F-8C57-4CE5-B459-D7605C1C0656@mailbox.org>
 <D8FFE44D-F92A-434A-91B0-03DE77464945@mailbox.org>
X-Debian-PR-Message: they-closed 992755
X-Debian-PR-Package: bugs.debian.org
Reply-To: 992755@bugs.debian.org
Date: Mon, 23 Aug 2021 05:33:06 +0000
Content-Type: multipart/mixed; boundary="----------=_1629696786-30835-1"

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

This is an automatic notification regarding your Bug report
which was filed against the bugs.debian.org package:

#992755: [BTS] Bcc'ed close mails not archived in bug log ?

It has been closed by Holger Wansing <hwansing@mailbox.org>.

Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Holger Wansing
<hwansing@mailbox.org> by
replying to this email.


--
992755: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992755
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[Message part 2 (message/rfc822, inline)]

    From: Holger Wansing <hwansing@mailbox.org>
    To: 992755@bugs.debian.org
    Subject: Re: Bug#992755: [BTS] Bcc'ed close mails not archived in
bug log ?)
    Date: Mon, 23 Aug 2021 07:30:09 +0200

    This mail is also sent to
    992755-close@bugs.debian.org
    via Bcc !

    Let's see what happens...


================



MIME-Version: 1.0
X-Mailer: MIME-tools 5.509 (Entity 5.509)
X-Loop: owner@bugs.debian.org
From: "Debian Bug Tracking System" <owner@bugs.debian.org>
To: Vincent Lefevre <vincent@vinc17.net>
Subject: Bug#989734 closed by J??rg Frings-F??rst
 <debian@jff.email> (reply to debian@jff.email) (Re: mailgraph does not
 start on boot)
Message-ID:
<handler.989734.D989734.162946096613955.notifdone@bugs.debian.org>
References: <75bfd56d668f858a0df8c89c963d31e8036414c2.camel@jff.email>
 <20210611143438.GA12721@joooj.vinc17.net>
X-Debian-PR-Message: they-closed 989734
X-Debian-PR-Package: mailgraph
X-Debian-PR-Source: mailgraph
Reply-To: 989734@bugs.debian.org
Date: Fri, 20 Aug 2021 12:06:07 +0000
Content-Type: multipart/mixed; boundary="----------=_1629461167-15851-1"

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

This is an automatic notification regarding your Bug report
which was filed against the mailgraph package:

#989734: mailgraph does not start on boot

It has been closed by J??rg Frings-F??rst <debian@jff.email> (reply to
debian@jff.email).

Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact J??rg Frings-F??rst
<debian@jff.email> (reply to debian@jff.email) by
replying to this email.



Reply to: