CBSRMT: [ my CBSRMT homepage | CBSRMT timeline | RMT title dupes | collecting RMT | RMT FAQ | EG Marshall contract | links ]  
CBSRMT database (RMTdb) Project: [ view or search RMT db | about the RMTdb | how to contribute data to the RMTdb | Episode Guide errata | RMTdb MVP contributors ]  
CBSRMT cassette tape encoding project: [ Do you have RMT cassettes? | Encoding projects ]  
OTR and trades: [ my OTR collection | search my CDs | OTR I need | OTR FAQ | my favorite shows | OTR by Geography | Collecting and organizing | trading for newbies | 70s-80s radio revival ]  
getting OTR on the Net [ OTRCat Old Time Radio Show Catalog | downloading OTR | Xnews newsreader | OTR binaries | binary posting tips | using Xnews to complete OTR binaries | OTR on peer to peer (p2p) | OTRnap! | yEnc encode/decode ]  
Rio: [ RioVolt review | burning RioVolt firmware CDs | Rio PMP 300 review ]

Note: I'm working on the page now so you may see errors

Agent and yEnc multipart binaries

Agent up to 1.92 cannot parse some yEnc Subject lines. The main symptom is a failure to identify the segments as parts of a multipart binary (see inset image - all those segments should be recognized by Agent as as a binary file).

The Short Answer

For Agent to be happy, preliminary testing shows these Subject: line settings may help:

Subject: blah blah yEnc blah "filename.mp3" [1/87]
Criteria:

  1. the filename needs to be quoted ("filename.mp3"). In my own adventures with Agent, this seems to be a major win for Agent.
    Powerpost users will need to do this manually: "$F"

  2. the filename ("filename.mp3") and multipart tag ([1/87]) may need to be adjacent to help Agent parse the subject.
    Since the tag goes at the end of the line with PowerPost (and is beyond the poster's control), put the "$F" as the last thing in your PowerPost subject template. The tag will be appended to this and, poof, the two are automagically adjacent.

  3. As usual, no extraneous slashes, ()s, []s or other funky characters should be in the filename. We already knew that having 1/3 instead of 1 of 3 for the file count could hose Agent. Note the difference between 1/3 files and 1/3 segments in a multipart binary, anyway.

There are many unknowns, but the above format has been tested to work with Agent 1.92.

The actual spec says: [Comment1] "filename" yEnc (partnum/numparts) [size] [Comment2] but this has not been tested to work yet.

Some sources also indicate an Agent-based fix: edit agent.ini and set RequireFilenameWithTag=0. This changes the way Agent identifies multipart binaries. May or may not help.

This page best viewed with a monitor.

You can if you are not a spammer.

Amazon.com 100 Hottest Books, CDs, Videos, and DVDs.