From: "Frank Ch. Eigler" <fche@elastic.org>
To: owner@bugs.debian.org, Overseers mailing list <overseers@sourceware.org>
Cc: "Frank Ch. Eigler" <fche@redhat.com>, Don Armstrong <don@debian.org>
Subject: Re: looping gcc/bugzilla <-> bugs.debian mail
Date: Sun, 22 Mar 2020 16:40:50 -0400 [thread overview]
Message-ID: <20200322204050.GB8709@elastic.org> (raw)
In-Reply-To: <20200322203829.y4tivs2zl63t43ir@qor.donarmstrong.com>
Hi -
> X-Loop: owner@bugs.debian.org is what we add to all of our outgoing
> messages to try to track mail loops.
OK.
> > Would this be something that you added and we stripped or something
> > that we didn't add?
>
> Something that we add, but Bugzilla strips out. The general problem is
> that incoming messages are connected to outgoing messages without
> maintaining the e-mail headers from the incoming message. [You really
> should keep all of the References, X-Loop, and Received headers at a
> minimum.]
Thing is bugzilla is not forwarding emails. Bugzilla appends as a
comment the body of the message. Then it sends out a new notification
email to all the various subscribers of that bug, which includes the
originator. And the originator was the pseudo-userid over
@bugs.debian. So it wasn't a direct mail loop.
- FChE
next prev parent reply other threads:[~2020-03-22 20:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-17 13:33 Frank Ch. Eigler
2020-03-18 20:06 ` Don Armstrong
2020-03-18 21:21 ` Christopher Faylor
2020-03-22 20:38 ` Don Armstrong
2020-03-22 20:40 ` Frank Ch. Eigler [this message]
2020-03-22 21:50 ` Don Armstrong
2020-03-22 21:53 ` Frank Ch. Eigler
2020-03-18 22:37 ` Joseph Myers
2020-03-19 3:28 ` Christopher Faylor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200322204050.GB8709@elastic.org \
--to=fche@elastic.org \
--cc=don@debian.org \
--cc=fche@redhat.com \
--cc=overseers@sourceware.org \
--cc=owner@bugs.debian.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).