Gnus development mailing list
 help / color / mirror / Atom feed
From: Zlatko Calusic <zlatko.calusic@iskon.hr>
Cc: ding@gnus.org
Subject: Re: Please, we need a header back, soon!
Date: Thu, 09 Nov 2006 16:56:10 +0100	[thread overview]
Message-ID: <8764domx5x.fsf@magla.zg.iskon.hr> (raw)
In-Reply-To: <ufaslgsd3qq.fsf@epithumia.math.uh.edu> (Jason L. Tibbitts, III's message of "09 Nov 2006 09:44:13 -0600")

Jason L Tibbitts III <tibbs@math.uh.edu> writes:

>>>>>> "ZC" == Zlatko Calusic <zlatko.calusic@iskon.hr> writes:
>
> ZC> This list has recently lost all headers which we could use to
> ZC> split it properly.
>
> All of that effort to complain, and yet no effort to complain to the
> proper place?  You should always contact the list owner about such
> things.

True, I'm guilty as charged. ;)

Somehow, I always presume that list owner must be on the list, but of
course it's not always true. Not even common these days.

> And, of course, depending on something nonstandard like
> Sender: isn't really the best thing.  In the past I always used the
> Envelope sender for that purpose, but there's still no guarantee that
> won't change.  (Messages from this list should appear with variable
> envelope senders, but you can still pattern match.)
>
> Fortunately there's a standard header for these things.  I have added
> a List-ID: header for you to filter on.  (Sorry if a couple of
> messages went out with the header showing "lists.math.uh.edu" instead
> of "gnus.org".)
>

While I don't see that header yet (for example in your message), of
course it's everything I asked for. There's nothing special in Sender:
header. Actually, you can use whatever header you want, it's just my
opinion that one such header MUST exist. Otherwise it's hard and error
prone to split mailing lists. I don't like spliting emails on headers
that are not primarily for that purpose (To, From, Received,
Subject...). It's asking for trouble.

For example, my split rules are full of different headers for
different mailing lists, I don't care, all of them work well, it's
just that ding list lost the last such header without warning and
mails started mixing with private/business mail. Thankfully this list
is not high traffic, so it wasn't such a big problem, but when that
happens to high volume lists like linux-kernel and you're on a 2 day
vacation... you know what happens. ;)

Example headers from my nnmail-split-fancy:

x-beenthere (mailman lists)
x-mailing-list
sender

Thank you!
-- 
Zlatko



  reply	other threads:[~2006-11-09 15:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-08 15:10 Zlatko Calusic
2006-11-08 15:30 ` Nedko Arnaudov
2006-11-08 22:33   ` Katsumi Yamaoka
2006-11-09  7:18     ` Steinar Bang
2006-11-08 16:27 ` Reiner Steib
2006-11-09 15:44 ` Jason L Tibbitts III
2006-11-09 15:56   ` Zlatko Calusic [this message]
2006-11-09 16:00     ` Zlatko Calusic
2006-11-09 16:02     ` Jason L Tibbitts III
2006-11-09 16:10       ` Zlatko Calusic
2006-11-09 16:33         ` John A. Martin
2006-11-21  9:31   ` Didier Verna
2006-11-21 15:13     ` Jason L Tibbitts III

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8764domx5x.fsf@magla.zg.iskon.hr \
    --to=zlatko.calusic@iskon.hr \
    --cc=ding@gnus.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).