NP>  BTW: You also mentioned that it could be changed to do XXDecoding
NP> instead. What is the change in UU > XX decoding, and how do I
NP> detect which was used to encode the file?
You guess! :) , look at the characters used if they are all from the XX 
ncode
set then it's been XXencoded, check the first line in most cases that will
contain enough information to tell you which set to use, but if it later
proves not to be XXencoded you'll have to start again...
the probability of a false detection of XXencoding by simply checking the
first line of data is extremely low if the original file was compressed (zip
or something)
Here's a table of the characters used in uuencoding
table
`!"#$%&'()*+,-./0123456789:;?
@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_
here's the same table for XX
table
+-0123456789ABCDEFGHIJKLMNOPQRST
UVWXYZabcdefghijklmnopqrstuvwxyz
with UUencoding some encoders use ' '(space) instead of '`'(back-tick)
NP>  Also: Do you have any examples on UUDemime?  What is different with
NP>        one, and how do i detect if a file was encrypted with this?
I really don't know, but this I have discovered something uses this table:
this _MAY_ be mime (but don't count on it unless you get confirmation)
table
`abcdefghijklmnopqrstuvwxyz;?
@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_
my decoder as it is written will handle all the above tables except the
XXencode one.
The XX standard (I think) allows a table like the ones above to precede the
data (it comes before the begin line) and it's presence should force the
decoder to use that the data from that table to do the decoding, the table is
not required to exactly match one of the above, it must merely follow the
format (2 lines, 32 characters each).
Bye.
--- EzyQwk V1.20 01fa018d
---------------