From: Christopher Faylor <cgf@redhat.com>
To: Kevin Buettner <kevinb@cygnus.com>
Cc: gdb@sources.redhat.com
Subject: Re: ADMINISTRIVIA: size limit for gdb* mailing list messages?
Date: Mon, 23 Jul 2001 11:30:00 -0000 [thread overview]
Message-ID: <20010723143043.A888@redhat.com> (raw)
In-Reply-To: <1010723182420.ZM18333@ocotillo.lan>
On Mon, Jul 23, 2001 at 11:24:20AM -0700, Kevin Buettner wrote:
>On Jul 23, 1:17pm, Christopher Faylor wrote:
>
>> Given the recent spate of viruses showing up here, I'd like to limit the
>> sizes of messages to the gdb mailing lists.
>>
>> Any thoughts on limitations to the size of messages to the gdb mailing
>> lists?
>>
>> gcc has a 400K limit. I think that is a little high for a non-patches
>> mailing list.
>>
>> How about 150K for gdb and 400K for gdb-patches and gdb-prs?
>
>I think 400k for gdb-patches is too low.
>
>Here are some other ideas on how to combat the problem:
>
> 1) Hold messages above a certain size for moderator approval.
>
> 2) Only allow large messages from mailing list subscribers.
I'm not soliciting ideas. I get tons of those every time there is
an increase in spam or a flurry of email viruses. I have scores
of interesting ideas for dealing with spam myself. Most of it would
require tuit time that is not available.
I'm not going to be redesigning the sources.redhat.com mailing list
software. Instead, I've asked for feedback for what we can do. We can
limit mime types and message sizes. AFAIK, that is the current limit on
what is possible with our ezmlm mailing list software.
cgf
next prev parent reply other threads:[~2001-07-23 11:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-23 10:17 Christopher Faylor
2001-07-23 11:24 ` Kevin Buettner
2001-07-23 11:30 ` Christopher Faylor [this message]
2001-07-24 3:32 ` Eli Zaretskii
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=20010723143043.A888@redhat.com \
--to=cgf@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=kevinb@cygnus.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