From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
To: owner@bugs.debian.org, Overseers mailing list <overseers@sourceware.org>
Subject: Re: looping gcc/bugzilla <-> bugs.debian mail
Date: Wed, 18 Mar 2020 17:21:37 -0400 [thread overview]
Message-ID: <20200318212137.GA14365@cgf.cx> (raw)
In-Reply-To: <20200318200607.2hbqiktyah4kl2t4@qor.donarmstrong.com>
On Wed, Mar 18, 2020 at 01:06:07PM -0700, Don Armstrong 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.
Please forgive my ignorance, but what should the X-Loop header look
like? Would this be something that you added and we stripped or
something that we didn't add?
We recently changed hardware and updated to a newer linux distro for
sourceware.org and there are still some software issues to work out.
So, if we need to change something here we'll be glad to do so.
>I'll drop in a rule to block your bugzilla setup to sending messages to
>bugs.debian.org to mitigate this in the future.
We have a rule to prevent the loop too but if we're missing something
here we'd like to fix it.
next prev parent reply other threads:[~2020-03-18 21:21 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 [this message]
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
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=20200318212137.GA14365@cgf.cx \
--to=cgf-use-the-mailinglist-please@sourceware.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).