This is a multi-part message in MIME format.
------=_NextPart_000_00A5_01BDBE10.A219DCC0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Does the H-sig have a digest mode where all messages are held for
a day and then either forwarded, or posted in a data base so that
they can be retrieved on request? You would have a hard time
managing a selective retrieval, but, retrieving each day, at your
option, would seem to be feasible. Of course, "sending to all"
on a daily basis would probably be easiest to administer. Either
process would reduce what I call the "snow flakes" problem.
Bob Cooper
------=_NextPart_000_00A5_01BDBE10.A219DCC0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
<HTML>
<HEAD>
<META content=3Dtext/html;charset=3Diso-8859-1 =
http-equiv=3DContent-Type>
<META content=3D'"MSHTML 4.72.2106.6"' name=3DGENERATOR>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT color=3D#000000>Does the H-sig have a digest mode where all =
messages=20
are held for a day and then either forwarded, or posted in a data base =
so that=20
they can be retrieved on request? You would have a hard time managing a=20
selective retrieval, but, retrieving each day, at your option, would =
seem to be=20
feasible. Of course, "sending to all" on a daily basis =
would=20
probably be easiest to administer. Either process would reduce what I =
call the=20
"snow flakes" problem.</FONT></DIV>
<DIV><FONT color=3D#000000></FONT> </DIV>
<DIV>Bob Cooper</DIV>
<DIV> </DIV></BODY></HTML>
------=_NextPart_000_00A5_01BDBE10.A219DCC0--
