From: Jason Molenda <jason-swarelist@molenda.com>
To: Jim Kingdon <kingdon@redhat.com>
Cc: rosalia@lanl.gov, overseers@sourceware.cygnus.com
Subject: Re: disallowing too-long messages
Date: Sat, 30 Dec 2000 06:08:00 -0000 [thread overview]
Message-ID: <20000520113305.B18351@shell17.ba.best.com> (raw)
In-Reply-To: <200005201726.NAA04957@devserv.devel.redhat.com>
On Sat, May 20, 2000 at 01:26:43PM -0400, Jim Kingdon wrote:
> Most lists probably have a 5 meg limit, as described at
> http://sourceware.cygnus.com/sourceware/procedures/new-list.txt
Actually, I rarely imposed any limits on the lists I set up unless
specfically asked to. The note about msgsize is there more as a
reminder for when list admins request it.
I think the only lists that use limits comprehensively are the gcc
lists, which IIRC, restrict posts to ~100k.
In any event, someone with 'alias' access (which really means root
access) has to make changes to a list like this.
J
WARNING: multiple messages have this Message-ID
From: Jason Molenda <jason-swarelist@molenda.com>
To: Jim Kingdon <kingdon@redhat.com>
Cc: rosalia@lanl.gov, overseers@sourceware.cygnus.com
Subject: Re: disallowing too-long messages
Date: Sat, 20 May 2000 11:33:00 -0000 [thread overview]
Message-ID: <20000520113305.B18351@shell17.ba.best.com> (raw)
Message-ID: <20000520113300.xTHVtq0gQ8eWvQbm45VG5ajQg9QbIzUG_QgSr6sMyXw@z> (raw)
In-Reply-To: <200005201726.NAA04957@devserv.devel.redhat.com>
On Sat, May 20, 2000 at 01:26:43PM -0400, Jim Kingdon wrote:
> Most lists probably have a 5 meg limit, as described at
> http://sourceware.cygnus.com/sourceware/procedures/new-list.txt
Actually, I rarely imposed any limits on the lists I set up unless
specfically asked to. The note about msgsize is there more as a
reminder for when list admins request it.
I think the only lists that use limits comprehensively are the gcc
lists, which IIRC, restrict posts to ~100k.
In any event, someone with 'alias' access (which really means root
access) has to make changes to a list like this.
J
next prev parent reply other threads:[~2000-12-30 6:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-30 6:08 Mark Galassi
2000-05-19 21:06 ` Mark Galassi
2000-12-30 6:08 ` Jim Kingdon
2000-05-20 10:26 ` Jim Kingdon
2000-12-30 6:08 ` Jason Molenda [this message]
2000-05-20 11:33 ` Jason Molenda
2000-12-30 6:08 ` Jeffrey A Law
2000-05-22 10:32 ` Jeffrey A Law
2000-12-30 6:08 ` Mark Galassi
2000-05-22 10:38 ` Mark Galassi
2000-12-30 6:08 ` Jeffrey A Law
2000-05-22 10:50 ` Jeffrey A Law
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=20000520113305.B18351@shell17.ba.best.com \
--to=jason-swarelist@molenda.com \
--cc=kingdon@redhat.com \
--cc=overseers@sourceware.cygnus.com \
--cc=rosalia@lanl.gov \
/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).