I have not been able to pin this down as "fact". I have noticed that RMS Express does not always put modem to level 3 after a connect. With a P3 only session, after the initial connect, you will get the disconnect from the remote station, since it only allows P3 sessions. I do not have this issue with Airmail and the same SCS Modem. Modem is USB version with latest firmware.

In the channel selection window, add sort feature for RMS stations by distance, similar to how sort may now be done by call sign, bearing, grid square. This would allow users to quickly find the closest RMS stations to make connections to.

The Icom M710 supports PTT. I believe its technically called CAT PTT.

Protocols, Clients, and Message (BBS) Systems sometimes are confused.

WINMOR is a protocol. A formal and documented way to send bits error free (after ARQ) to another station. It is like Pactor, Packet etc. There are other protocols too but unless they are ARQ they can't insure error free transmission. The WINMOR TNC is a program that runs on a PC that with a sound card implements the WINMOR Protocol.

A radio client or server program is one that uses a TNC (or a virtual TNC as the WINMOR TNC above) to implement a radio client or server. Examples are AirMail, RMS Express, Paclink, RMS WINMOR and several others. You can think of them as the radio equivalent to your home email program. Clients initiate the connection. Servers accept the connection.

A BBS system is what ties all the Radio Servers and Clients (and sometimes internet) together for the purpose of exchanging messages etc. Examples are WINLINK, BPQ32, PSKMail and others. These have software (hidden to the user) that stores, organizes and forwards messages and user accounts.

So as you can see WINMOR (as a protocol) could be used in many applications just as Pactor. In fact the motivation for WINMOR was to provide a lower cost of entry to HF ARQ modes. Its faster than P1 and can approach P2/P3 but is much lower in cost. WINMOR could be used in any Client or Server program that is willing to write a driver for it (like a TNC driver) and there are several now available.

(Edited version of a message posted by Rick Muething, KN6KB)

It seems that the statistics does not tell the truth.
It looks like the whole bunch of traffic is done on the highest level allowed on that channel, even if the truth is that traffic have been done in Pactor 1.

I'm getting an error message when RMS Express is tring to receive a Peer to Peer Packet message...
*** Link Error - Received data stream not correct format...
I'm able to send messages just fine. 
I'm using an AEA PK-232mbx

Current WL2K server station software package official names are:

RMS Packet
RMS Pactor
RMS WINMOR

And, there is also: RMS Linux Gateway, and you have several BBS packages running the WINMOR TNC package, from third parties.

RMS HF was at one time an official WL2K software package name, but has been deprecated.

General usage:

The general term "RMS" for 'Radio Mail Server' has replaced "PMBO" for 'Packet (or Pactor) Mail Box Operator'.

"RMS Gateway" also refers to any RMS station connected to one or more CMS (Common Mail Server) in the "cloud". Or, it can refer to an HSMM or D-Star gateway connecting to any CMS using the Telnet protocol.

"RMS HF Stations" refers to all stations in the high frequency bands, which may run either RMS Pactor or RMS WINMOR or RMS Linux Gateway software. They use either Pactor I, II, III, or WINMOR protocols. This is seen on status reports and maps on the website.

"RMS Packet Stations" always refers to VHF or UHF stations running RMS Packet or RMS Linux Gateway software. They always use Packet Radio (AX.25) protocol.

And you have "RMS Express", which is not an RMS at all, but client software. Don't ask.

Winlink "nodes" don't exist - never did -- just "gateways".

(portions borrowed from a post by Lor, W3QA)

I have frustrated Ham buddies in Africa and South America who cannot effectively use RMS Express with Winmor, since there are no Winmor RMS's within easy, reliable reach.
Please allow Hams in these areas to set up RMS's, even if they are somewhat substandard. Substandard is better than NOTHING.

Needed is a driver added to RMS Express and Paclink to support the new SCS Dragon (DR-7800) modem with P4.   There are an increased number of RMS Pactor stations with the Dragon as their node, yet the client software doesn't support this new modem yet.

Create an .kml file of RMS HF/Packet Sysops that can be downloaded from the FTP server and opened and saved into Google Earth and updated every few minutes, days, or hours rather than have to browse the Winlink website to locate sysops. Example would be .kml file of IRLP nodes from IRLP.net  website.