Re: looping gcc/bugzilla <-> bugs.debian mail

[Don Armstrong <don@debian.org>]

On Wed, 18 Mar 2020, Christopher Faylor wrote:
> 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?

X-Loop: owner@bugs.debian.org is what we add to all of our outgoing
messages to try to track mail loops.

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

We're probably partly to blame, because we haven't changed our setup to
account for RFC 3834, which I'll file a bug to add eventually.

-- 
Don Armstrong                      https://www.donarmstrong.com

You could say to the Universe this is not /fair/. And the Universe
would say: Oh it isn't? Sorry.
 -- Terry Pratchett _Soul Music_ p357