ml>>> errrr... take your pick at the PROGRAMMERS you want "shot"
ml>>> then... it's not the mail SYSTEM that has the problem but
ml>>> the programmers that can't determine things correctly...
ml>>> how many times have you seen something like this?

ml>>> ___----------
ml>>> this was under a line of all dashes

ml>> HA!! something out there cannot tell the difference between a
ml>> dashed seperator and a real tearline! my point with the above
ml>> is made abundantly clear...

 PE> That was likely your own system, Mark.  You are responsible for
 PE> your own packet.

no shit... and it was not my system, paul. my system doesn't care about
tearlines and it surely doesn't modify them without my say so.

another test for paul.
--------------------
this line is under 20 dashes.

PE>> Mark!  Listen!  If tearlines are made compulsory (ie you are
PE>> the only person in the entire world that needs to update their

you really need to get out more, paul... i'm NOT the only one...

ml>> the above demonstration is not enough proof that there's much
ml>> software out there that cannot tell the difference is a
ml>> tearline and a dashed seperator line?

 PE> I'm not surprised since it's technically impossible at the moment.

to tell the difference between a "real" tearline and user entered
text? the above samples cannot be a tearline because of at least TWO
things...

  1. there is NO SPACE after the first three dashes.
  2. the origin line doesn't immediately follow it.

wake up paul... you're starting to sound like some others who used to
participate in here mumbling in their dreams... >

)\/(ark