🚀 go-pugleaf

Jonathan Duddington (jsd@argonet.co.uk) wrote:
: There seem to be two topics:
: a.  Basic UUE
: b.  Attachments in mail and news messages.

: How should an attachment be recognised?
: Anything starting with "begin 644 "?

Certainly not 644, because 644 represents file access permission bits
which could be anything (well, any three numbers between 0 and 7).

'begin nnn' looks like it might be the best you can get, although you could
perhaps run a few checks to see if the rest looks like UUE (eg check for
equal length lines and 'end').

: Or only if it's after the sig. (if there is a sig.)?

Not as far as I know.

: Does it have to have "644" in the "begin" line?
:   (the Unix UUE document doesn't say it must be "644")

No (see above).

Furthermore, uuencode on this Linux system seems to put the filename
after the 'begin nnn' (I just got begin 600 /dev/stdout).

: If not, then does "begin" at the start of *any* line of the message mean
:   an attachment?  Or "begin <number>" ?

You'd probably have to try it out on any readers you have access too.

I could perhaps post or e-mail a short (1 or 2 character) attachment
from knews if you like? (I'm not using ATM, though).

--
alex@hayward.u-net.com; xelah@ferret.lmh.ox.ac.uk