.: Binky: method

 METHOD [method]

The METHOD command will tell Binky how you want files delivered to you. When the SEND or URL commands come across a binary file, that file must be encoded in order to send it through email. The default encoding is UUEncode. If you don't want UUEncode, or you would like to try another format, you can use the METHOD command to specify which other format you want the file in. Below is a description of all of the file formats on Binky.

UUE
UUEncoding -- the default. It is the "newer" UUEncode, which uses the ` character instead of spaces.
Encoded size: (BYTES / 3) * 4 + 2 * (BYTES / 45) + 17 +
FNSIZE
Rough estimate: 35% to 40% larger

XXE
XXEncoding -- Exactly the same as UUEncoding, but uses a different set of characters. It is said to go through mail gateways with less corruption.
Encoded size: (BYTES / 3) * 4 + 2 * (BYTES / 45) + 17 +
FNSIZE
Rough estimate: 35% to 40% larger

B64
Base 64 -- Also known as MIME (Multimedia Internet Mail Extension) encoding. It is supposed to appear as an attachment in your mail, if everything works right. B64 can not be used with the SPLIT command. Encoded size: (BYTES / 3) * 4 + (BYTES / 45)
Rough estimate: 33% larger

BtoA
Binary to ASCII -- Also known as base 85 encoding. It is the smallest encoding method that Binky currently supports. The "NUMSIZE" is in relation to the size of the numbers produced, which depends on the file. This value can range from 5 to 32 plus the number of digits in FNSIZE. I estimate 25.
Encoded size: (BYTES / 4) * 5 + 32 + FNSIZE + NUMSIZE
Rough estimate: 25% larger

DBG
Debug script -- This only works for files under 63k. This creates a script that you can feed to an old DOS program, debug, that will create the file for you. This is very useful if you do not have any decoding software yet.
Encoded size: 2 + FNSIZE + BYTES * 2 + (BYTES / 30) * 7
Rough estimate: 60% larger

BYTES = size (in bytes) of the file to be encoded
FNSIZE = length of the filename in characters