Hi! Rick,

On 21 Jan 18 16:37, you wrote to me:

 PQ>> Be warned: it currently doesn't do JAM netmail areas, or at
 PQ>> least, not in a way that you might expect.  Yes, I found out the
 PQ>> hard way.  ;-)

 RC> Is the issue just JAM ** NETMAIL ** areas or ALL JAM msgbases systems
 RC> including echo?

I only use Netmgr on netmail areas.  The /SVN/xmsgapi/doc notes that...

                            ---===[ * * * ]===---
This is the first release of XMSGAPI.  Some new bugs may be introduced.
SDM support has not been tested thoroughly.

This library is based on smapi-2.2, however the code has been cleaned
up, modified, and ported to a number of additional compilers.  Note that
due to unresolved bugs and/or incomplete code in api_jam.c, JAM support
is currently not compiled into the library by default.  Also, it is not
yet possible to generate a DLL of the XMSGAPI.  These issues may be
corrected in a future release.
                            ---===[ * * * ]===---

I can tell you after having used it, that netmgr will carry out copy/move
actions to a JAM nemail 'definition' but treats it as a directory path.  I.e.,
the resultant netmails end up at the bottom of a tree rooted by an exclamation
point, from where the executable was called from.

 RC> I've always used MSG for Netmail, and some other things verus x
 RC> message base be it JAM or Hudson, which I used in the past.

For over 24 years I have used MSG but have also used what's called a
'secondary' area for my own personal mail, freeing the primary area for junk
that has to happen with mailer & tosser software (e.g. areafix, PINGs, etc). 
It has usually been another MSG area but in recent years I have developed a
preference for a JAM area, which can be presented with the JamNNTPd server (of
course).

Cheers,
Paul.

... Lymph (v.), to walk with a lisp.
--- GoldED+/LNX 1.1.5-b20110213