> I apologize for the delay in response, but I can certainly help you move
> forward with this.
> Rather than muck with an already creaky and hack-laden Mailman instance,
> I'd prefer to do this on the MTA side -- I can create a router to
> conditionally reroute traffic for bug-gnu-emacs elsewhere -- I just need
> to know the envelope and client parameters.
I hoped Don or Stephen would know what to tell you, because I don't.
The quoted thread already says what I know:
1 - Mail that is sent to [EMAIL PROTECTED] should be redirected to
[EMAIL PROTECTED] (and not distributed to the
recipients of the [EMAIL PROTECTED] mailing-list).
2 - Mail coming from the [EMAIL PROTECTED] to
[EMAIL PROTECTED] should be distributed to the recipients of the
[EMAIL PROTECTED] list.
I don't know what envelope parameters you need to know, nor what "client"
you have in mind. If you want to know the "envelope-from" parameter for
email coming from the [EMAIL PROTECTED] mailing-list, it
seems to be "[EMAIL PROTECTED]".
Stefan
>> [EMAIL PROTECTED] - Sat Mar 29 15:57:34 2008]:
>>
>> Hi,
>>
>> We're trying to use a Debbugs to manage bug reports for the
>> Emacs project. For various reason, it is necessary to reuse the
>> [EMAIL PROTECTED] email address for bug submission as well as the
>> bug-gnu-emacs mailing-list for distribution of the discussions about
>> bugs, so we need to insert the Debbugs in between the
>> [EMAIL PROTECTED] address and the bug-gnu-emacs Mailman list.
>>
>> Stephen J. Turnbull says that a clean way to do it is to add a special
>> Mailman Handler for the bug-gnu-emacs list which would redirect to
>> Debbugs all the email that is not coming from Debbugs. Can you help
>> us
>> out here?
>>
>>
>> > Stefan
>>
>>
>> >>>>> "Sylvain" == Sylvain Beucler <[EMAIL PROTECTED]> writes:
>>
>> > On Sat, Mar 22, 2008 at 09:01:48AM +0900, Stephen J. Turnbull wrote:
>> >> > >>>>> "Sylvain" == Sylvain Beucler <[EMAIL PROTECTED]> writes:
>> >> > > On Wed, Mar 19, 2008 at 09:55:11PM -0400, Stefan Monnier wrote:
>> >>
>> >> > >> >> All email sent to [EMAIL PROTECTED] should not go to
>> Mailman,
>> >> > >> >> but instead it should be forwarded to
>> >> > >> >> [EMAIL PROTECTED]
>> >> > >> >>
>> >> > >> >> Then all mail currently sent from Emacsbugs to the
>> >> > >> >> [EMAIL PROTECTED] mailing list should be
>> distributed to
>> >> > >> >> the members of the bug-gnu-emacs mailing list.
>> >>
>> >> > >> > Well, there's no magic. The only working
>> >> > >> > "[EMAIL PROTECTED]" adress is "bug-gnu-
>> [EMAIL PROTECTED]",
>> >> > >> > so if you want to make that one point to somewhere else, we
>> need to
>> >> > >> > rename the Mailman mailing list.
>> >>
>> >> I don't think this is true. AFAIK Mailman knows nothing and cares
>> >> less about the envelope recipient.
>> >>
>> >> So you should currently have an alias (sendmail-style, and I'm
>> kinda
>> >> guessing here, depends on Mailman version and suchlike)
>> >>
>> >> bug-gnu-emacs: "|/var/lib/mailman/bin/mailman post
>> >> bug-gnu-emacs"
>> >>
>> >> Change that to
>> >>
>> >> bug-gnu-emacs: [EMAIL PROTECTED]
>> >> bug-gnu-emacs-really: "|/var/lib/mailman/bin/mailman post bug-gnu-
>> emacs"
>> >>
>> >> Obviously you need the right configuration of the debbugs program
>> at
>> >> emacsbugs.donarmstrong.com, pointing back to "bug-gnu-emacs-
>> really".
>> >> Season nomenclature to taste (-recipients made line-length 82
>> columns ;-).
>> >>
>> >> Note that you now have three addresses where spam can get into the
>> >> pipeline. I don't know how these "internal" addresses leak out,
>> but
>> >> they sometimes do. So you may wish to restrict the envelope sender
>> to
>> >> bug-gnu-emacs-really to be "emacsbugs". You probably also want to
>> >> ensure that traffic to "submit" always goes via the "bug-gnu-emacs"
>> >> alias, or you need to make "[EMAIL PROTECTED]" be
>> an
>> >> alias of bug-gnu-emacs in the Mailman interface.
>>
>> > Hi,
>>
>> > We don't have root access to the lists.gnu.org computer, so this
>> kind
>> > of thing is outside our reach. Please contact [EMAIL PROTECTED] to
>> see
>> > if they can do something.
>>
>> > Consider that lists.gnu.org hosts thousands of lists - this is
>> > mass-hosting. There isn't a series of hand-made aliases, but a set
>> of
>> > custom Exim rules that deliver all @gnu.org and @nongnu.org to
>> Mailman
>> > or other places (such as fencepost) dependending on various factors.
>>
>> > --
>> > Sylvain
>>
>>
>>
> --
> Joshua Ginsberg <[EMAIL PROTECTED]>
> Free Software Foundation - Senior Systems Administrator
