https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77319
Andrew Pinski changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77319
Frank Ch. Eigler changed:
What|Removed |Added
CC||fche at redhat dot com
--- Comment #4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77319
Frédéric Buclin changed:
What|Removed |Added
CC||overseers at gcc dot gnu.org
--- Comme
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77319
--- Comment #2 from joseph at codesourcery dot com ---
Maybe CC overseers, ask for the mail settings to be restored to what they
were (sending mail in a way that bypasses spamassassin and restoring the
Bugzilla addresses to the global-allow lis
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77319
--- Comment #1 from Frédéric Buclin ---
Is this behavior new? Because the Bugzilla code and configuration didn't change
since Aug 17.
I suspect that the anti-spam filters on the mail server are the culprit. fche
said they could take several tens
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77319
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
