TERMINOLOGY:

Throughout New Yanoff and its documentation we use the following
conventions:  "article" refers to a Usenet/NNTP message, "email" refers
to an email/SMTP message, "message" is generic including both/either
NNTP and/or SMTP messages, "Yanoff" refers to all versions of Yanoff,
"GPL Yanoff" refers to the original open-source Yanoff, "Yanoff-" refers
to the totally demoware (free) version of the private-branch (our)
Yanoff, "Yanoff+" refers to the trialware (pay-to-keep) version of the
private-branch (our) Yanoff, and "New Yanoff" refers to both "Yanoff-"
and "Yanoff+" We also abbreviate the word "Newsgroup" as "NG" and the
word "Message-ID" as "MID".

Q:  I was using Yanoff+ for a week or 2 and then a bunch of stuff
    stopped working; what happened?

A:  Yanoff+ will only allow the advanced features to work for 15 days.
    After this trial period, it disables them and reverts to the same
    feature set as exists in Yanoff-.  You may either continue to use
    Yanoff+ as-is (although it is better to downgrade to Yanoff- if
    that's your decision because it same features but smaller size) or
    register Yanoff+ to unlock the lost features (and also enable a few
    super-advanced features which are only available to registered
    users).

Q:  I love Yanoff+; how can I purchase a license and become a registered user?

A:  Basically, you send the registration fee to us via PayPal or US$
    Money Order along with the delivery email address and the user's
    HotSync ID.  Within 24 hours of the payment clearing, we will email
    to you a file which, when installed on the designated PDA, registers
    the payment and unlocks the advanced features.

Q: The app itself indicates I can pay by Credit Card; is that right? Is it safe?

A: Yes, we do offer a secure 3rd-party, encrypted, real-time fulfillment
   option for Credit Card purchases called "Pocket Purchase" and it is
   completely safe so long as you trust the end-service provider (we do).
   However we would much rather you order directly from the web pages because
   there are hefty surcharges to us (both in the form of CC fees and in the
   form of 3rd party service fees) which take a substantial bite out of our
   margin (the price to you is the same for any order method).  We provide
   this facility as a courtesy to our users who REALLY want to buy RIGHT NOW!
   If you can wait a day or so, please do order directly from the web pages
   as it really helps our bottom line when you do so.

Q: I heard there is SpyWare in New Yanoff; is that true?
Q: Are there any privacy concerns with using Yanoff?

A: All versions of Yanoff do nothing secretly; they only send email/articles
   when YOU tell it to and only add (with the exception of some mundane
   headers generated at transfer time) the text you give them.  Everything
   they use and do is available for you to see.  While New Yanoff has NO
   SpyWare, Yanoff+ does have limited "push" ability provided by Pocket
   Purchase through its conduit by which we can update the "nag" popups
   which are displayed when unregistered users launch Yanoff+.  This option
   is selectable during installation so if you don't want to allow these
   updates, you can prevent them from being transmitted to your PDA.  Be
   aware that the primary purpose of such updates is to notify users of
   temporary discounts (e.g.  "Buy a license by the end of tomorrow and
   receive a 20% discount" or some such).  Our Privacy Statement is
   available on our Legal Notices & Policies Page.

Q: I can't spare the extra memory that Pocket Purchase uses.
Q: I fear Pocket Purchase!  Save me!!!

A: Before you take the dramatic step of removing Pocket Purchase,
   be aware that:
   * Pocket Purchase only adds about 1 second to your HotSync duration.
   * PocketPurchase.prc only uses about 80K of memory on your PDA.
   * PocketPurchase.prc and the conduit are required to receive product
     discount "nag" updates from the PocketPurchase server.

   The initial 2.0 release of Yanoff+ required PocketPurchase.prc to decrypt
   the license keys but this is no longer the case.  The folks at Pocket
   Purchase worked quickly with us to create an update that allows any
   user to remove Pocket Purchase at any time and still use Yanoff+ including
   validating the license key.  The only things that are lost if Pocket
   Purchase is disabled are the convenience features Pocket Purchase provides
   ("nag" screen updates, real-time credit card validation, etc.).  There are
   several ways to disable or remove Pocket Purchase.  The simplest is to use
   the launcher or your favorite PDA file utility to delete
   'PocketPurchase.prc' from your PDA.  If 'PocketPurchase.prc' is not
   present, the conduit sits idle and does nothing.  If you further wish to
   uninstall the conduit, the simplest way is to run the Yanoff+
   uninstaller.  This does 2 things: it removes the Pocket Purchase conduit
   and it removes the Yanoff+ documentation (all of which is duplicated on
   the web at http://www.PalmYanoff.com anyway).  If you'd like to keep the
   documentation on your PC and wish to manually uninstall the conduit, then
   locate these files in your palm directory on your PC and delete them:
   * PocketPurchaseConduit.dll
   * PalmOSUplinkClientStub.dll
   * PalmOSUplinkClientDLL-xxxxxxxx.dll

   Power users may also want to remove the few registry entries that Pocket
   Purchase installs but really there is no need (and this can be quite
   dangerous if one does not know what one is doing).

Q:  What features are in Yanoff+ but not in Yanoff-?
Q:  What features are available to Yanoff+ which expire after the 15-day
    trial period?

A: There are 30 as follows:
   * Logging destination options other than "Alert" (and none).
   * The "Use Auth" option for Mail (SMTP) servers.
   * ButtonAction (tm) listbox selections beyond the "REGISTER" action (many
     cool actions).
   * Thread caching (super-fast threading) facility (use/examine/query).
   * DB row caching (internal speedup when drawing the list screens).
   * "Max lines" and "Max NGs" in "NG Prefs" (these are the primary
     "spam killer" functions).
   * Killfile facility (add-to/kill-using/edit).
   * Article font selection.
   * The Uni-Index option (i.e.  turning off "Multi-Index") in "Global
     Poll Prefs".
   * Cancel/Defer/Resume ability of long operations (e.g. Re/Index).
   * Progress dialogs ("% done") for long operations.
   * Low-memory poll auto-abort (if configured in "Global Poll Prefs").
   * Text-entry for in-body find.  Find always works if some of the
     body's text is selected (that's the text-to-find) but registered
     and trial users are presented a screen to enter the text-to-find
     when nothing is selected.  In other words Yanoff- and post-trial
     users have only "Find Again", not "Find".
   * Global Find.
   * Sound options in addition to "MID del" in "Sound Prefs".
   * Tap options in addition to "Un/Lock".
   * Control of history facility (i.e.  the "MID" options in "Global
     Poll Prefs").
   * Options other than "All" (e.g.  "Some" and "None") for "Confirm
     Dels" in "Misc Prefs".
   * Goto/ReadTo prev/next article in subject/thread.
   * Goto prev/next unread/marked/locked article.
   * Auto-repeat of some buttons.
   * Reverse/Rot13/De-MIME(Quoted Printable '=##' tags) text conversions.
   * Multi/selected/MIME/Leading-white/Trailing-white/ article text
     trimming (manual and automatic).
   * Rearranging the order of the newsgroups (polling order and viewing order).
   * Sent messages saved to "Sent" box (if configured in "Global Poll Prefs").
   * The "Skip Srv" and "Skip NG" buttons during online polling.
   * Repopulate history feature (not super useful).
   * Index specific article (mostly for debugging).
   * Editing the scoring DB (does *anybody* really use scoring?).
   * Scrollbar placement options in addition to "Right" (not use/fully
     functional; no reason to use it yet).

Q:  What features are available only to registered Yanoff+ users?

A: There are 3 as follows:
   * Auto-completing article bodies.  If the user has downloaded only
     headers and is online; when he enters an article, the body of the
     article is automatically retrieved (functionality is available to
     all users as a manual action).
   * Soft button ButtonActions (tm) on the newsgroup list screen.  There are
     several configurable soft buttons on the bottom margin of each
     screens (in addition to the hard buttons which are available for
     all users).
   * Global Find launch.  Global Find will work but only registered
     users are allowed to launch into a found message by tapping on it
     in the Global Find results window.

Q:  Is New Yanoff compatible with GPL Yanoff?

A:  Because of a necessary change to the NewsArts.pdb data structure,
    for now, no.  However at some point in the near future, we will
    submit a code change to GPL Yanoff so that it can understand both
    versions of the articles and then backwards compatibility will be
    restored.  Of course, there are many things that New Yanoff does
    that GPL Yanoff doesn't know about and therefore can't understand.
    Besides this change, though, most everything is saved in the same
    spot and in the same format for both versions so none of the new
    things should break anything in GPL Yanoff.  The only exception is
    some of the trivial preference data (mostly booleans) moved around a
    little bit so all the preference settings should be verified when
    moving back and forth.  Most likely we will submit those changes to
    GPL Yanoff soon, too.  We wish to be as compatible with GPL Yanoff
    as possible and to live in cross-compatible harmony!

Q:  Is New Yanoff compatible with the Java Conduit?

A:  There is 100% backwards compatibility with the Java Conduit but
    there is 1 "gotcha" which you need to beware (the "Conduit" Poll
    Pref mentioned elsewhere herein)!  Other than this, the Java Conduit
    works exactly as it does with GPL Yanoff.  Obviously, though, it is
    ignorant of the new preferences and the features they control so it
    cannot respond to the added functionality the way the online polling
    code does.  If interest and demand are high, we plan to update the
    Java Conduit so that it comprehends and obeys the new preferences.

Q: Does New Yanoff do SSL?
Q: Does New Yanoff do POP3?
Q: Does New Yanoff support color?
Q: Does New Yanoff support Hi-Res?
Q: Does New Yanoff support JogDial?
Q: Does New Yanoff support OS versions older than v3.5?
Q: Will using New Yanoff make me popular with the opposite sex?
Q: Does New Yanoff support non-standard screens sizes/dimensions?

A:  No.  Maybe it will in a future release; let us know what missing
    features are important to you.  If this missing function is
    essential, we would be happy to move your feature request to the top
    of our to-do list and implement it immediately if you would care to
    pay our standard consulting rate.  Otherwise, please register and
    contribute to the success of the current release as this will ensure
    future updates will continue to be produced.  In any case, please do
    send us your ideas for improvements and we'll do our best to
    eventually implement the ones which make good sense.

Q:  I can't get the "Network Svc" preference to do anything on "Server Prefs".
Q:  The "Type" setting doesn't work right on "Server Prefs".
Q:  I have defined additional SMTP servers but they aren't working.

A:  Those features don't fully work yet; they are for future releases.  The
    "Network Svc" preference does nothing at all.  The "Type" preference is
    functional but the original restrictions still apply: There is only 1
    SMTP (mail) server and it must be at position 0 (i.e. the first server
    defined).  Any number of NNTP (news) servers can be defined at any
    position other than 0.  Any number of additional SMTP (mail) servers may
    be defined but only the one at position 0 is used.  At some point in a
    future release, we intend to support additional mail servers and also
    the association of a particular server to a particular network "Service"
    (as defined on the "Network" OS preferences).  

Q:  Whenever I send an email or post an article, the message body is missing.
Q:  Whenever I send an email or post an article, the message body is garbage.

A:  You must be using the Java Conduit.  If so, you need to checkmark the
    "Conduit" box in the "Poll Prefs".  If interest and demand are high, we
    plan to update the Java Conduit so this won't be necessary.

Q: What does ButtonAction (tm) <action> do?

A: Here are what most (not a complete list) of the actions do:
   * Native function: whatever the button normally does (i.e. phone launches
     phonebook app).
   * Nothing: If you need an explanation for this, delete  Yanoff right now.
   * Enter: Go to the next (deeper) screen (or article).
   * Exit: fall back 1 level to the previous screen (or to launcher if on
     the main newsgroup list screen).
   * Goto top/first: Go to top/first entry in table.
   * Goto bottom/last: See previous action and "Nothing".
   * Goto last<->first: If not at last entry in table, goto last entry;
     otherwise goto first entry.
   * Goto first<->last: If not at first entry in table, goto first entry;
     otherwise goto last entry.
   * Line up/down: Move the cursor up/down 1 entry. 
   * Page up/down: Move the cursor up/down 1 page of entries.
   * Line/Page up/down+Wrap: move cursor; if at one end of the table, wrap
     around to other end.
   * Line/Page up/down+Jump: move cursor; if at one end of the table, jump
     to prev/next table.
   * Goto prev/next un\read/un\locked/un\marked/ article: See "Nothing".
   * GoTo/ReadTo prev/next subject/thread: If ReadTo, mark articles along
     the way as "read".
   * Purge MIDs: Purge the history database using default/last days-to-keep
     setting.
   * Purge MIDs w/?: Purge the history database after prompting user for
     (and storing) days-to-keep.
   * Purge articles [w/?]: See previous 2 actions plus the "Nothing" action.
   * [Any action(s)] +Jump/Jmp: Do the action(s) and then jump to the next
     table (if possible).
   * [Any action(s)] + Jump/JmpTop/#1: Do the action(s) and then jump to the
     top entry in the next table.
   * [Any action(s)] + Jump/Jmp1st!Read/1!Rd: Do the action(s) and then jump
     to the first unread message in the next newsgroup.

Q:  I used to be able to include the article's text to which I was
    replying or following-up.  Now when I "Re" or "F'Up", that text is
    missing.  How can I get New Yanoff to copy the article to my response?

A:  Now it is required that you highlight the text you wish to include.
    Just select the portion you want before you hit the button and the
    selected text will be used to seed your response.

Q:  What are the various lines on the Header screen and why are they
    abbreviated?

A:  Screen space is a scarce resource for PDAs.  By contracting each header
    label to a single character (or 2) each we are able to fit the vast
    majority of dates, email addresses, newsgroup names and Message-IDs on
    a single line.  Many times, this allows the header to fit on 1 screen.
    The abbreviations and the order in which they will appear are:
    * "S:" is "Subject:"
    * "F:" is "From:"
    * "D:" is "Date:"
    * "N:" is "Newsgroups:"
    * "T:" is "To:"
    * "M:" is "Message-ID:"
    * "R2:" is "Reply-To:"
    * "F2:" is "Followup-To:"
    * "R:" is "References:"
    * "MIME-Version:" is not abbreviated
    * "CT:" is "Content-Type:"
    * "CTE:" is "Content-Transfer-Encoding:"

    All other incoming headers are discarded by Yanoff (although there will
    be options to save them in a future release).  If the "D:" appears as
    "d:", this indicates that it is the creation date of a user-created
    message which has not yet been transmitted.  Once it is sent, the "d:"
    becomes a "D:" and the date displayed is the transfer date of the
    message.  This, of course, is only true if the "Sent box" Poll
    Preference is used (otherwise messages are deleted immediately
    following transmission).  

Q:  What does the text on the Title bar at the top of the Header screen mean?

A:  The first number is the position of the message's reference in the
    newsgroup database.  The second number is the newsgroup database
    entry's unique ID.  The third number is the position of the message
    in the article database.  The fourth number is the article database
    entry's unique ID.  The fifth/last number is the message's multi-index
    count.  The symbol before the last number is either a vertical bar
    (|) which indicates the message is stored in the "new" format or a
    colon (:) which indicates it is stored in the "old" format.  The old
    database format used a single position for the "Reply-To:" and
    "Followup-To:" headers.  If the message was user-created, it was to
    be interpreted as "Reply-To:"; if the message was a polled article,
    it was to be interpreted as "Followup-To:".  This is a very poor
    compromise because it is valid for any message to have both headers
    so one is always lost.  The new format adds an extra field so each
    header has it's own space and both can exist at the same time.

Q:  What do the various symbols mean in the left-most column of the article
    list screen?

A:  There are 3 flags.  The left flag is a centered dot indicating the
    message is marked.  The middle flag has a top and bottom indicator.
    The top indicator is an apostrophe (') indicating the message is
    locked.  The bottom indicator is a period (.) indicating either that
    the message has been read (body displayed to the screen) if it is a
    polled article or that the message has been sent if it is
    user-created.  These appear as an exclamation point (!) if both are
    true.  The right flag is either a vertical bar (|) indicating a
    "genuine" message body exists or a centered dot indicating it does not.

Q:  Some articles don't have regular bodies but instead have text like
    "1.3582"; what is that?

A:  Whenever a head is downloaded (articles are downloaded in 2 parts;
    first the head, then the body), a context is saved in the article's
    body.  The first number (the "1" in this case) indicates which
    newsgroup in the article's "Newsgroup:" header is the one where this
    header was downloaded.  The second number is the article's
    position/number within that newsgroup (local to a specific newsgroup
    on a specific server; different servers and even different newsgroups
    will have different numbers for the same Message-ID).  This
    information is important because it allows us an additional option to
    specify the article's body.  It can be specified either by Message-ID
    (global context) or by group+number (server-local context).
    Sometimes one will work but not the other; we need to be able to try
    both ways.  Note that articles of this type do not have the "body
    present" flag indicator described above because this text is not a
    "genuine" body.

Q:  I get a lot of "423" and "430" errors when I poll online; what are they
    and what do they mean?

A:  Yanoff will only attempt to obtain articles within the range the
    server has specified is valid.  However it is very common for servers
    to be missing some articles within this range (they were canceled,
    corrupted, whatever).  Those 2 errors are returned when an article
    (header or body) is requested but no longer exists.  Most of the time,
    the header does exist but the body does not.  The problem with MOST
    newsreaders is that they don't report the "missing" articles and so
    the user has no idea the situation exists.  New Yanoff allows the user
    to see the header even if the body cannot be retrieved.  This follows
    our "power to the user" paradigm in that the user is notified of
    articles which he has missed which empowers him to attempt retrieval
    via other means (i.e. Google, etc.).  With the header, one has both a
    reasonable idea as to the content of the missing body and also the
    unique Message-ID to assist in outside retrieval.

Q:  Some articles in a newsgroup show they are read (or marked or
    locked) even though I haven't gone into that newsgroup since the
    last poll; how can this be?

A:  Remember that each single article may exist in more than 1 newsgroup.
    If you are subscribed to 2 newsgroups in an article's header, and the
    article is indexed into both newsgroups, then when it is read (or
    marked or locked) in the first newsgroup, all changes will be
    reflected when you run across it in the other newsgroup because
    both newsgroups point to the same (shared) article in the article
    database.  Most users find this an annoying waste of time so they
    will want to uncheck the "Multi Index" Poll Preference.  When
    unchecked, crossposted articles will only be indexed into 1
    subscribed newsgroup: whichever one is highest on the main screen.
    This option is also more efficient for RAM because articles which are
    "deleted" in one newsgroup but which are indexed in another newsgroup
    merely have the newsgroup reference deleted, not the article itself.
    An article will not be deleted from the article database until its
    multi-index count is 0 (i.e. until all newsgroup references are
    deleted).  Unchecking "Multi Index" ensures that every article's
    multi-index count is no more than 1 and when a reference to an
    article is deleted, the article is always deleted at that same time.

Q:  I want to view the rest of a truncated article; how can I?
Q:  I need to see a post's .sig but I trimmed it; can I get it back?

A:  If you poll online (sorry conduit users), go into the truncated article
    and do a "Re/Poll body" from under the "Mgmt" menu.  When bodies are
    manually repolled, no automatic trimming or truncating is done and the
    maximum article size (32K) is used (overriding the "Max" setting in
    "NG Prefs").

Q:  I have "Trim MIME" set in my "Global Poll Preferences" yet I sometimes
    still see the Quoted-Printable "=##" tags in articles.  I can decoded
    them with the "Decode '=##' tags" command so why is it not
    automatically being done?

A:  There are plenty of natural occurrences of strings which appear to be
    encodings which are not (e.g. cgi parameters such as in eBay URLs).
    So while it is true that "Trim MIME" will both trim non-text MIME
    stanzas and decode the quoted-printables, the latter is only done if
    it can be conclusively determined an encoding is present.  This is
    done by checking for the "Content-Transfer-Encoding: quoted-printable"
    header.  If this header is not found, no automatic decoding is done.
    The manual operation assumes you know what you are doing and will
    happily mangle eBay URLs or anything else that fits the format of "=##".

Q:  I repolled my article body but it just beeped and nothing changed;
    what's up with that?

A:  Remember the explanation about the 2 ways to specify an article
    earlier? The failure to repoll the article is almost certainly
    because your news server requires the group+number specification and
    does not respond properly to the MID specification.  The problem is
    that when the article was first polled, the incoming body permanently
    destroyed the (temporary) encoded group+number which was stored there.
    You are out of luck.  

Q: After a while MemoPad has stopped syncing.
Q: After a while MemoPad has begun to crash during HotSync.
Q: After a while MemoPad has begun to report errors during HotSync.

A:  If you have a value greater than 4KB for "Memo max" on "Logging Prefs"
    then you will have problems with MemoPad HotSyncing once any of new
    Yanoff's logfiles grows to greater than 4KB.  In general, this setting
    should be left as 4KB for this reason.

Q:  My PDA got reset and my license key is no longer working; will you
    please resend my original license key?

A:  YES!  Just send an email from the Contacts Page with your name and
    HotSync ID and we will verify your registration in our records and
    resend the key to you.  This may take a couple of days.  If you are
    using PocketPurchase, though, this can never happen because once you
    reinstall the yanoff.prc and PocketPurchase.prc, the conduit restores
    the key automatically.

Q:  I changed my HotSync ID, will you please send me another license key?

A:  At this time, it is our policy that when you pay for a license key,
    that is exactly what you are doing.  If you need a different license
    key (because you changed your HotSync ID or for any other reason),
    then you must pay for another (different) one.  We are sure everyone
    can appreciate the reason for this policy as it protects us from
    people "sharing" their license keys when the sharee should be paying
    for his own.  Because license keys are based on the HotSync ID of
    your device and because users may change their HotSync ID, we will
    soon provide instructions on our web page for how to change your
    HotSync ID back to what it used to be which will re-validate your
    original, existing license key.

Q:  Which ButtonActions (tm) should I use and why?

A:  Most of us use these (top-to-bottom as listed in the ButtonAction
    (tm) screen):

    * NG list (main) screen
        Re/Index articles
        Enter NG
        PageUp+Wrap
        PageDown+Wrap
        LineUp+Wrap
        LineDown+Wrap
        Purge old MIDs
        Poll
        Goto first<->last

    * Article list (NG) screen
        Exit+DelOnUpRd
        Enter article
        PgUp+Jump
        PgDn+Jump
        LnUp+DelRead+Jmp
        LnDown+DelRead+Jmp
        Goto 1st unread
        Goto first<->last
        Delete all unlocked

    * Article screen
        Exit
        Next article
        Kill (read) subject (Occasionally: Decode "=##" tags)
        Un/Lock
        PgUp+Next art
        PgDn+Next art
        Followup
        Reply

    Most are obvious but a few are subtle.  On the NG screen, I do not
    have DelRead on the PgUp/Dn buttons because I like to be able to
    "Jump" to another NG either with or without deleting.  Since PgUp/Dn
    is the same as LnUp/Dn when near the end of a list (i.e. first/last
    page), I use the "Pg" buttons to Jump without deleting or the "Ln"
    buttons to jump with deleting.  I like to be able to initiate a
    manual DelRead at the press of a button (or 2); that's why I have
    Exit+DelOnUpRd.  When reading an article I'll decide I'm done for
    now so I push Calendar twice (Exit, Exit+DelOnUpRd) which is a quick
    way to initiate a DelOnUpRd for the NG.  Then, if I want to go back
    to reading, I push Phone twice (Enter, Enter) and I'm back to
    reading where I left off and I never had to look at the PDA or tap
    the screen.  I always read from top-to-bottom and never skip any
    articles so I have "Bip After" set for "Art del".  This is to
    exploit the fact that most Del (and all DelOnUp) functions begin low
    and work their way back/up: when it stops beeping, I cancel the
    operation (no need to let it search for unlocked or read articles
    which I know aren't there).  If I didn't read the way I do, though,
    this wouldn't be a useful shortcut.

Q:  Does New Yanoff have the Good Net-Keeping Seal of Approval?

A:  Sadly, not yet.  We are proud to report that of the many scores of
    violations that GPL Yanoff had, only a tiny handful remain.  We
    intend to have full compliancy and official approval by the first
    major maintenance release.

Q:  What does the "Toggle Debug" menu item do?
Q:  What does the checkbox next to the "Debug" heading on "Logging Prefs"
    do?

A:  Those do the same thing and should only be accessible in test versions
    of the software.  They set an internal flag which dumps out extra
    programmer-interpretable-only data used by us while we are programming.
    It allows us to dump out internal values of various things to track
    down bugs.
