On 04-11 20:32, Michael Elkins wrote: > On Sat, Apr 10, 2010 at 01:38:19AM +0200, ilf wrote: >> I would like a workaround to use Regex in 'lists' and 'subscribe', but >> that feels dirty. Why doesn't Mutt allow 'lists'/'subscribe' to lists >> based on the List-Id: header? > The List-ID header is not necessarily a valid email address. All > that the RFC requires is that it be a unique value for each list. As > such, it's not terribly useful for figuring out where to reply.
I never proposed using List-Id to figure out where to reply, List-Post
is the right field for that and it's being done nicely.
But I think Mutt could display messages as from a list (in index with %L
and %Z) automatically, if a List-Id header is present. Then I would not
need lists/subscribe at all.
> The problem with not using the subscribe command in Mutt is the very
> common case where your address appears on the To or CC line in
> addition to the mailing list address. In this sitation you will
> receive two copies of the email: one directly from the message
> sender, and another from the mailing list software.
That's a user error in my view and not something Mutt should care about.
People should use <list-reply> instead of <reply-all>.
On 04-11 20:22, Michael Elkins wrote:
> The reason for the distinction between lists/subscribe is that just
> because you received an email that was addressed to a list doesn't
> mean that you are subscribed to said list.
But if there's a List-Id header, I am subscribed.
--
ilf @jabber.berlin.ccc.de
Über 80 Millionen Deutsche benutzen keine Konsole. Klick dich nicht weg!
-- Eine Initiative des Bundesamtes für Tastaturbenutzung
signature.asc
Description: Digital signature
