Hi again,
Another thing we may want to mention is that list maintainers
(including [EMAIL PROTECTED]) get one Mailman "request for approval"
per incoming mail - something that users would usually rather get in
daily batches.
I have a procmail rule to remove all these "request for approval" from
m
Hi,
On Fri, Jan 18, 2008 at 06:26:04PM -0600, Karl Berry wrote:
> I'm talking about listhelper here, not about the volunteer human
> review. Aren't the two separate things?
>
> Yes.
>
> But the same three volunteers (as it happens -- it wouldn't necessarily
> have to be this way and ther
I believe listhelper forwards mail to a spamassassin daemon that can
remove part of the pending mails from the queue.
True.
I also believe there are a few volunteers who are willing to approve
non-removed mailing lists posts, when there's no list maintainer or
when maintainers
(As a sidenote, I think it would help not to trim the reply context to
single lines, because usually both you and I forget what it was all
about after 2 posts, and this leads to confusions)
On Fri, Jan 18, 2008 at 05:48:13PM -0600, Karl Berry wrote:
> > - You mentioned "Out of the many hundreds o
What was that person's motivation?
They did not trust in our human review of the messages.
if possible with instructions on how to set it up at other places.
We can describe how we set it up for ourselves, at least. I doubt it is
possible to make something like this generically instal
A problem with distributing listhelper code is one of preparing it for
generic distribution such that it would work in a generic environment.
As Sylvain says, that's not necessary. Let's just upload the code we
are, in fact, using. I think we should do that for the sake of
transparency a
On Fri, Jan 18, 2008 at 03:16:59PM -0700, Bob Proulx wrote:
> Sylvain Beucler wrote:
> > - We at Savannah represent a strong stand against services that keep
> > their source code private (such as SourceForge, of course). Hence,
> > we need a permanent location where the listhelper source code
Sylvain Beucler wrote:
> - We at Savannah represent a strong stand against services that keep
> their source code private (such as SourceForge, of course). Hence,
> we need a permanent location where the listhelper source code can be
> downloaded, if possible with instructions on how to set i
Hi,
I have 2 comments:
- You mentioned "Out of the many hundreds of lists we've added
[listhelper] to, exactly one person has decided not to use it."
What was that person's motivation?
- We at Savannah represent a strong stand against services that keep
their source code private (such as S
FYI ...
The dotgnu people wanted to start using some of the mailing lists they
have had on lists.gnu.org. They sent me additional subscriptions for
dotgnu-announce dotgnu-general dotgnu-libjit dotgnu-pnet-commits dotgnu-pnet
(existing subscriptions are unaffected.)
They also sent me mbox files f
10 matches
Mail list logo
