All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Domsch <Matt_Domsch@dell.com>
To: Tim Moore <linux-kernel@nsr500.net>
Cc: linux-kernel@vger.kernel.org,
	linux-kernel-digest-admin@lists.us.dell.com
Subject: Re: list digest / non-digest delivery problems?
Date: Wed, 30 Jun 2004 13:45:01 -0500	[thread overview]
Message-ID: <20040630184501.GB17774@lists.us.dell.com> (raw)
In-Reply-To: <40E304E2.4060807@nsr500.net>

On Wed, Jun 30, 2004 at 11:22:26AM -0700, Tim Moore wrote:
> Hi;
> 
> After LK switched to digest-only some time back

meaning you're subscribed to linux-kernel-digest or
linux-kernel-daily-digest at lists.us.dell.com, so this clearly isn't
an issue with vger.kernel.org, right?

> 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.

Hmmm.  Nothing has changed on lists.us.dell.com regarding these lists in
quite a while.  Can you provide an example message that you believe is
incorrect?

The linux-kernel-digest list sends one digest every 100KB, which I
think is also near the vger single message size limit.  Any chance
what came through was a single message, yet still wrapped in a digest?

 
> 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.

They'll have the normal mailman list headers on every message, can't
you use those?


> 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.

This is the first I've heard of any problems with the digester in a
long time.  Please provide an example message as requested above, and
I'll look into it.

Thanks,
Matt

-- 
Matt Domsch
Sr. Software Engineer, Lead Engineer
Dell Linux Solutions linux.dell.com & www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com

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

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

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=20040630184501.GB17774@lists.us.dell.com \
    --to=matt_domsch@dell.com \
    --cc=linux-kernel-digest-admin@lists.us.dell.com \
    --cc=linux-kernel@nsr500.net \
    --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.