Re: [Evolution] Bounce/remail command

["Jeffrey P. Lanza" <jpl alumni unh edu>]

On Wed, 19 Apr 2000, Christian Borup wrote:

> > > OK I'll bite.
> > > Could you explain why you use bounce instead of forward?
> > > I used it a fair bit in pine long time ago, but only because it didn't forward
> > > right.
> >
> > Basically, I have 2 email accounts,
> > one for list emails and one for private emails.
> > If there's an email to the list account that I want to follow up on, and think
> > it is likely to turn into a discussion, that I don't want to loose track of,
> > then I can bounce it to the private account. Likewise email that should have
> > gone to the private account, but went to the list one, can be redirected without
> > hassle.
> >
> > Only the private account can print emails, so if there's an interesting mail on
> > the list I can bounce it to the other account and print it without having > in
> > front of everything.
>
> But a forwarded message doesn't have to be mangled, in fact it should
> just be forwarded as is in a message/rfc822 mimepart (with headers and
> everything). This way the original message can be read, printed or
> even replied to. Just because many mail clients forward stuff wrongly,
> doesn't mean we need to keep doing so.

Christian,

  You make a good point when you say that forwarded messages don't have to
be mangled; I forgot that when reading the first comment.  The only time
reply separators (ie. ">") should be used is when one is replying to a
message.  However, the bounce command still serves an important function
in that it passes the message along such that it still appears to come
from the original sender. On the other hand, forward is intended when you
want the target to know that you have looked over the message and perhaps
added comments.

-Jeffrey

--------------------------------------------------------------------------
                 Jeffrey P. Lanza <jpl alumni unh edu>
Computer Science Department             ResNet Second-Level Support
Engineering and Physical Sciences       Computing and Information Services
University of New Hampshire             603-862-4242, questions unh edu