Great Circle Associates List-Managers
(October 1995)
 

Indexed By Date: [Previous] [Next] Indexed By Thread: [Previous] [Next]

Subject: Re: Date problems
From: Al Gilman <asgilman @ access . digex . net>
Date: Tue, 24 Oct 1995 16:58:08 -0400 (EDT)
To: info-labview-request @ pica . army . mil (Info-LabVIEW List Maintainer)
Cc: list-managers @ GreatCircle . COM
In-reply-to: <9510241348.aa17377@fsm-1.pica.army.mil> from "Info-LabVIEW List Maintainer" at Oct 24, 95 01:48:48 pm

Tom,

What would be the problem of sending received-undated messages
forward with a date as of when you handled them.  This is not the
true date of origination, of course.  You could even invent an
X-date-repaired-at: header comparable to the "Damaged in
transport" wrappers the snail mail postal service applies.
Notification that you had to repair the post could go back to
the originator, too.

Plan B: If you are willing to handle these manually, you can kick
undated messages into your "special handling" inbox from which
you can send them on as dated material.  The volume is probably
low enough.

Plan C: Tell the users who bounce undated items to subscribe to
the digest.

Keith,

Has any thought been given to sending _forward_ repaired messages
by the Notary working group?

Al Gilman
asgilman@access.digex.net	http://access.digex.net/~asgilman


References:
  • Date problems
    From: Info-LabVIEW List Maintainer <info-labview-request@pica.army.mil>
Indexed By Date Previous: Re: Date problems
From: Info-LabVIEW List Maintainer <info-labview-request@Pica.Army.Mil>
Next: Re: Mailinglist spamming countermeasures
From: Elizabeth Thomsen <et@clsn1102.noble.mass.edu>
Indexed By Thread Previous: Re: Date problems
From: Christopher Davis <ckd@loiosh.kei.com>
Next: Re: Date problems
From: Malcolm Ray <malcolmr@westminster.ac.uk>

Google
 
Search Internet Search www.greatcircle.com