🚀 go-pugleaf

In article <dyNxFej030n@sktb.demon.co.uk>, Paul L. Allen wrote:
>  
> Seems reasonable to me.  When I contemplated fixing Arc KA9Q I was just
> going to make the ">" code conditional on having the separator set to
> "From".  I suppose making it insert ">" before any instance of the separator
> in the body is a better idea.  Mind you, that will only improve matters
> if mailers which detect a particular separator detect "\nseparator" and
> not just "separator", but it's still a better idea than mine.

At present, PC-Elm and the like use "\nFrom " as the separator. To all intents 
and purposes this can be interpreted as "\nFrom *\n". (Note that "From " is 
merely required to start a line, not be its sole contents.) When a separator 
is used as far as KA9Q is concerned it represents the whole line, so 
"\n[defined separator]\n" is the search key; whether or not PC-Elm expects 
such a separator to be the entire line or just start it I don't know. (I've 
interpreted some of the comments in this thread as meaning that PC-Elm does 
support user-defined separators, something which i was not previously aware 
of.)

In practice a common user defined separator is "^A^A^A^A" (ie control-A times 
four), which is unlikely to appear in a message let alone on a line by itself. 
The obvious exceptions are malicious use and test mail. 

Mark.
-- 
int MeaningOfLife (void) { return 42; }   // mcr@holly.demon.co.uk
function MeaningOfLife :integer; begin MeaningOfLife := 6 * 9 end;