Adding crap to
the Subject header is for [...]
...or for people who [...] are accustomed to seeing
it for EVERY
OTHER LIST AROUND,
This may be true of your mail feed, but it is an artifact of the set of
lists you are subscribed to. Some 73% of the lists I've had traffic
from in the last week don't do it, including the
high-volume ones -
something like 95% percent of my list traffic by message count.
(That's assuming all the lists I'm on generate a List-Id: header, which
to a pretty good approximation is true.)
and just plain LIKE it.
If this is admitted as a reason (and I see no reason it shouldn't be),
we kinda have to counterbalance it by the people who just plain DISLIKE
it. Such as, me and at least one other person who's spoken up.
In any case, it's all moot except to the extent that Jay cares what we
think, and as far as I can recall he hasn't weighed in this time
around, so I see no reason to think it's likely to change.
You wrote that procmail is difficult for you to use. So I'll make this
offer: if you want, I'll configure my own system to (a) make the
Subject: header change and (b) remail the result to you. It'd mean
your cctalk mail stream will be behind my filtering, and may get
delayed if/when my mailsystem is being slow or is off the air - if the
list will let me, I can subscribe a separate address which has the
filtering bits that are easy to turn off turned off, which will reduce
that but not eliminate it. And it means that unsubs and option changes
and the like might need to go through me, which would delay them if I'm
incommunicado for any reason.
But the resulting mail _will_ have the Subject: marker.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTML mouse at
rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B