All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tim Moore <linux-kernel@nsr500.net>
To: linux-kernel@vger.kernel.org
Cc: linux-kernel-digest-admin@lists.us.dell.com
Subject: list digest / non-digest delivery problems?
Date: Wed, 30 Jun 2004 11:22:26 -0700	[thread overview]
Message-ID: <40E304E2.4060807@nsr500.net> (raw)

Hi;

After LK switched to digest-only some time back I wrote an awk digest 
expander since I manage the list volume by filtering on key words in the 
subject field.  Recently some messages with headers indicating a digest are 
actually coming through as individuals which really tarts things up.

While the digest expander is my problem, keying on reliable email headers 
it is significantly easier than coding logic to tell if the message is a 
real digest or an individual message.  It would be very helpful to let the 
group know if there is a problem with digests and if the headers will 
accurately reflect the message content.

Thanks,
Tim.
-- 
  | for direct reply, prepend "private_" to address

             reply	other threads:[~2004-06-30 18:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-30 18:22 Tim Moore [this message]
2004-06-30 18:45 ` list digest / non-digest delivery problems? Matt Domsch

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=40E304E2.4060807@nsr500.net \
    --to=linux-kernel@nsr500.net \
    --cc=linux-kernel-digest-admin@lists.us.dell.com \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.