unofficial abma/aba faq
Annotated :: Single Page/Plain :: Text :: Notes

1. Preface
2. Introduction
3. Newsgroups
4. Encoding
     a. uu
     b. mime
     c. yEnc
5. Archives
     a. .rar/.r##/.part##.rar
     b. RAR recovery
     c. .ace/.c##
     d. .###
     e. .zip
6. Support Files
     a. .sfv
     b. .par/.p##
     c. .rev
     d. .idx/.sub/.ifo
     e. .smi/.ssa/.srt
     f. .nfo/.txt/.md5
7. Newsreaders
8. Posting
     a. Bad Requests
9. Auto-Posters
10. Hentai
11. Formats/codecs
     a. avi/ogm
     b. mpeg4
     c. mpg
     d. rm
     e. audio
     f. linux
12. News servers
13. Software
14. Appendices
     a. About the FAQ
     b. Mirroring the FAQ

The new home of the FAQ is http://animeusenet.org/wiki/.

This site exists only for historical/archival purposes.

4. Where are the files? I'm seeing garbage text...

Binary File Encoding [Akito, NetGear, ed.]

Because Usenet was originally developed for communication of text messages, it is not possible to post binary data in its natural form. To overcome this limitation, several binary encoding methods have been devised to allow posting of binary materials to the Usenet. Below are explanations of several of the most popular encoding methods.


On an older, less featured newsreader, you may see something like this:

	begin 644 filename.r10

This is known as a uuencoded format. The "begin 644 filename" line and the fact that every single line starts with "M" is a good way to recognize uuencode.

Any half decent newsreaders will automatically decode the file into binary formats so you would never actually see the code. So if you are having problems with the codes your best bet is probably get a new newsreader. Most news readers understand this kind of encoding and have the ability to decode the message back to its original form. See section 6 on good newsreaders for decoding.

A more verbose explanation of uuencode

Here's what this means. "begin 644 filename.r10": save this uuencoded text as filename.r10 with permissions 644 (that number is a Unix code that means let everyone read the file, and let the owner modify it).

You may also occasionally see messages encoded using some other system such as Base64. The principle is the same. Usenet was designed to transmit messages containing only printable letter, digits and symbols. Binary files like anime episodes containa wider range of data, so that data has to be transformed into text before posting it to Usenet.

Uuencode, aka uuencode/uudecode, is one of the popular forms of binary file distribution along the realms of passive file distribution. (Meaning it's not done in real-time, files are sent but received later, not instantly). Email and newsgroup messages are of such type.

Originating on UNIX systems (thus the UU means Unix-to-Unix), it is used by users who wish to send binary data to others who are using software that's not capable of processing binary code. Something like this would be a unix-based email client like PINE.

Basically how uuencode works is that it takes whatever binary attachment you are sending- it may be a WinRAR archive, an .rm or some executable- and translates (encodes) that file into a HUGE string of text garbage that only someone with the decoder can convert back to the original form. This way, it simplifies the transmission as no special protocol and/or software is needed. (Nearly all computers can do text transfer without problems. I say nearly because there is always some exceptions to the rule in the world of computers - just look at Windows).

In summary, uuencode is simply a utility, if you wish, that translates binary code into encrypted text to be sent: 1) Over a medium that cannot process binary transfers. 2) To a individual using software not capable of receiving binary attachments.


Now for MIME... (this is the uglier one as it involves Windows and Mac OS...)

Raw codes of MIME looks something like this:

If your mail reader is text-only
	This is a multi-part message in MIME format.

	Content-Type: text/plain;
	Content-Transfer-Encoding: 7bit

-OR- if your mail can read MIME encoded mails but can't handle the file type

	MIME-Version: 1.0
	Content-Type: multipart/mixed;
	X-Priority: 3
	X-MSMail-Priority: Normal
	X-Mailer: Microsoft Outlook Express 4.72.3110.5
	X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3

Again, current newsreaders will decode MIME automatically like uuencoded files.

MIME, aka Multi-purpose Internet Mail Extension, is an extension of the original E-mail protocol (an agreement between computers that data of such type [email] will be transferred using this set of specifics) to exchange different types of data. (Such as webpages, audio, video, and of course, text files)

How it works is that servers sending the transmission will insert MIME headers into the body where it instructs the client on HOW to handle the binary data that's to follow. Say it may be a webpage, then the client knows to launch the web browser to handle the attachment. (Or RealPlayer for those anime .rms ^_^ )

Currently only so many MIME types are registered on the Internet Assigned Number Authority (http://www.isi.edu/in-notes/iana/assignments/media-types/), as new file formats are surfacing as the days go by, the Internet MIME databases will be updated accordingly and YOU as the user, will need to download the appropriate software and update your computer so they can handle such files. Fortunately most installation programs take care of this for you on most platforms. (Called file associations - ie: files with .RM extension will be handle by RealPlayer, .HTM - web browser, MP3 - Winamp...etc)

In summary, MIME is a string of instructions inserted at the beginning of any web transmission that instructs the client receiving this how to deal with the binary attachments that's to come. By equipping themselves with the associated software, (which is usually widely available on the Internet) users will not have to hunt down software every time they receive a binary attachment.

Now, I've stripped down the definitions to avoid the complicated techno jargon, there is MUCHO to know about MIME but that I think is beyond the scope of this FAQ. There are numerous documents out there floating on the web on MIME and can be easily found using a search engine like www.google.com

The main difference between MIME and uuencode is that MIME is more user-friendly to newbies as it takes the guesswork out of the user on what software is used to deal with this piece of binary code. But uuencode is computer-friendly as it does not require fancy software to be able to receive such type of information.

Uuencode is the most preferred transmission type because most newsgroup servers will not handle binary transmissions therefore MIME is not recommended here at ABMA Make sure you are using a reader that is capable of uuencode or else you might have some complaints (or nasty comments from our "respected" SWong) coming your way =)

yEnc [xo, Keikai]

This section is currently in its preliminary stages, more information will be added in the next revision. A good deal of additional information is currently available in the notes for this section in the annotated FAQ: http://abma.x-maru.org/faq/annotated/encoding.php

yenc is an alternative to uuencoding for encoding of files posted to Usenet. A new decoder is required in order to process these files. Some news clients include native decoding of yEnc encoded files, however, many do not and will require some additional work and the use of an external decoder.

Details and the status of client support can be found at http://yenc.org.

Zen's web page hosts his excellent yEnc FAQ. This FAQ can be found at http://www.geocities.com/zenwebpage/yEncFAQ.htm and includes:

  • a consise explanation of yEnc
  • list and locations of news clients and binary posters that natively support yEnc
  • list and locations of manual encoding/decoding applications
  • possible workarounds and hacks for clients that do not have native support (including Agent)
  • links to many, many yEnc resources

It is also important that posters indicate in the subject when posting any binaries encoded in yEnc format. More specifically, make sure the word "yEnc" appears somewhere in the subject, preferably in the description.

Occasionally, files are posted with the extension .NTX. These are actually files that are yEnc'd prior to posting (usually via uuencode, thereby neutralizing any benefit of the yEnc format). They can be decoded using a standalone yEnc decoder such as yEnc32 or ydec.

Linux-specific information [xo, ed.]

On the Mac platform, the most popular newsreaders descend from the original Newswatcher and do not include uuencoding within the newsreader. Instead, a helper application is needed. YA-Decoder is a good utility for this and is available from http://www.newsreaders.com/link/jump.cgi?version=Sys71_yad. It has problems with some long file names, but less so than many other uudecoders available.


User Contributed Notes

Alacrity Fitzhugh
2002-02-14 06:03pm
Proposal for new addition to FAQ
Gathering info from this topic and other posts here is what I have so far...
Suggestions welcome... (as well as spell and grammer corrections)

( > indicates new information/suggested addition)

(Based on ABMAfaq.txt)

4. Encoding
a. uu
b. mime

> c. yEnc

5. Archives
a. .rar/.r##
b. RAR recovery
c. SFV files
d. .ace/.c##
> e. yEnc files

> e.1. Auto combining yEnc Files with Agent (use at your own risk)

> e.2. Decoding yEnc using Agent and a decoder
8. On posting...


> 4.c yEnc Encoding


> UU encoded and BASE64 encoded messages are still standard on Usenet.

> There are three general problems with these encodings - and the actual usage of such binary encodings

> They are Size and Overhead,No error-checking, and Bad multipart detection. yEnc was created to fix/address

> such problems.

> yEncode and MIME (as taken from http://www.yenc.org/)

> As some people would prefer to include a new encoding into the MIME structure a short discussion was made in
> comp.mail.mime. Unfortunately it is very difficult to introduce new transfer encodings and also the rest of MIME is
> pretty difficult (for non MIME specialists) this topic has been moved downwards on the priority list. A short
> example for a single binary and a multipart binary has been created and is available in the 'Documents' section.
> Treat it with CARE !

> There is a general approach if you want to embed a yEncoded message into MIME:

> Take the entire yEncoded message as one block and add all you need for embedding in front of it - and behind it.
> The =ybegin line with all parameters, the data and the =yend line should stay one block. Even if information is
> redundant - the =y lines should stay as they are specified (even for multiparts). This allows other decoders to
> detect such blocks - and decode them properly - even if all other information is stripped from your messages.

> 5.e What is yEnc?

> (as written by Zen's Web page yEnc FAQ -

> http://www.geocities.com/zenwebpage/yEncFAQ.htm)

> An usenet transport method similar to uuencode/base64/binhex/etc. but

> with more efficiency. Downloads and uploads are up to 30-40% faster.

> Also, it has error checking built-in. And it can be decoded out of

> sequence.

> Main yEnc site: http://www.yenc.org

> absmc yEnc FAQ: http://www.geocities.com/altbinariessoundsmusicclassical/yenc.html

> Onakra's How to work with yEnc: How to work with yEnc.txt

> yEnc is currently not fully supported by all news readers, such as

> Forte' Agent and Free Agent.

> News Readers supporting yEnc are:

> Xnews L5: http://xnews.3dnews.net - free

> Super Gravity: http://members.home.net/gravitypages - free

> MyNews: http://www.winews.net - free

> NewsPro: http://www.usenetpro.com - 30-day trial

> News Rover: http://www.newsrover.com - free demo

> Newsbin beta 4: http://www.newsbin.com - free trial

> Or save as raw in Agent (save message as a .txt file) and use an external decoder:

> http://code.blitzaffe.com/delphi.php or free decoder by yDec: http://www.yenc.org/ydec.htm


> For more information on decoding in Windows: http://www.yenc.org/ydec.htm

> For more information on decoding in Mac: Thoth - newsreader: http://www.thothsw.com (Brian Clark)

> Rosetta - decoder: http://www.thothsw.com (Brian Clark)

> For more information on decoding in Linux:

> How to decode YENC in LINUX (might work with other UNIXes too)according to Zathras [contributed by gloop]

> - Get nget (http://nget.sourceforge.net/) and newest bnews-utils (http://users.pandora.be/stef/)

> - Using nget, download what you want using the -K option.

> - Run "ydec *" in the same catalog.

> - Delete temp-files

> Now you should have all the files you downloaded in decoded format.

> 5.e.1. How to modify Agent to combine yEnc posts automatically (use at your

> own risk) [contributed by gloop]


> This does NOT solve all vertical spam.

> Here is the answer. Change

> RequireFilenameWithTag=1 to

> RequireFilenameWithTag=0

> Do this with a text editor such as Notepad or Editpad.

> This line is in Agent.ini which is in the Data folder of Agent

> [Attachment]

> [Attachment]

> RequireFilenameWithTag=1

> This option is enabled to make it less likely for Agent to mistakenly

> identify a single message that has a (N/M) tag in its subject as a

> section of a multipart message. When you retrieve new message

> headers, Agent scans the subject line to determine whether it's a

> section of a multipart message. All multipart messages are tagged

> with [N/M] (e.g., [1/6] or [9/14]). This setting controls whether

> Agent should also include a filename before or after the [N/M] tag.

> When non-zero, Agent will require a reasonable facsimile of a

> filename before or after the [N/M] tag.

> Changing this to 0 may cure the problems with yEnc but might create

> new problems elsewhere. So try/use at your own risk.

> 5.e.2. To Decode yEnc Posts Using Agent: [contributed by gloop]

> Using Agent, in the Message List Pane(tab)

> -Sort by author or subject (if your not, why?)

> -highlight all messages that are part of the posts

> -right click on selected messages, and "save all attachments"

> agent will download the bodies of the messages and mark as read

> -with all messages highlighted, "ALT+F" "save as"

> what should be checked is -unix message file

> -save raw message

> -no fields

> -saved file name "title".txt, and save this to the same directory

> where yEnc is located

> -then decode the txt file. Typically this has to be done in at a

> dos/command line prompt [C:\yenc\] with a command such as

> C:\ydec1\ydec.exe title.txt. In this case the decoder being used is ydec

> for Windows (http://www.yenc.org/ydec.htm)

> - This comand will decode the yenc files in to .rars, pars, etc.

8. On posting...
Here is a guideline on header labels on posts:

> [series] ep ## (format/sub or dub/encoding) file ## of ##

> encoding can be posted as UUE for standard uuencode and MIME or

> yEnc for yEnc encoding. Xnews ver L5 and Yencpost 2002 put the "yenc" in the subject line

> automatically.

For large posts that takes several days, a "Day # of #" should be
included as well.
Power-post [Onakra]

Another automatic poster for binaries is Power-Post 2000 (PP2K).

> For yEnc endcoded post get yencpost(a mod of powerpost2000):

> http://www.geocities.com/zenwebpage/Yenc-PowerPostBuild3.zip

Alacrity Fitzhugh
2002-02-14 09:05pm
>> 5.e.1. How to modify Agent to combine yEnc posts automatically >> (use at your own risk) [contributed by gloop] this was actually contributed by John Ross Mc Master
2002-07-22 07:54pm
> News Readers supporting yEnc are:

Also Binary News Reaper (AKA BNR2), which can be found at http://www.binnetwork.net/~bnr/bnr.html. It's free to use, and versions are available for both Windows and Linux. It's still in beta, though (As of Jul 22, '02).