Recently, Jose posted:

I was referring to your reply to my post where I added an extra "OT:
(was..." and your reader posted only " OT - OT:" If your app
didn't do that, then you did for some reason that really escapes me.
;-)

Hmmm. I noticed that; I didn't notice that =my= app did it. Trying
it again... hmmm.. curiouser and curiouser. That's a bizzare one! I
guess my app =does= sometimes "oddly truncate subject lines". What
does =your= app do as a reply to your multicolon message (subject
line below)?

OT - OT: (was: the OT tag and the Re bug.)

My app (OE) retains the full line as submitted. Other examples in the
original thread suggest that OE may not be the only app that handles this
situation correctly.

Is there really a downside to avoiding a colon after a prepend?

I wouldn't say there is a downside, but who knows if that solves the
problem for all readers, or that some other reader anomalies won't create
the same kind of "problem" with other subject line content?

Neil