From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
To: Overseers mailing list <overseers@sourceware.org>
Cc: owner@bugs.debian.org, Don Armstrong <don@debian.org>
Subject: Re: looping gcc/bugzilla <-> bugs.debian mail
Date: Wed, 18 Mar 2020 23:28:16 -0400 [thread overview]
Message-ID: <20200319032816.GA15153@cgf.cx> (raw)
In-Reply-To: <alpine.DEB.2.21.2003182236030.10208@digraph.polyomino.org.uk>
On Wed, Mar 18, 2020 at 10:37:10PM +0000, Joseph Myers wrote:
>On Wed, 18 Mar 2020, Don Armstrong via Overseers wrote:
>>On Tue, 17 Mar 2020, Frank Ch. Eigler wrote:
>>>We have a mail loop situation happening between bugs.debian.org and
>>>sourceware.org (= gcc.gnu.org)'s bugzilla servers. Can you advise
>>>whether we should stop this somehow or whether you can from your end?
>>
>>Your bugzilla setup is stripping off all of the X-Loop and other
>>relevant headers when it forwards mail it receives, so it's made it
>>very difficult to automatically mitigate this kind of mail loop.
>
>I'm not sure if Bugzilla has any connection between the incoming and
>outgoing emails. It may just generate a comment from an incoming
>email, and generate an outgoing email from a new comment independent of
>how that comment was added.
That was my understanding too but maybe we could just automatically add
an X-Loop for the email address from the comment if that helped.
cgf
prev parent reply other threads:[~2020-03-19 3:28 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
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 [this message]
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=20200319032816.GA15153@cgf.cx \
--to=cgf-use-the-mailinglist-please@sourceware.org \
--cc=don@debian.org \
--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).