From: Joseph Myers <joseph@codesourcery.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: Martin Sebor <msebor@gmail.com>,
Eric Gallager <egall@gwmail.gwu.edu>,
GCC Mailing List <gcc@gcc.gnu.org>
Subject: Re: Bugzilla timing out
Date: Fri, 26 Jan 2018 22:15:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1801262213170.16084@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20180126220404.GB25056@redhat.com>
On Fri, 26 Jan 2018, Frank Ch. Eigler wrote:
> Hi -
>
> > Thanks for looking into it. I'm still (or again) seeing very
> > poor responsiveness. Right now, bringing up an existing bug
> > takes an entire minute.
>
> There has been quite a burst in activity on sourceware.org over the
> last few hours. Will look further into why, but quite a bit of it may
> be anti-spam processing.
Many copies of a 5 MB message have apparently been timing out in
sourceware's spam processing, resulting in sourceware repeatedly accepting
the message while the sender's mail server also times out (sooner) and
keeps resending it.
https://sourceware.org/ml/libc-alpha/2018-01/msg00901.html
(the list archives uniquify based on message-id, but many separate copies
have been delivered to libc-alpha so far each with its own ezmlm sequence
number).
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2018-01-26 22:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-15 20:54 Martin Sebor
2018-01-15 20:58 ` Joseph Myers
2018-01-15 22:29 ` H.J. Lu
2018-01-18 19:11 ` Frank Ch. Eigler
2018-01-21 6:20 ` Eric Gallager
2018-01-22 18:09 ` Frank Ch. Eigler
2018-01-23 10:26 ` Richard Biener
2018-01-23 13:19 ` Frank Ch. Eigler
2018-01-26 21:52 ` Martin Sebor
2018-01-26 21:55 ` H.J. Lu
2018-01-26 22:04 ` Frank Ch. Eigler
2018-01-26 22:15 ` Joseph Myers [this message]
2018-01-26 23:08 ` Frank Ch. Eigler
2018-01-26 23:29 ` Martin Sebor
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=alpine.DEB.2.20.1801262213170.16084@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=egall@gwmail.gwu.edu \
--cc=fche@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=msebor@gmail.com \
/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).