LISTSERV mailing list manager LISTSERV 16.5

Help for JESSE Archives


JESSE Archives

JESSE Archives


JESSE@LISTSERV.UTK.EDU


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Monospaced Font

LISTSERV Archives

LISTSERV Archives

JESSE Home

JESSE Home

JESSE  October 2012

JESSE October 2012

Subject:

tech glitch jESSE msgs

From:

Gretchen Whitney <[log in to unmask]>

Reply-To:

Open Lib/Info Sci Education Forum <[log in to unmask]>

Date:

Fri, 12 Oct 2012 20:08:25 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (110 lines)

Greetings,

I started this msg to an individual subscriber but thought that more might
be interested. It is technical. If technical stuff is not your interest
skip to the last few paras for advice.

   The usual reason for labeling a msg "rec'd with a technical glitch"
is that the person REPLYing has put the jESSE address as a "cc" or
"bcc", and has put the original SENDer (the person who first posted the
msg) in the "TO" statement. Given the variable practices of today's
e-mail clients and how they process listserv (and other discussion list
msgs) this is not uncommon.

   That is, the placement of what goes in the "TO" statement is in part
your choice, and in part the determination of your e-mail client.

   The listserv software enables me to approve a msg for jESSE with a
simple OK command as a reply to the listserv software, AS LONG AS the
jESSE listserv address appears in the TO statement, and not any other one.

   Some lists are configured to send a reply to a listserv post to the
individual, first poster (for example a disability list that I belong to,
which is incessantly rained with msgs like "please post to the list".
jESSE is configured to send replies to a jESSE post to the list itself
(hence the lack of rain).

   It appears that some e-mail clients also have such configurations, in
that sensing a listserv or other discussion post, they are configured to
send a reply to such a msg to the original poster, with the jESSE list as
a "cc" or "bcc".

   I recall some early e-mail clients who had only two REPLY functions:
REPLY and REPLY ALL, and who knows what they put into these two fields
when the msg was from a listserv (mailbase, listproc, etc) or whatever
software the discussion list was based on.

   Once or twice a week I get msgs directed to jESSE which don't appear to
have the jESSE list address in the TO statement. I can't use the
automated OK mechanism which directly forwards the REPLY to the jESSE
list.

   In this case, I have two choices: (1) work with the person trying to
REPLY to a jESSE msg to figure out what went wrong, and this person may
not be really comfortable with listserv software, STMP protocols, other
standards for e-mail, or e-mail clients, or (2) copy the REPLY person's
msg into a new msg that I know will get to the listserv software and get
out to jESSE readers right away. In that case, I include the REPLY
person's header information and the complete posting. I label these as
"received with a technical glitch" because I have no idea exactly what
went wrong.

   But the msg goes out quickly and without a fuss. And it gets posted to
the jESSE archive so that you can see if your msg was distributed to the
jESSE list.

   The difference between these two processes is this: If I can use the OK
mechanism, the msg is sent out clearly as sent in and without any editing
on my part. I clearly have not touched it. If I have to copy the msg to
a new msg and send it as one "received with a technical glitch" one could
fuss that I edited the msg. But I didn't and don't.

   The point here is this: If you read a msg from jESSE that says
"received with a technical glitch" DO NOT assume that the person who is
REPLYing has a problem or is anything else negative. There are WAY TOO
MANY variables in listserv or discussion list software to sort this out.
And there is NO WAY IN H*** that I am going to insist that everyone use
the same e-mail client to comunicate with a community. People who do (and
we know who they are) are just (&^%$$#@).


    DO assume that the msg so labeled is an honest copy of the original,
and that the original REPLYer (or sometimes SENDer) just unavoidably ran
afoul of the still-lacking standards for e-mail communication and clients.


    I hope that this clarifies issues for everyone.

    Send away. Neither rain, nor sleet, nor lack of standards, nor poorly
designed e-mail clients, will prevent the mail from getting through. At
least as far as I can help it. :-)

    --gw

<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
Gretchen Whitney, PhD, Retired
School of Information Sciences
University of Tennessee, Knoxville TN 37996 USA [log in to unmask]
http://web.utk.edu/~gwhitney/
jESSE:http://web.utk.edu/~gwhitney/jesse.html
SIGMETRICS:http://web.utk.edu/~gwhitney/sigmetrics.html
<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>

---------- Forwarded message ----------
Date: Fri, 12 Oct 2012 11:23:30 -0400
From: "listserv.utk.edu LISTSERV Server (15.5)" <[log in to unmask]>
To: Gretchen Whitney <[log in to unmask]>
Subject: JESSE: approval required (8C720435)

This message was originally submitted by [log in to unmask] to the JESSE list
at LISTSERV.UTK.EDU. You can approve it using the "OK" mechanism (click on the
link below), ignore it, or repost an edited copy. The message will expire
automatically. You do not need to do anything if you just want to discard it.
Please refer to the List Owner's Manual at
http://www.lsoft.com/resources/manuals.asp if you are not familiar with the
"OK" mechanism. These instructions are being kept purposefully short for your
convenience in processing large numbers of messages.

To APPROVE the message:
http://listserv.utk.edu/cgi-bin/wa?OK=8C720435&L=JESSE

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
August 2003
July 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003
December 2002
November 2002
October 2002
September 2002
August 2002
July 2002
June 2002
May 2002
April 2002
March 2002
February 2002
January 2002
December 2001
November 2001
October 2001
September 2001
August 2001
July 2001
June 2001
May 2001
April 2001
March 2001
February 2001
January 2001
December 2000
November 2000
October 2000
September 2000
August 2000
July 2000
June 2000
May 2000
April 2000
March 2000
February 2000
January 2000
December 1999
November 1999
October 1999
September 1999
August 1999
July 1999
June 1999
May 1999
April 1999
March 1999
February 1999
January 1999
December 1998
November 1998
October 1998
September 1998
August 1998
July 1998
June 1998
May 1998
April 1998
March 1998
February 1998
January 1998
December 1997
November 1997
October 1997
September 1997
August 1997
July 1997
June 1997
May 1997
April 1997
March 1997
February 1997
January 1997
December 1996
November 1996
October 1996
September 1996
August 1996
July 1996
June 1996
May 1996
April 1996
March 1996
February 1996
January 1996
December 1995
November 1995
October 1995
September 1995
August 1995
July 1995
June 1995
May 1995
April 1995
March 1995
February 1995
January 1995
December 1994
November 1994
October 1994
September 1994
August 1994
July 1994
June 1994
May 1994
April 1994
March 1994
February 1994
January 1994

ATOM RSS1 RSS2



LISTSERV.UTK.EDU

CataList Email List Search Powered by the LISTSERV Email List Manager