LSTOWN-L Archives

LISTSERV List Owners' Forum

LSTOWN-L

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Rick Troth <[log in to unmask]>
Thu, 14 Sep 1995 13:58:39 CDT
text/plain (58 lines)
On Thu, 14 Sep 1995 12:57:35 EDT you said:
>On Thu, 14 Sep 1995 12:10:43 -0400 Dave Lampson said:
>
>>No, it is not that simple.  If you "forward" the message back to the
>>list, then it appears that all messages posted to the list come from
>>you, and you get those nasty embedded headers.  This is completely
>>unacceptable, and something even Majordomo is smart enough to handle
>
> I've found the term "forward" here to be somewhat ambiguous.
 
        Yes.   There are at least three meanings.
 
> In an earlier version of MailBook (formerly RiceMail) you could
> Forward the incoming post to the list.  Recent versions however
> produce the effects listed by Dave.  I now must use the Resend
> function, not Forward and I suspect this may be relevant to other
> such mail applications.
 
        I was chastised recently by a colleague who is  "in the know"
about mail/RFC822/MIME  (in short,  someone who bothers to read the
specs better than I)  for  sending something to him with  Resent-  tags
in the header.   I had used an older version of  MAILBOOK  (a RiceMail,
so you know it's old).   I didn't fully understand,  but I think he
wanted me to  "forward"  whatever it was,  and I had  "resent"  it.
 
        It seems there are at least three ways to do this:
 
            o   Bounce,  per Elm,  should direct something to
                whomever you wish without changing the headers.
                These can be as confusing to the recipient as a BCC.
 
            o   Forward,  per old MAILBOOK (RiceMail) will prepend
                Resent-  headers when sending the item,  and this
                seems to be more appropriately called  RESENDing.
 
            o   Forward,  per Pine and others,  inserts a  "forwarded
                message"  line of varying format  (textual,  and not
                suited to machine processing)  before the message,
                usually leaving you in the editor to add your own
                comments.   The original 822 header  (or part of it)
                may or may not be there.   (hopefully it's quoted
                if present)   Is this also  MAILBOOK's  current
                FORWARD function behaviour?
 
        I think I've seen a "forwarded" note where both the body and
original header were present and were quoted.   This looks  (to me)
too much like a reply,  and it's obviously not what you'd want when
passing on a moderated note.
 
        The whole situation really is an unfortunate mess,  as Eric says.
 
>  --Jim Cocks  Univ. of Louisville  <[log in to unmask]>
 
--
Rick Troth, BMC Software, Inc.  <[log in to unmask]>  <USNMNEWN@IBMMAIL>
2101 City West Blvd., Houston, Texas, USA, 77042   1-800-841-2031
* T H E  B E S T  L I T T L E  S O F T W A R E  H O U S E  I N  T E X A S *

ATOM RSS1 RSS2