from localhost (localhost [127.0.0.1])
	by phobos.labs.netnoteinc.com (Postfix) with ESMTP id 550C044155
	for <jm@localhost>; Wed, 28 Aug 2002 10:50:03 -0400 (EDT)
from phobos [127.0.0.1]
	by localhost with IMAP (fetchmail-5.9.0)
	for jm@localhost (single-drop); Wed, 28 Aug 2002 15:50:03 +0100 (IST)
from listman.example.com (listman.example.com [66.187.233.211]) by
    dogma.slashnull.org (8.11.6/8.11.6) with ESMTP id g7SEmuZ29177 for
    <jm-exmh@jmason.org>; Wed, 28 Aug 2002 15:48:56 +0100
from listman.example.com (localhost.localdomain [127.0.0.1]) by
    listman.redhat.com (Postfix) with ESMTP id 80E063EEE6; Wed, 28 Aug 2002
    10:49:05 -0400 (EDT)
from int-mx1.corp.example.com (int-mx1.corp.example.com
    [172.16.52.254]) by listman.redhat.com (Postfix) with ESMTP id DD2FE40226
    for <exmh-workers@listman.redhat.com>; Wed, 28 Aug 2002 10:46:31 -0400
    (EDT)
(from mail@localhost) by int-mx1.corp.example.com (8.11.6/8.11.6)
    id g7SEkST30975 for exmh-workers@listman.redhat.com; Wed, 28 Aug 2002
    10:46:28 -0400
from mx1.example.com (mx1.example.com [172.16.48.31]) by
    int-mx1.corp.redhat.com (8.11.6/8.11.6) with SMTP id g7SEkSY30971 for
    <exmh-workers@redhat.com>; Wed, 28 Aug 2002 10:46:28 -0400
from ratree.psu.ac.th ([202.28.97.6]) by mx1.example.com
    (8.11.6/8.11.6) with SMTP id g7SEVFl08404 for <exmh-workers@redhat.com>;
    Wed, 28 Aug 2002 10:31:16 -0400
from munnari.OZ.AU (localhost [127.0.0.1]) by delta.cs.mu.OZ.AU
    (8.11.6/8.11.6) with ESMTP id g7SEiQW22630; Wed, 28 Aug 2002 21:44:26
    +0700 (ICT)
From exmh-workers-admin@redhat.com  Wed Aug 28 15:50:04 2002

| so I'll probably poke around at the sequences performance issues,
Well, there's this wonderful piece of code in MhSeqExpand ...
# Hack to weed out sequence numbers for messages that don't exist
if ![file exists $mhProfile(path)/$folder/$m] {
which is going to run slow if a sequence happens to start with a bunch
of messages that don't exist.   I'm not sure why it is important that the
first message in the sequence returned exists, but not necessarily any
of the others, but I'm sure glad it is, as MhSeqExpand gets called lots,
and I don't know if I could cope if it were checking every file in the
sequences it is looking at, all the time...
It may help to keep a list of the valid message numbers for the current
folder (though that would then need to be verified against changes to the
directory).   Does tcl have a directory read function?   I assume so...
Mh_Sequence also goes and rereads the files (.mh_sequences and the
context file) but I'm not sure how frequently that one is called.
| I'll email anything I figure out since I'm leaving town in less