httpd-apreq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stas Bekman <>
Subject Re: cvs lists commit messages
Date Wed, 14 Jul 2004 20:31:45 GMT
Noel J. Bergman wrote:
> Stas Bekman wrote:
>>Again and again we hit this -cvs lists problems. On unmoderated lists
>>legitimate commit mails don't get posted if the committer is not
>>subscribed from their address.
> Why are there unmoderated lists?  

I don't know. I haven't set up that list. Joe?

> This is the problem, IMO.  And with SA in
> place, the excuse of high spam volume should be gone.  Change the list
> setting so that it is moderated, and the problem goes away.  If the spam
> volume is still high, we can address that with SA changes.  Doesn't that
> make sense?

I guess so. Indeed at the moment the amount of spam has been 
significantly reduced. So I can't really complain.

But we still have a problem with every new committer subscribed from a 
different address. May be the procedures of adding a committer should be 
changed to automatically add a new committer to a project foo to the 
allow list of the foo-* lists?

> I get particularly annoyed when, as root, we send e-mail to a PMC in
> response to their request and it gets bounced because we aren't subscribed
> to their PMC.

Right. And moderation doesn't always help here, since sometimes noone 
approves the email and it just sits there in the queue until it gets 
expired and you still have the same effect. That's exactly where my 
suggestion solves this problem as well as others. Allow any emails 
coming from to be delivered, w/o requiring any moderation. 
(not based on From: but the physical IP check or whichever way it is done).

>>automatically allow all posts originating form the machine
>>sending cvs commit mail and automatically block any other
> You raised this question before, and Ask told you that there is no
> configuration setting for doing such a thing.  Managing this by per-list
> hacking of the editor files by hand would be a major PITA, but patches to
> code or scripts are welcomed.  But the easiest thing to do now would be to
> turn moderation back on.
> See attached, since I don't know who still had a copy of the earlier
> discussion.

Yes I know, but I remember that someone has mentioned that there may be 
a better global solution can be found. Hence I've pinged again.

> ------------------------------------------------------------------------
> Subject:
> Re: [Fwd: MODERATE for]
> From:
> Ask Bjorn Hansen <>
> Date:
> Mon, 14 Jun 2004 02:30:33 -0400
> To:
> "Noel J. Bergman" <>
> To:
> "Noel J. Bergman" <>
> CC:
> <>, "Stas Bekman" <>, <>
> On Sun, 6 Jun 2004 11:25:36 -0400, Noel J. Bergman <> wrote:
>>>>Is it possible to arrange for lists and
>>>> to silently discard any emails but the ones
>>>>coming from, w/o any moderation. Both lists have a single
>>>>purpose of showing the commit logs, nothing is ever discussed there.
>>>>Both lists CC the corresponding -dev lists where any follow ups are
>>>>posted to.
>>>It's relatively trivial to do, the only caveat is that the lists will
>>>get a slightly non-standard configuration which might be lost if
>>>someone is editing options without beware of the special config.
>>>apmail, do we have similar exceptions for other lists?
>>Ask, how would you suggest doing this, and is this something that could be
>>done in qpsmtpd?  By convention, nothing should be sent to -[cvs|scm|svn]*
>>addresses except from our tools.
> I'm not quite sure what our policy on mocking with the dot-qmail files
> ezmlm creates is, but one way to do it would be adding something like
> |perl -e 'exit 0 if $ENV{SENDER}=~/apache\.org$/i; print "Sorry, you
> are not allowed to post to this list\n"; exit 100;'
> early in the DIR/editor file.
> If the restriction should be to subscribers instead, then something like
> |ezmlm-issubn 'DIR' 'DIR/digest' 'DIR/allow' || { echo "Sorry, you are
> not allowed to post to this list."; exit 100; }
> should do the trick.
>  - ask

Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker     mod_perl Guide --->

View raw message