Date: Wed, 26 Jun 2013 19:58:10 -0400
From: Dubiousjim <dubiousjim@gmail.com>
To: alpine-devel@lists.alpinelinux.org
Subject: [alpine-devel] Mailing list weirdness
Message-ID: <20130626235810.GC18572@zen>
Mail-Followup-To: alpine-devel@lists.alpinelinux.org
Precedence: list
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.21 (2010-09-15)

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
---