BAD AOL Messages
John Hanks
to me like this one.
I get one message inside of another inside of another and on and
on. Is there some setting in Pegasus that can fix this?
------- Forwarded Message Follows -------
From: m...@aol.com
Date sent: Thu, 8 Oct 1998 23:13:48 EDT
To: Hrts...@aol.com, Matt...@aol.com, Sultr...@aol.com,
Tenmo...@aol.com, RGuet...@aol.com, jha...@sos.net
Subject: Fwd: A TRUE FRIEND WILL SEND THIS BACK
This is a multi-part message in MIME format.
--part0_907902830_boundary
Content-ID: <0_907902830@inet_out.mail.aol.com.1>
Content-type: text/plain; charset=US-ASCII
from deborah
--part0_907902830_boundary
Content-ID: <0_907902830@inet_out.mail.aol.com.2>
Content-type: message/rfc822
Content-transfer-encoding: 7bit
Content-disposition: inline
From: Matt...@aol.com
Return-path: <Matt...@aol.com>
To: JuJuB...@aol.com, Wndy...@aol.com,
DIA...@aol.com,
Care...@aol.com,
Hidi...@aol.com, Tenmo...@aol.com, ell...@hotmail.com,
Adict...@aol.com, Crve...@aol.com
Subject: Fwd: A TRUE FRIEND WILL SEND THIS BACK
Date: Thu, 8 Oct 1998 14:11:32 EDT
Mime-Version: 1.0
Content-type: multipart/mixed;
boundary="part1_907902830_boundary"
--part1_907902830_boundary
Content-ID: <0_907902830@inet_out.mail.aol.com.3>
Content-type: text/plain; charset=US-ASCII
--part1_907902830_boundary
Content-ID: <0_907902830@inet_out.mail.aol.com.4>
Content-type: message/rfc822
Content-transfer-encoding: 7bit
Content-disposition: inline
From: Crve...@aol.com
Return-path: <Crve...@aol.com>
To: Snugg...@aol.com
Cc: Tenmo...@aol.com, Pati...@aol.com,
HOMER...@aol.com,
Zoot...@aol.com,
Tma...@aol.com, Misw...@aol.com, Boein...@aol.com,
Glowo...@aol.com, Oof...@aol.com, Bali...@aol.com,
Mary...@aol.com,
Xlad...@aol.com, APegs...@aol.com, Gunr...@aol.com,
A68V...@aol.com, Maur...@aol.com, Matt...@aol.com,
Tige...@aol.com, Rbbin...@aol.com, MMou...@aol.com
Subject: Fwd: A TRUE FRIEND WILL SEND THIS BACK
Date: Thu, 8 Oct 1998 13:59:41 EDT
Mime-Version: 1.0
Content-type: multipart/mixed;
boundary="part2_907902830_boundary"
--part2_907902830_boundary
Content-ID: <0_907902830@inet_out.mail.aol.com.5>
Content-type: text/plain; charset=US-ASCII
--part2_907902830_boundary
Content-ID: <0_907902830@inet_out.mail.aol.com.6>
Content-type: message/rfc822
Content-transfer-encoding: 7bit
Content-disposition: inline
From: Mary...@aol.com
Return-path: <Mary...@aol.com>
To: Kre...@aol.com, ROSE...@aol.com, Kall...@aol.com,
MN4W...@aol.com,
Crve...@aol.com
Subject: Fwd: A TRUE FRIEND WILL SEND THIS BACK
Date: Thu, 1 Oct 1998 15:31:38 EDT
Mime-Version: 1.0
Content-type: multipart/mixed;
boundary="part3_907902830_boundary"
--part3_907902830_boundary
Content-ID: <0_907902830@inet_out.mail.aol.com.7>
Content-type: text/plain; charset=US-ASCII
--part3_907902830_boundary
Content-ID: <0_907902830@inet_out.mail.aol.com.8>
Content-type: message/rfc822
Content-transfer-encoding: 7bit
Content-disposition: inline
From: Kall...@aol.com
Return-path: <Kall...@aol.com>
To: MOi...@aol.com, Mary...@aol.com, Ag...@aol.com,
SxyA...@aol.com,
On2L...@aol.com, Soya...@aol.com,
Teres...@aol.com,
Lovel...@aol.com
Subject: Fwd: A TRUE FRIEND WILL SEND THIS BACK
Date: Thu, 1 Oct 1998 13:59:11 EDT
Mime-Version: 1.0
Content-type: multipart/mixed;
boundary="part4_907902830_boundary"
--part4_907902830_boundary
Content-ID: <0_907902830@inet_out.mail.aol.com.9>
Content-type: text/plain; charset=US-ASCII
--part4_907902830_boundary
Content-ID: <0_907902830@inet_out.mail.aol.com.10>
Content-type: message/rfc822
Content-transfer-encoding: 7bit
Content-disposition: inline
From: Fantc...@aol.com
Return-path: <Fantc...@aol.com>
To: Booga...@aol.com, Pjh41...@aol.com,
Scou...@aol.com,
Kall...@aol.com Subject: Fwd: A TRUE FRIEND WILL SEND
THIS BACK Date:
Thu, 1 Oct 1998 09:40:37 EDT Mime-Version: 1.0 Content-type:
multipart/mixed;
boundary="part5_907902830_boundary"
--part5_907902830_boundary
Content-ID: <0_907902830@inet_out.mail.aol.com.11>
Content-type: text/plain; charset=US-ASCII
--part5_907902830_boundary
Content-ID: <0_907902830@inet_out.mail.aol.com.12>
Content-type: message/rfc822
Content-transfer-encoding: 7bit
Content-disposition: inline
From: Booga...@aol.com
Return-path: <Booga...@aol.com>
To: Fantc...@aol.com, PHT...@aol.com,
GASS...@aol.com,
Pjh41...@aol.com,
Joey4...@aol.com, KM...@aol.com
Subject: Fwd: A TRUE FRIEND WILL SEND THIS BACK
Date: Wed, 30 Sep 1998 02:20:02 EDT
Mime-Version: 1.0
Content-type: multipart/mixed;
boundary="part6_907902830_boundary"
--part6_907902830_boundary
Content-ID: <0_907902830@inet_out.mail.aol.com.13>
Content-type: text/plain; charset=US-ASCII
--part6_907902830_boundary
Content-ID: <0_907902830@inet_out.mail.aol.com.14>
Content-type: message/rfc822
Content-transfer-encoding: 7bit
Content-disposition: inline
From: KM...@aol.com
Return-path: <KM...@aol.com>
To: Booga...@aol.com
Cc: EFH...@aol.com, CHAI...@aol.com,
Peace...@aol.com,
Swee...@aol.com Subject: Fwd: A TRUE FRIEND WILL SEND
THIS BACK Date:
Tue, 29 Sep 1998 18:38:44 EDT Mime-Version: 1.0 Content-type:
multipart/mixed;
boundary="part7_907902830_boundary"
--part7_907902830_boundary
Content-ID: <0_907902830@inet_out.mail.aol.com.15>
Content-type: text/plain; charset=US-ASCII
--part7_907902830_boundary
Content-ID: <0_907902830@inet_out.mail.aol.com.16>
Content-type: message/rfc822
Content-transfer-encoding: 7bit
Content-disposition: inline
From: AUNT...@aol.com
Return-path: <AUNT...@aol.com>
To: KM...@aol.com, Fas4...@aol.com, Syn...@aol.com,
VEG...@aol.com,
DameE...@aol.com
Subject: Fwd: A TRUE FRIEND WILL SEND THIS BACK
Date: Tue, 29 Sep 1998 14:01:55 EDT
Mime-Version: 1.0
Content-type: multipart/mixed;
boundary="part8_907902830_boundary"
--part8_907902830_boundary
Content-ID: <0_907902830@inet_out.mail.aol.com.17>
Content-type: text/plain; charset=US-ASCII
--part8_907902830_boundary
Content-ID: <0_907902830@inet_out.mail.aol.com.18>
Content-type: message/rfc822
Content-transfer-encoding: 7bit
Content-disposition: inline
From: Sarah...@aol.com
Return-path: <Sarah...@aol.com>
To: Izus...@aol.com, Fire...@aol.com, AUNT...@aol.com,
ACE...@aol.com,
lad...@WCTEL.NET, sbe...@usit.net, TUR...@aol.com,
B23...@aol.com
Subject: Fwd: A TRUE FRIEND WILL SEND THIS BACK
Date: Mon, 28 Sep 1998 07:58:52 EDT
Mime-Version: 1.0
Content-type: multipart/mixed;
boundary="part9_907902830_boundary"
--part9_907902830_boundary
Content-ID: <0_907902830@inet_out.mail.aol.com.19>
Content-type: text/plain; charset=US-ASCII
--part9_907902830_boundary
Content-ID: <0_907902830@inet_out.mail.aol.com.20>
Content-type: message/rfc822
Content-transfer-encoding: 7bit
Content-disposition: inline
From: B23...@aol.com
Return-path: <B23...@aol.com>
To: Nla...@aol.com, Dab...@aol.com, Sarah...@aol.com,
JK...@aol.com,
Heath...@aol.com
Subject: Fwd: A TRUE FRIEND WILL SEND THIS BACK
Date: Fri, 25 Sep 1998 19:06:08 EDT
Mime-Version: 1.0
Content-type: multipart/mixed;
boundary="part10_907902830_boundary"
--part10_907902830_boundary
Content-ID: <0_907902830@inet_out.mail.aol.com.21>
Content-type: text/plain; charset=US-ASCII
pass it on
--part10_907902830_boundary
Content-ID: <0_907902830@inet_out.mail.aol.com.22>
Content-type: message/rfc822
Content-transfer-encoding: 7bit
Content-disposition: inline
From: Nla...@aol.com
Return-path: <Nla...@aol.com>
To: MJDS...@aol.com, EAH...@aol.com,
LaBr...@aol.com,
TRAC...@aol.com,
MissG...@aol.com, MOBU...@aol.com,
Nikk...@aol.com,
ROBER...@aol.com, RLLA...@aol.com,
Mksvi...@aol.com,
Dund...@aol.com, Oz...@aol.com, Ngen...@aol.com,
MRSP...@aol.com,
Pate...@aol.com, B23...@aol.com, Dab...@aol.com,
Honc...@aol.com,
Jd...@aol.com, PHe46...@aol.com
Subject: Fwd: A TRUE FRIEND WILL SEND THIS BACK
Date: Fri, 25 Sep 1998 01:08:52 EDT
Mime-Version: 1.0
Content-type: multipart/mixed;
boundary="part11_907902830_boundary"
--part11_907902830_boundary
Content-ID: <0_907902830@inet_out.mail.aol.com.23>
Content-type: text/plain; charset=US-ASCII
--part11_907902830_boundary
Content-ID: <0_907902830@inet_out.mail.aol.com.24>
Content-type: message/rfc822
Content-transfer-encoding: 7bit
Content-disposition: inline
From: LaBr...@aol.com
Return-path: <LaBr...@aol.com>
To: Grac...@aol.com, EAH...@aol.com,
Bija...@aol.com, Brh...@aol.com,
Dumpi...@aol.com, Ngen...@aol.com,
BBY...@aol.com, Rms...@aol.com,
Flos...@aol.com, Dulce...@aol.com, Dund...@aol.com,
Hny...@aol.com,
Recd...@aol.com, MS...@aol.com,
BeWho...@aol.com, Dryca...@aol.com,
Kidf...@aol.com, TPe...@aol.com, ROPE...@aol.com,
Lyn83...@aol.com,
MARE...@aol.com, Mitr...@aol.com, Nla...@aol.com,
PEarl...@aol.com,
LamSh...@aol.com, TRAC...@aol.com
Subject: Fwd: A TRUE FRIEND WILL SEND THIS BACK
Date: Fri, 25 Sep 1998 00:17:01 EDT
Mime-Version: 1.0
Content-type: multipart/mixed;
boundary="part12_907902830_boundary"
--part12_907902830_boundary
Content-ID: <0_907902830@inet_out.mail.aol.com.25>
Content-type: text/plain; charset=US-ASCII
--part12_907902830_boundary
Content-ID: <0_907902830@inet_out.mail.aol.com.26>
Content-type: message/rfc822
Content-transfer-encoding: 7bit
Content-disposition: inline
From: TRAC...@aol.com
Return-path: <TRAC...@aol.com>
To: KMB3...@aol.com, POOK...@aol.com,
Syr...@aol.com,
Eveni...@aol.com,
LaBr...@aol.com, BBY...@aol.com, AntF...@aol.com,
Goo...@aol.com,
HSSTO...@aol.com
Subject: Fwd: A TRUE FRIEND WILL SEND THIS BACK
Date: Thu, 24 Sep 1998 20:12:38 EDT
Mime-Version: 1.0
Content-type: multipart/mixed;
boundary="part13_907902830_boundary"
--part13_907902830_boundary
Content-ID: <0_907902830@inet_out.mail.aol.com.27>
Content-type: text/plain; charset=US-ASCII
--part13_907902830_boundary
Content-ID: <0_907902830@inet_out.mail.aol.com.28>
Content-type: message/rfc822
Content-transfer-encoding: 7bit
Content-disposition: inline
From: Kim...@aol.com
Return-path: <Kim...@aol.com>
To: Dyd...@aol.com, Stor...@aol.com, CLi...@aol.com,
TRAC...@aol.com,
Kitty...@aol.com
Subject: Fwd: A TRUE FRIEND WILL SEND THIS BACK
Date: Thu, 24 Sep 1998 19:41:26 EDT
Mime-Version: 1.0
Content-type: multipart/mixed;
boundary="part14_907902830_boundary"
--part14_907902830_boundary
Content-ID: <0_907902830@inet_out.mail.aol.com.29>
Content-type: text/plain; charset=US-ASCII
--part14_907902830_boundary
Content-ID: <0_907902830@inet_out.mail.aol.com.30>
Content-type: message/rfc822
Content-transfer-encoding: 7bit
Content-disposition: inline
From: Swelc...@aol.com
Return-path: <Swelc...@aol.com>
To: Kim...@aol.com
Subject: Fwd: A TRUE FRIEND WILL SEND THIS BACK
Date: Thu, 24 Sep 1998 07:54:41 EDT
Mime-Version: 1.0
Content-type: multipart/mixed;
boundary="part15_907902830_boundary"
--part15_907902830_boundary
Content-ID: <0_907902830@inet_out.mail.aol.com.31>
Content-type: text/plain; charset=US-ASCII
It says send this to a good friend...5 of um...your 1 of um....you and
Steve stay outta the rain and wind.
--part15_907902830_boundary
Content-ID: <0_907902830@inet_out.mail.aol.com.32>
Content-type: message/rfc822
Content-transfer-encoding: 7bit
Content-disposition: inline
From: Clow...@aol.com
Return-path: <Clow...@aol.com>
Subject: Fwd: A TRUE FRIEND WILL SEND THIS BACK
Date: Wed, 23 Sep 1998 00:04:13 EDT
Mime-Version: 1.0
Content-type: multipart/mixed;
boundary="part16_907902830_boundary"
--part16_907902830_boundary
Content-ID: <0_907902830@inet_out.mail.aol.com.33>
Content-type: text/plain; charset=US-ASCII
--part16_907902830_boundary
Content-ID: <0_907902830@inet_out.mail.aol.com.34>
Content-type: message/rfc822
Content-transfer-encoding: 7bit
Content-disposition: inline
From: WMR...@aol.com
Return-path: <WMR...@aol.com>
To: ATuff...@aol.com, britt_...@hotmail.com,
Carou...@aol.com,
ChiLi...@aol.com, Clow...@aol.com, dia...@yahoo.com,
Fi...@aol.com,
Fyne...@aol.com, GEN...@aol.com, JstIn...@aol.com,
l.m...@mailexcite.com, Lipz...@aol.com,
miss...@hotmail.com,
Sugar...@aol.com, tpo...@sunnet.net, TRAF...@aol.com,
WaVn...@aol.com, Wildf...@aol.com, WlLD...@aol.com
Subject: Fwd: A TRUE FRIEND WILL SEND THIS BACK
Date: Sun, 20 Sep 1998 14:58:40 EDT
Mime-Version: 1.0
Content-type: multipart/mixed;
boundary="part17_907902830_boundary"
--part17_907902830_boundary
Content-ID: <0_907902830@inet_out.mail.aol.com.35>
Content-type: text/plain; charset=US-ASCII
--part17_907902830_boundary
Content-ID: <0_907902830@inet_out.mail.aol.com.36>
Content-type: message/rfc822
Content-transfer-encoding: 7bit
Content-disposition: inline
From: Texa...@aol.com
Return-path: <Texa...@aol.com>
To: Texa...@aol.com
Subject: A TRUE FRIEND WILL SEND THIS BACK
Date: Sat, 19 Sep 1998 20:59:41 EDT
Mime-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7bit
"A part of you has grown in me,
together forever we shall be,
never apart,
maybe in distance,
but not in heart"
~unknown
This is the sacred RED ROSE.
You MUST pass this rose on to at least 5 people within the hour of
receiving this rose. After you do, make a wish. If you have passed
it
on, your wish will come true and love will come your way shortly. If
you
didn't, your life will be cursed for eternity and you will not have any
love in your life whatsoever. It's your choice. Make the right
one.....
@->->>- ^v^ -<<-<-@
To a friend, from a friend
Pass it on to those who seem worthy of your time and
friendship.
*And remember never to forget who your friends are.
@->->>- ^v^ -<<-<-@
Remember:
"GOOD FRIENDS ARE HARD TO FIND .....................
SO CHERISH THE ONES YOU HAVE !!!"
--part17_907902830_boundary--
--part16_907902830_boundary--
--part15_907902830_boundary--
--part14_907902830_boundary--
--part13_907902830_boundary--
--part12_907902830_boundary--
--part11_907902830_boundary--
--part10_907902830_boundary--
--part9_907902830_boundary--
--part8_907902830_boundary--
--part7_907902830_boundary--
--part6_907902830_boundary--
--part5_907902830_boundary--
--part4_907902830_boundary--
--part3_907902830_boundary--
--part2_907902830_boundary--
--part1_907902830_boundary--
--part0_907902830_boundary--
Mark Zec
> to me like this one.
> I get one message inside of another inside of another and on and
> on. Is there some setting in Pegasus that can fix this?
Sure...use the "New Message" option. Use it to email your friend on AOL,
and tell them to stop forwarding the same chain letter to you over and
over again.
If that doesn't work, set up a filter rule to automatically delete any
mail from them.
Mark
Thought for the day:
Love means nothing to a tennis player.
Bob Jonkman
This is what John Hanks <jha...@sos.net> said about
BAD AOL Messages on 8 Oct 98, at 21:58
> Every once in awhile a friend of mine on AOL forwards a message
> to me like this one.
> I get one message inside of another inside of another and on and
> on. Is there some setting in Pegasus that can fix this?
You can't do anything about the message that's been sent to you,
except asking your friend to stop sending you nested attachments
instead of a text message. Some mailers don't support quoted
replies, and it's possible the AOL is one of those...
As a matter of e-mail nettiquette, if you want to include a threaded
dialogue in your message it is much easier for the recipient to read
when all the text is in the body of the message, with the various
replies marked with successive quotation indicators, eg:
Bob wrote:
> Look what I got!
>
> Larry writes:
>
> > Pass this on...
> >
> > John says:
> >
> > > Make Money Fast!
> > >
> > > Laurie mailed:
> > >
> > > > Get Rich Quick...
> > > >
> > >
> >
>
and so on.
Wish List item: I would really like to be able to define a different
quote indicator from a "Tools, Options" setting, and have the reader
recognize multiple quote indicators (like ">", "|", ")" and so on).
-----BEGIN PGP SIGNATURE-----
Version: 2.6.3i
Charset: cp850
Comment: PGP ensures message authenticity and non-repudiability
iQCVAwUBNh2246LoCveuM+mJAQEpCAP/d8XNv9w/n/lqE96zsK/H53KvlZJwTq+G
0iiMx+UIDUxodfeirjf0hpWLBVM9oTR/ZLnucUXI0o1VOOafYPDGCOi0naVXb/r0
n/s0Eysxqggh1uUnq8ow+Zl/rM1ag5eEoAR1LYYwpIw4QvegTN66WOhDoe73eukY
8hGktQY2qp0=
=rC7J
-----END PGP SIGNATURE-----
=====
Bob Jonkman SOBAC Microcomputer Services
4 Gold Pine Court Voice: +1-905-793-4537
Brampton ON L6S 2K6 Canada mailto:bjon...@sobac.com
Networking -- Office & Business Automation -- Consulting
Key Fingerprint: 9F AF A6 AC B5 67 BC 10 89 73 7C F0 CB 27 03 17
Key ID: AE33E989 mailto:bjon...@sobac.com?subject=send_key
Raymond W. Jerome
> Every once in awhile a friend of mine on AOL forwards a message
> to me like this one.
> I get one message inside of another inside of another and on and
> on. Is there some setting in Pegasus that can fix this?
It appears to me that the messages are being repeatedly forwarded
from one person to the next with all the forwarding headers included.
This is a symptom more of the behavior of people rather than the
behavior of the email programs. When someone clicks on "forward"
there is usually an option to include/not_include all headers. Many
email programs have 'include' set as default. This is especially
annoying when the email in question is one of those silly chain
letters such as you posted here. There are two ways to cure this:
When forwarding email chose the option to NOT include the previous
headers, or, the best solution is to simply not forward silly chain
letters.
-----BEGIN PGP SIGNATURE-----
Version: PGP 5.5.5 -- QDPGP 2.12
Comment: Security through Encryption
iQCVAwUBNh3TKa1VAe72ewqVAQFOeAP/fmaMEEtFWkTLHNLJsfdqc4jYp2JE7GNy
A+IBgIfHr5gM53lkSykyUvx2tdDbK1tTHENdpvcsKHmKJWWYn7FcVEz2uKrf4WUK
AE9xV8TenfplgXDMbmsI73WzXYUXGPFxj1I/3ZQU3SJWTjgRPjHFliyAHEzOA2Oo
p9QXBaZfLdQ=
=XODy
-----END PGP SIGNATURE-----
Owl o,o
Raymond W. Jerome
JW...@USA.net
My PGP Public Key can be found at:
http://www.bit-net.com/~jwrey2/
---- PGP Key fingerprint ----
---- 95 72 24 36 59 75 40 5E AC 97 8B A0 56 D1 63 13 ----
Abbott Wool
part:
> Wish List item: I would really like to be able to define a different
> quote indicator from a "Tools, Options" setting, and have the reader
> recognize multiple quote indicators (like ">", "|", ")" and so on).
Bob;
I wonder why? On a mail list I run, someone changed their
quote indicator. Of course nobody reading his mail could
then parse threaded discussion he quoted.
If anything might be a quote indicator, how could a reader
decide which one to honor? If several people were in a
threaded quote all with different quote indicators would it
br readable by anyone?
I think this is one of those things were sticking with the
standard is far better than offerring options.
Just my 2c
Abby
^^^^^^^^^^^^^^^^^^^^^^^
Abbott Wool
Principal, Abbott Wool Media / Marketing, LLC
Multicultural, Hispanic and Interactive Communications
aw...@awool.com http://www.awool.com
(516) 295-1342 Fax(516) 295-5370
Publisher, Advertising Media Internet Center http://www.amic.com
Grant Root
> Every once in awhile a friend of mine on AOL forwards a message to
> me like this one. I get one message inside of another inside of
> another and on and on. Is there some setting in Pegasus that can
> fix this?
Telling the sender not to pass along chain letters would be one
fix...
But as far as Pegasus Mail is concerned, nothing is broken. The
program is displaying the message correctly for the way it is
formatted.
If you want to display it as a flat text file, hold down the CTL key
while you double-click the message to open it.
Grant Root
MIS Supervisor, Dayton-Phoenix Group, Inc.
Fred Viles
"Re: BAD AOL Messages":
} On 9 Oct 98, at 3:10, in Re: BAD AOL Messages, Bob Jonkman wrote, at least in
} part:
}
} > Wish List item: I would really like to be able to define a different
} > quote indicator from a "Tools, Options" setting, and have the reader
} > recognize multiple quote indicators (like ">", "|", ")" and so on).
}
} Bob;
}
} I wonder why?
So quoted material can more often be correctly recognized, and benefit
from special handling in Pegasus (colored, preserved during reformat).
} On a mail list I run, someone changed their
} quote indicator. Of course nobody reading his mail could
} then parse threaded discussion he quoted.
Huh? Why not?
} If anything might be a quote indicator, how could a reader
} decide which one to honor?
In the current Pegasus, it should at least honor the quote string
configured in pmail.ini. The wish is for Pegasus to support a
configurable list of quote strings, like Free Agent does. At least it
would be nice if Pegasus were hard-coded to recognise more of the
common choices. Either way, it would honor all of them.
} If several people were in a
} threaded quote all with different quote indicators would it
} br readable by anyone?
Sure, why not? More readable, IMHO, because the different quote
strings make it easier to keep track of who is "speaking".
} I think this is one of those things were sticking with the
} standard is far better than offerring options.
That's a logical argument, but it is based on the mistaken assumption
that there is a standard. ">" and "> " are very common, perhaps even
most common (certainly on this list for obvious reasons), but it is not
a "standard".
"|" and "| " are also very common, as are ")" "=>", and others.
- Fred Viles <mailto:f...@episupport.com>
Dagan Sgiath
=> Wish List item: I would really like to be able to define a different
=> quote indicator from a "Tools, Options" setting, and have the reader
=> recognize multiple quote indicators (like ">", "|", ")" and so on).
I know what you mean... as you can see from my quoted text above, I don't use
a standard '>' character to quote my mail, and neither do some of my friends.
Support of more characters would be great!
Dagan
([XXH<>()<>HXX])=============================
"Look, good against remotes is one thing. Good against the living, that's
something else."
Han Solo, Star Wars 1977.
Join the Rebel Squadrons. Visit http://www.RebelSquadrons.org/
Bob Jonkman
This is what Abbott Wool <aw...@awool.com> said about
Re: BAD AOL Messages on 9 Oct 98, at 9:37
> On 9 Oct 98, at 3:10, in Re: BAD AOL Messages, Bob Jonkman wrote, at
> least in
> part:
>
> > Wish List item: I would really like to be able to define a different
> > quote indicator from a "Tools, Options" setting, and have the reader
> > recognize multiple quote indicators (like ">", "|", ")" and so on).
>
> Bob;
>
> I wonder why? On a mail list I run, someone changed their
> quote indicator. Of course nobody reading his mail could
> then parse threaded discussion he quoted.
That's my point -- because different commenting strings aren't
recognized, the mailer doesn't display quoted paragraphs with any
special font or colour, and people can't easily identify what part is
the quote and what part is the new message.
> If anything might be a quote indicator, how could a reader
> decide which one to honor? If several people were in a
> threaded quote all with different quote indicators would it
> br readable by anyone?
When Pegasus v3.0 was first released I mentioned this in a bug
report. I'd like to propose that the "Commenting String" entry in
PMAIL.INI accepts a delimited list of (user defined?) strings, and
that the reader accepts all of these and highlights the text. The
editor would use the first entry to create a quoted reply.
F'rinstance:
Commenting String = "> ","=} ","| ",") "
This would cause lines prefixed with any of the entries to be
highlighted, but only "> " gets used in new replies.
> I think this is one of those things were sticking with the
> standard is far better than offerring options.
Trouble is, there is no standard, just conventions of use. While ">
" is the most common, I've seen all of the commenting strings in my
example used in newsgroups (and to a lesser extent in mail). I'm not
at all proposing that Pegasus be morphed into a news reader, but any
news message could be forwarded as mail, so Pegasus should handle the
commenting strings used there.
-----BEGIN PGP SIGNATURE-----
Version: 2.6.3i
Charset: cp850
Comment: PGP ensures message authenticity and non-repudiability
iQCVAwUBNh9Wo6LoCveuM+mJAQHMDAQAoZUZmA8iCRF10SBmnRByjVfV6o+Iw5+u
LYNtepZZfp/6by/KCWFyNpD+VukLnQfXVZS685XWDQ4W6Dm80dRVNFgMO5Go+93Z
e8EoeLSV9z4qMwIBq3A98l1y8l8p2fiS4fO+dO4yTX5GWrycvJ1kNCQAE3G7QNET
y29KOAiXGqM=
=BU86