From: Christopher Faylor <cgf-use-the-mailinglist-please@gcc.gnu.org>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: Overseers mailing list <overseers@sourceware.org>,
overseers@gcc.gnu.org, "Maciej W. Rozycki" <macro@orcam.me.uk>
Subject: Re: Cannot subscribe to gcc.gnu.org mailing lists
Date: Wed, 20 Jan 2021 10:06:11 -0500 [thread overview]
Message-ID: <20210120150611.GA23993@cgf.cx> (raw)
In-Reply-To: <20210120140150.GB9217@redhat.com>
On Wed, Jan 20, 2021 at 09:01:50AM -0500, Frank Ch. Eigler wrote:
>> NB it looks like /var/mail/spam has overflown; perhaps use logrotate(8)
>> or suchlike on it?
>
>Yeah, manually aged that file and another one like it. 512MB of
>precious spam! Things should be working again. Please try it with
>one -subscribe destination at a time.
I empty that periodically, the last time on 1/15, and use it to feed
sa-learn.
prev parent reply other threads:[~2021-01-20 15:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 7:59 Maciej W. Rozycki
2021-01-20 14:01 ` Frank Ch. Eigler
2021-01-20 15:06 ` 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=20210120150611.GA23993@cgf.cx \
--to=cgf-use-the-mailinglist-please@gcc.gnu.org \
--cc=fche@redhat.com \
--cc=macro@orcam.me.uk \
--cc=overseers@gcc.gnu.org \
--cc=overseers@sourceware.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).