[prev in list] [next in list] [prev in thread] [next in thread] 

List:       debian-devel
Subject:    Re: BTS not archiving Bcc: mails? [was: Re: inconsistent mailgraph settings]
From:       Tomas Pospisek <tpo2 () sourcepole ! ch>
Date:       2021-08-23 5:19:26
Message-ID: bcd725bc-9b66-6ada-d31a-dfe4cd5ed92f () sourcepole ! ch
[Download RAW message or body]

On 23.08.21 02:21, Vincent Lefevre wrote:
> On 2021-08-22 23:32:15 +0500, Andrey Rahmatullin wrote:
>> On Sun, Aug 22, 2021 at 08:25:41PM +0200, Tomas Pospisek wrote:
>>> Wouldn't the Bcc'ed email that arrived to the BTS be visible in the bug's
>>> log/archive (on the bug's page (https://bugs.debian.org/989734))?
>> It's visible: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989734;msg=27
> 
> Where? I don't see any "close" or "done".
> 
> Note that the "Done:" in the metadata at the top just reflects the
> *current* status of the bug; it is currently also present at
> 
>    https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989734;msg=5
> 
> where the bug was obviously open.

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...

Not sure why people are using `Bcc: 999999999999-close@bugs.debian.org` 
in the first place. To hide that 999999999999-close@bugs.debian.org 
address from spammers? But then all the other addresses are visible...?
:-/
*t

[prev in list] [next in list] [prev in thread] [next in thread]