X-Original-To: alpine-devel@lists.alpinelinux.org Delivered-To: alpine-devel@mail.alpinelinux.org Received: from jeremythomerson.com (mail.jeremythomerson.com [74.117.189.150]) by mail.alpinelinux.org (Postfix) with ESMTP id 8F673DC008C for ; Thu, 27 Jun 2013 02:42:40 +0000 (UTC) Received: from mail-ve0-f171.google.com (mail-ve0-f171.google.com [209.85.128.171]) by jeremythomerson.com (Postfix) with ESMTP id 72A1E1CE5B for ; Wed, 26 Jun 2013 23:16:43 -0500 (CDT) Received: by mail-ve0-f171.google.com with SMTP id b10so179830vea.16 for ; Wed, 26 Jun 2013 19:42:39 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:from:date:message-id :subject:to:content-type; bh=EnjNF+FmVzMDrMIaPaPfTuepFlRWiRwhilGYMHC9XVg=; b=PcE9kPhpOXGAuqt7mkoopMxj9JTqVROt2GgUD+arCFOR0uBQ5QzCTzIh4gS4+rgpUe CsN/6lbZYgnhX9WUNMDbvFKqD9JcXQZsc0Gxdbp8RT5Crc8jeW7C6jd/ps5NSruVBlyA 98YpkIHWl59TI1nQ1x3fOI5nImO3cGbA2hnGW75AXtAA2VwysvfpABQXN6/A2fdfa+4C zExCEywKMhSvR8ubwCNzha7JwG5vmDYraLCqxhHgXwAShXdyJAxgB0yx9RzGvh6GttBZ cuJsA0Hv2/duWjDPRKTh5QKYSW2r4L0/kOIR0Saq1CLF0eGEoVGzt3OCAIXVuIfz7UP5 bLrw== X-Received: by 10.58.255.229 with SMTP id at5mr2735673ved.44.1372300959370; Wed, 26 Jun 2013 19:42:39 -0700 (PDT) X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-Version: 1.0 Reply-To: jeremy@thomersonfamily.com Received: by 10.58.143.12 with HTTP; Wed, 26 Jun 2013 19:42:19 -0700 (PDT) In-Reply-To: <20130626235810.GC18572@zen> References: <20130626235810.GC18572@zen> From: Jeremy Thomerson Date: Wed, 26 Jun 2013 22:42:19 -0400 Message-ID: Subject: Re: [alpine-devel] Mailing list weirdness To: Alpine-devel Content-Type: multipart/alternative; boundary=047d7bea39503559c404e019b70e --047d7bea39503559c404e019b70e Content-Type: text/plain; charset=ISO-8859-1 Probably too obvious to mention (but it's bit me before): What MTA is your git-send-email using? Is it possible that it sends to your domain only but isn't configured as a relay? I've had that where I could send patches to myself (i.e. non-relay) but not a list (i.e. relay). Jeremy Thomerson On Wed, Jun 26, 2013 at 7:58 PM, Dubiousjim wrote: > I'm trying to send some patches to the list using git-send-email, but > they don't seem to be coming through. If I change the To: address to > myself, they come through fine. > > Perhaps the list is just unusually sluggish, though if this email comes > through and the patches don't that will be some evidence against that > diagnosis. > > Some lists block emails that aren't from list subscribers. I tried to > anticipate that, but no joy. More on this in a moment. Anyway, if this > email comes through, it will be evidence that this list is not > configured that way. And indeed, I see that I've had two messages go > through to the list in the past that weren't from my subscribed address. > > All my patches are authored by dubiousjim@gmail.com. > > This email's envelope sender is vaio@jimpryor.net, and its From: header > is dubiousjim@gmail.com. Neither of those is the address I subscribed to > the list with; I subscribed with a mangled address > lists+alpine-devel@jimpryor.net because that makes it easy to implement > a global system for filtering mail from mailing lists. (As opposed to > keeping track of which identifier headers are present this week for umpteen > different lists.) > > It's easy enough to configure git to set the envelope sender of the > patches it sends to the subscribed address. It's also possible to > configure git to set the From: to the subscribed address, but this > doesn't work so well. In the current version of git, if I do that, the > right From: field gets put in the header block. But an old "From: > dubiousjim@gmail.com" header (originally created by git-format-patch, > because that's the author address on the commits) gets left as the first > line of the email bodies. If you supply the --compose switch to > git-send-email, then that spurious header is omitted; but I don't want > to have to open and close a text editor for every patch I'm sending. > Perhaps this is a bug with the current version of git-send-email? > > Anyway, the upshot is that, given the mismatch between the address on my > commits and the address I'm subscribed to the list with, it's easiest if > the list accepts emails without verifying the sender is subscribed. It's > second-easiest if the list will accept emails so long as the envelope > sender OR the From: header is a subscribed address. At the moment, it's > more awkward if the list demands that the From: header be a subscribed > address. > > Of course, if this email gets through but my (several) attempts to send > the patches don't, I'm currently at a loss to explain why... > > -- > Dubiousjim > dubiousjim@gmail.com > > > --- > Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org > Help: alpine-devel+help@lists.alpinelinux.org > --- > > --047d7bea39503559c404e019b70e Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Probably too obvious to mention (but it's bit me befor= e): What MTA is your git-send-email using? =A0Is it possible that it sends = to your domain only but isn't configured as a relay? =A0I've had th= at where I could send patches to myself (i.e. non-relay) but not a list (i.= e. relay).

Jeremy Thomerson

<= br>
On Wed, Jun 26, 2013 at 7:58 PM, Dubiousjim <= span dir=3D"ltr"><dubiousjim@gmail.com> wrote:
I'm trying to send some patches to the l= ist using git-send-email, but
they don't seem to be coming through. If I change the To: address to myself, they come through fine.

Perhaps the list is just unusually sluggish, though if this email comes
through and the patches don't that will be some evidence against that diagnosis.

Some lists block emails that aren't from list subscribers. I tried to anticipate that, but no joy. More on this in a moment. Anyway, if this
email comes through, it will be evidence that this list is not
configured that way. And indeed, I see that I've had two messages go through to the list in the past that weren't from my subscribed address= .

All my patches are authored by dubi= ousjim@gmail.com.

This email's envelope sender is va= io@jimpryor.net, and its From: header
is dubiousjim@gmail.com. Neithe= r of those is the address I subscribed to
the list with; I subscribed with a mangled address
lists+alpine-devel@jim= pryor.net because that makes it easy to implement
a global system for filtering mail from mailing lists. (As opposed to
keeping track of which identifier headers are present this week for umpteen=
different lists.)

It's easy enough to configure git to set the envelope sender of the
patches it sends to the subscribed address. It's also possible to
configure git to set the From: to the subscribed address, but this
doesn't work so well. In the current version of git, if I do that, the<= br> right From: field gets put in the header block. But an old "From:
dubiousjim@gmail.com" head= er (originally created by git-format-patch,
because that's the author address on the commits) gets left as the firs= t
line of the email bodies. If you supply the --compose switch to
git-send-email, then that spurious header is omitted; but I don't want<= br> to have to open and close a text editor for every patch I'm sending. Perhaps this is a bug with the current version of git-send-email?

Anyway, the upshot is that, given the mismatch between the address on my commits and the address I'm subscribed to the list with, it's easie= st if
the list accepts emails without verifying the sender is subscribed. It'= s
second-easiest if the list will accept emails so long as the envelope
sender OR the From: header is a subscribed address. At the moment, it's=
more awkward if the list demands that the From: header be a subscribed
address.

Of course, if this email gets through but my (several) attempts to send
the patches don't, I'm currently at a loss to explain why...

--
Dubiousjim
dubiousjim@gmail.com


---
Unsubscribe: =A0alpine-devel+unsubscribe@lists.alpinelinux.org
Help: =A0 =A0 =A0 =A0 alpine-devel+help@lists.alpinelinux.org
---


--047d7bea39503559c404e019b70e-- --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---