🚀 go-pugleaf

In article <479c26d990jsd@argonet.co.uk>, Jonathan Duddington
<jsd@argonet.co.uk> wrote:
> 
> I'm still not sure though why (some) UUE attachments have every line
> ending in an 'a' character.

I /think/ it's just an end-of-line character in case newlines get lost?

> How should an attachment be recognised?
> Anything starting with "begin 644 "?
> Or only if it's after the sig. (if there is a sig.)?
> Does it have to have "644" in the "begin" line?
>   (the Unix UUE document doesn't say it must be "644")
> If not, then does "begin" at the start of *any* line of the message mean
>   an attachment?  Or "begin <number>" ?

The "644" is an octal number giving private/public/read/write access;
I don't know the bit assignments, but suspect your final option of
recognising "begin <number>" would be the most appropriate, remembering
that there will/should be a matching "end" after all the gubbins.

John


-- 
Don't ask the question if you cannot live with the answer.
 __    ZFC: B _               (protovale@argonet.co.uk)
  | _ |_  _  |_||| _| _ _  _|   john@protovale.co.uk
(_j(_)| )| ) | |||(_|| (-`(_|    in and around Oxford