[502] in Tooltime

home help back first fref pref prev next nref lref last post

Re: Confirmation of Email received

daemon@ATHENA.MIT.EDU (Steven Wade Neiterman)
Thu Nov 13 12:29:01 1997

In-Reply-To: <v03020900ff03d8cf8cef@[18.81.0.146]>
Date: Thu, 13 Nov 1997 12:33:00 -0500
To: Barbara Goguen <goguen@MIT.EDU>, Debi Fuchs <debi@MIT.EDU>
From: Steven Wade Neiterman <wade@MIT.EDU>
Cc: tooltime@MIT.EDU

When we talked about this on Monday, I was hoping we could just replace an
existing text file with a new one.

The insertion of mailing listname, log number makes this more difficult.
While we could write a program to look for patterns (e.g. [mailing list
name] and perform substitution, this probably can not be done by tomorrow.
Or, we could hardcode the entire message, but, this has drawbacks.

So, is it possible to write a generic text file?

..Steve

At 9:30 AM -0500 11/13/97, Barbara Goguen wrote:
>My only concern with the proposed text below are those clients whose logs
>come over as open logs from FileMaker and who then get into some continued
>email correspondence with us.  If they knew a log number prior, they will
>now get a different log number and it may be confusing to them if they do
>not know anything about our new tool implementation.
>
>Even if we open with a line such as "Welcome to the new automated email
>interface to our call tracking database."
>
>At 12:09 PM -0500 11/12/97, Debi Fuchs wrote:
>>Hi Babs and Steve,
>>
>>On Monday I looked at the questions submitted via email on Sunday  Although
>>there were a total of 3 threads among the 6 questions submitted, 6 new logs
>>were created.  I think it is very important that we have a mechanism to
>>notify all recipients of the original message that a log has been created
>>in our database and that one should reply to database response message, not
>>directly to the original message.
>>
>>Barbara is planning to compose that message.  Barbara, I know you're busy
>>this week, so I'll take a crack and you can either modify mine, or make up
>>a different message yourself.  How about the following:
>>================================================================
>>  To: [original sender]
>>  Cc: [everyone the original message went to (except the mailing list
>>itself)]
>>  Reply-To:  [mailing list from which the log was generated]
>>  Subject: Log XXXXXXX: blah blah blah blah blah (where the "blahs" are
>>                         the original subject)
>>
>>
>>  The following email, sent to [mailing list name]@mit.edu, was assigned Log
>>  ID XXXXXX in our database.  Please include the text "Log XXXXXX" in the
>>subject
>>  line of any subsequent email regarding this topic, and be sure to include
>>  [mailing list name]@mit.edu in the "To" or "CC" field. In this way, all
>>information
>>  regarding this topic may be tracked in our database.
>>
>>  Alternately, you may simply choose to reply to THIS message, rather than
>>  the original.
>>
>>  Sincerely,
>>  The MIT Support Process
>>
>>
>>  -----------
>>  [Include original email here].
>>================================================================
>>
>>
>>For confirmation of additional messages which are associated with an
>>EXISTING LOG, how about the following:
>>================================================================
>>  To: [original sender ONLY]
>>  Reply-To:  [mailing list from which the log was generated]
>>  Subject: Log XXXXXXX: blah blah blah blah blah (where the "blahs" are
>>                         the original subject)
>>
>>
>>  The following email, sent to [mailing list name]@mit.edu, was added to Log
>>  ID XXXXXX in our database.  Please be sure to include the text "Log
>>XXXXXX" in
>>  the subject line of any subsequent email regarding this topic, and be
>>sure to include
>>  [mailing list name]@mit.edu in the "To" or "CC" field. In this way, all
>>information
>>  regarding this topic may be tracked in our database.
>>
>>  Sincerely,
>>  The MIT Support Process
>>
>>
>>  -----------
>>  [Include original email here].
>>================================================================
>>
>>
>>Hope this helps,
>>-Debi
>>
>>
>>-------------
>>Debi Fuchs, Consultant
>>MIT Information Systems
>>Computing Help Desk Group
>>77 Massachusetts Avenue, 11-319
>>Cambridge, MA  02139
>>(617) 253-7812
>>debi@mit.edu




home help back first fref pref prev next nref lref last post