Frequently Asked Questions

Yes. See http://groups.yahoo.com/group/Airmail2000.

A108 The license class only limits the frequencies on which you can transmit, not whether you can use Winlink email. You can hold a Technician license, be limited to VHF and above frequencies and use WL2K. But you would be limited to 50-100 mile distances. For most work at sea, with practical 100-7,000 mile ranges, you will need a General or Amateur Extra class amateur radio license (in the USA), which provide privileges on the radio bands that support distant communications.

A675 New e-mail addresses are automatically added to your Whitelist when the CMS receives the message from you, independent of which user program you are using. The list can also be changed by:
A) If you are connected to the Winlink 2000 web page:
1) WebMail….User Settings
2) Add or Delete specific addresses and/or domains to either the Whitelist or the Blacklist.
3) Hit the Save button

B) Create a new message [the following is an example] to the CMS with the following format (not case sensitive):

To: System
Subject: Whitelist
LIST will return a list of all Whitelist and Blacklist entries for the user.

ACCEPT: jblow@somewhere.com will allow messages from jblow@somewhere.com to be accepted. You may send multiple lines, each containing one e-mail address.

Reject: jblow@somewhere.com will reject any messages from jblow@somewhere.com. You may send multiple lines, each containing one e-mail address.

Delete: jblow@somewhere.com will remove jblow@somewhere.com from the user's Whitelist. You may send multiple lines, each containing one e-mail address.

ACCEPT: arrl.net will allow all messages from xxxxxx@arrl.net to be accepted

REJECT: Verizon.com will reject all messages from xxxxxx@verizon.com

IMPORTANT NOTE: Domain Entries without the "@" will be treated as "domain names" only. For example if "Accept: sailmail.com" were entered, then ANY message from that "domain name" (sailmail.com) would be accepted.

Send the message

A955 First please try and remember we have been doing this WL2K project about 9 years so we have a pretty good idea of what works and what doesn’t. RMS is not an experiment; it is the natural evolution of what we have learned and optimized over the past 9 years. The RMS concept grew out our experience with PMBOs, central servers and from the successful Telpac effort for packet--hundreds of which have been installed and operated for over 7 years.

The only time an RMS captures or buffers any message will be if it has lost internet connectivity and it has the optional RMS Relay module installed and enabled. (This Module is still being written but the design is functionally complete). RMS relay does have the optional capability to bridge mission critical prioritized messages from local packet users via HF Pactor in the case of no internet connectivity. This allows emergency long haul traffic out of any locally isolated (orphaned) RMS that has Pactor capability. Normally this bridging function would only be enabled during emergency situations due to the limited available bandwidth on HF compared to VHF/UHF. Even if HF bridging does not take place, when connectivity returns buffered messages will flow out to the CMSs and waiting messages for the RMS users will flow in to be available on an RF connection.

A951 The first thing you have to remember about server loading is the bandwidth of a radio channel (packet or pactor) is VERY slow compared to internet bandwidth. Each of the CMSs have at least one T1 connection (1.5 megabits/sec). Most have multiple. Each T1 line would handle roughly 200 simultaneous 9600 baud packet channels running at max throughput. Or something like 1000 Pactor channels. In practice these servers are set up to allow 1000 simultaneous connections but we have rarely seen them go above 20 or so. There are currently four CMSs with distributed DNS servers world wide. All RMS sites now cache actual dotted CMS IP addresses so they don’t require any DNS service. All RMSs automatically rotate through all available CMSs if a connection can’t be made to the initial CMS. If a CMS ever becomes saturated it simply will reject new connections and slow down the throughput to those connected to it. However based on the typical speeds of radio links most users would never even see this throttling.

Each CMS has a firewall and a mechanism of capturing connect attempts and these along with some additional mechanisms can be used to block most Denial of service types of attacks. It might be worth noting that we have had a Central server mechanism used in WL2K for over 9 years and have never had a successful Denial of service attack. Since going to redundant CMSs about 4 years ago we have had virtually 100% availability of the system…even during major disasters such as Katrina, The Tsunami, etc., and hardware/internet failures at a CMS.

A7080 Yes, it can be used with the Paclink MP software and Airmail using setups for Telnet connections with PMBOs, RMS/RMS Relay and CMS. Another way is to use Paclink MP as a POP/SMTP server in a high-speed D-Star LAN. D-Star users with DD mode can connect directly to the Paclink MP server using their e-mail client software with tactical e-mail addresses. With good design of the local high-speed network, extremely efficient and fast radio e-mail service can be expected.

A2545 That depends on your definition of "robot" and "automatic". PMBO and RMS stations have their transceivers and TNC's controlled by the station computer. They are usually "unattended" by their Control Operator. Transmissions will begin ONLY after the receiver detects being called by another station. Loss of a satisfactory receive signal will time out the transmitter and disconnect with the other station.

Possible modes and frequencies are enabled by software, abiding to goverment regulations. The list of scanned frequencies may change, depending on time-of-day. Get the PMBO RMS Frequency List from ZS5S for the latest information (see Q2560). All PMBO and RMS stations can be remotely re-configured by the Winlink 2000 System Administrator, if an internet connection is available.

A950 Certainly!

ARRL (ARES/RACES) – General FAQ concerning Winlink 2000
http://www.laarrl.org/ARESFAQ1.htm

Chester County (PA) ARES/RACES – W3EOC Radio Email Exercises
http://www.w3eoc.org/RadioEmail/#top

Harris County (Texas) ARES/RACES – WL2K Resource Page
http://harriscountyares.org/resources/digital/dist_14_dig.htm

AE5V – WL2K Implementation
http://home.earthlink.net/~bscottmd/wl2k_implement.htm

K4SET - The Winlink 2000 Network, Amateur Radio, and How It Could Help Your Work
http://radioministries.org/winlink.htm

N0IA – Tuning Packet Parameters for Best Performance
http://home.earthlink.net/~k7bfl/TuningVHFPacket.pdf

N7CW, KI5DR, VE3GFW – A Winlink 2000 Training Session
http://www.joppe.net/dares/Winlink%202000%20Training%20Session.ppt

SV2AGW – A discussion about packet TNC’s built into radios
http://home.earthlink.net/~k7bfl/TascoModem.pdf

Icom – D Star Specifications
http://www.aesham.com/display_pages/d-star.pdf

ARRL Lab (KC1SX) – Comparative Performance of Packet Radios at 9600 baud
http://home.earthlink.net/~k7bfl/RadioCompare.pdf

The “Pactor Primer” and “RF Interference”; two excellent articles written by Jim
Corenman, KE6RK; author of the AirMail software:
http://www.airmail2000.com/docs.htm

AirMail Installation and Setup Instructions – W5IFQ
http://www.ke5exx.com/pdf/AirMail_HOWTO.pdf

AirMail Setup Instructions – San Diego ARES
http://www.sdgares.net/2%20AirMailSetup%20R3.pdf

WL2K Information Resource pages:
http://www.activeham.com/winlink/wiki/index.php?title=Main_Page

Florida Amateur Digital Communication Association
http://www.fadca.org/

Each Wednesday night on the W8FSM EchoLink server at 8:00 PM EST, (7 PM Central,
etc.) there is a group that meets to discuss WL2K and related topics.

A930 Yes! Several things will be happening, which will improve the system. See the paper "Winlink 2000 Roadmap”, written by two members of the WL2K Development Team.

A920

http://groups.yahoo.com/group/wl2kemcomm/
Purpose of the group is to share ideas, uses, methods and procedures of utilizing Winlink 2000 for Disaster Recovery/Emergency Preparedness; and to include any other organization/agency that deploys or is considering deploying Winlink 2000 for emergency communications.

http://groups.yahoo.com/group/airmail2000/
A general purpose list for things like: Beginner questions on setting up, tips on using and connecting to the WinLink2000 system, frequency updates, WinLink 2000 station status and new station additions are all welcome on this list.

http://groups.yahoo.com/group/mars_wl2k/
This Yahoo group is for the use of Army, Air Force and Navy/Marine Corps MARS (Military Affiliate Radio System) members interested in the establishment and use of Winlink 2000 network technology. It is not an official forum. Messages posted here, unless otherwise noted, are the opinions of the poster. Do not discuss matters such as specific frequencies or channel designators on this Group. This group is for technical assistance to WL2K users and sysops, NOT for arguments of whether we should/shouldn't run Winlink.

There are also several limited-membership discussion groups for the purpose of coordinating sysop functions and beta testing software in development.

A900 Winlink 2000 (WL2K) is (and always has been) all volunteer. No one is compensated for their contributions of time which now [2007] totals well over 20 man-years. We try to offset at least some of the costs of running servers, registering internet addresses and domains, licensing software etc with donations.

In 2006 we set up a not-for-profit public service corporation to handle the finances and contributions from the distributions of CDs and also as a vehicle to accept donations of equipment and services (e.g. retired commercial servers etc). This corporation is called the Amateur Radio Safety Foundation Inc. (ARSFI) see http://www.arsfi.org/ The directors of the ARSFI are the founders and developers of WL2K and no director receives any compensation. We are in the process of obtaining Public Charity status 501(c )3 for this corporation but that is a time consuming process and it is not guaranteed we will be granted this status. The ARSFI is the mechanism we use to pay for the expenses of WL2K and to purchase what licenses, hardware and new development tools and software are required. It is also a mechanism to provide training for Emcomm groups and distribute information about WL2K and Amateur Radio Emergency services in general.

Interested parties or those wishing to contribute to the operation of WL2K can do so in one of a few ways. These mechanisms can all be reached via the ARSFI web site above.

• Join the ARSFI ($10/year). Your membership gives you a vote into how the
  organization is run and what it does. The contribution goes to the ARSFI and some of that is used to support Winlink 2000.

• Make a cash donation through the ARSFI. Both Pay Pal and Secure Credit Card
  mechanism are available on the ARSFI.org web site. We request that personal donations be limited to $100.

• Purchase one of the CDs which we make available throughout the year to various
  boater, RV, and EMComm groups. These have convenient up-to-date software and other
  useful information. A nominal $15 donation is suggested to cover duplicating and mailing costs. If you would like a CD configured to target a particular group or service please contact one of the directors and provide us information on what your target audience is.

• Make a donation of equipment or services to the ARSFI. This can be in the form of retired but otherwise useable servers, radio equipment, software, facilities or services (e.g. legal, accounting, engineering, programming or documentation help) To make a donation of equipment of services please contact one of the directors of ARSFI.
• Donations of cash or check are also appreciated and should be sent to:

  ARSF Inc.
  c/o Rick Muething, KN6KB
  6143 Anchor Lane
  Rockledge, Florida USA 32955

  Make checks payable to ARSF Inc. or Amateur Radio Safety Foundation Inc.

Your support of Winlink and the ARSFI is much appreciated.

Rick Muething, KN6KB
Director, Treasurer Amateur Radio Safety Foundation
Winlink 2000 Development Team

A690 Yes, if you will be giving a Winlink demonstration, it would be good to turn the Whitelist OFF, prior to the demo. Many email users, including some that you may send messages to during the demo, do not have identical email addresses for their incoming and outgoing email. A Reply from one of these persons will bounce from your Whitelist.

Another important case would be if you are participating in an EmComm exercise. You never know which e-mail addresses will be sending you mail. You do not want them to bounce if they aren't in your whitelist.

If you haven't used your Winlink address for more than 400 days (or have never used it), but suddenly want to use it and receive incoming email from any email address, send your first message to SYSTEM with a Subject of OPTIONS and a message body of Whitelist: OFF. See Q670.

A670
A) If you are an AirMail user: Options Message (created with AirMail) Update and Send.

B) If you are a Paclink MP user, and you are connected to the internet:
1) After starting the Paclink MP software: File…Site Properties…
2) Put a “check” in the “Use Whitelist” and “Whitelist Notice” boxes if you want these turned On.
3) Select the “Update” box.

C) If you are a Paclink MP user, and you are not connected to the internet; or you are a Paclink AGW user:
1) Create a new message to the CMS in the following format (not case sensitive):
To: System
Subject: Options
Whitelist: On [or Off, True, False, No, Yes]
Whitelist Notice: On [or Off, True, False, No, Yes]
2) Send the message

D) If you are connected to the Winlink 2000 web page:
1) WebMail….User Settings
2) Change and Save your new Settings.

A630 Messages incoming to WL2K users are filtered, using high level methods, by the Central Message Server (CMS). Winlink 2000 uses the information from SPAMCOP. It also requires a reverse DNS lookup. Each server IP address must return a PTR-record that matches the HELO or ELHO command received from that server and it must have an A-record that matches the host name shown in the HELO or ELHO command. If such a record exists, then it has entry to the Whitelist system.

In addition, individual WL2K users have the ability to use a “Whitelist”. “Whitelist” is the default method for new users. Your choice may be changed at any time. If you decide to not use your Whitelist, you will get a lot of Spam. It is recommended that all users turn their Whitelist “ON”.

As of September 2007 WL2K is no longer using a Spam Filter with a “Threshold”. Ignore references to a Spam Threshold in the AirMail software.

A620 Yes, go to the Webmail page and login. Then …User Profile.

A610 This can be done via the Winlink WebMail page after you log in. The limit is in bytes.

The Attachments limit can also be changed by sending an “Options” message to the
Common Message Servers with the AirMail program. See Q670. Go to: Message Index….Window…Winlink-2000….Options Message

[Note: The Attachment Limit filter is not used by a PMBO station when downloading to a WL2K user directly (without using a Telpac Winlink Gateway) via the Telnet method.]

A600 The TNC’s made by SCS contain a LOT of technology. Discounts are available from Farallon Electronics for qualified users. See:
http://home.earthlink.net/%7Ek7bfl/SCSDiscount.pdf

A590 Yes, Winlink still has value, even in this very unlikely scenario. In an event as you described, each PMBO or RMS equipped with RMS Relay stores messages received from users before sending them to the Common Message Servers. Therefore, each PMBO or RMS would act as a “Hub” for Winlink users who can access that station by radio. If N3ABC and K3KK can both access RMS K4CJX via radio, then they can exchange emails by using their normal Winlink email addresses. If it is a PMBO they are connecting to, they cannot send or receive an internet e-mail from someone like mother@earthlink.net. When a path to the CMS is restored all stored messages will flow to and from the PMBO stations.

However, given the more likely scenario that the internet is gone only across a large region--even a whole continent--, and if it is an RMS with RMS Relay they are connecting to, their messages are forwarded by radio to another RMS that does have connectivity to the CMS. Local messages, as well as those bound for internet destinations outside the WL2K system, are delivered.

PMBO stations are being phased out in favor of RMS.

A560 That particular transaction is not allowed by the Winlink 2000 system.

A500 Attributes of Winlink User Software

A480 Third-party traffic is any traffic transmitted over the Amateur bands that is either from or to a non-amateur. In the Western Hemisphere (with a few exceptions) there is no restriction on third-party traffic being passed over amateur radio. Many countries outside of the Western Hemisphere also now permit third-party traffic over amateur radio.

Messages between amateurs even if they originate or are delivered over Internet are not considered third-party traffic. Third-party traffic only deals with that portion which is transmitted over the radio spectrum. Since there is no limitation on third-party traffic over Internet itself, messages passed between WL2K participating stations, or a participating station and the Internet are not
restricted. Only when the message involves a non-amateur and is passed over a radio
link is the issue a concern. For example: if a message originates in the U.K. on Internet but is delivered to a U.S. amateur over the radio from a U.S.-based station no third-party rule is broken even though the U.K. does not allow third-party traffic over amateur channels. Likewise, a message originating over the radio from a U.S. amateur and passed to a U.S. station is legal even if it is addressed to the Internet address of a nonamateur in the U.K.

Users must make themselves familiar with these third-party rules for the country in which they are operating as well as linking with if they are exchanging messages with nonamateurs. See the country list for countries known to permit third-party traffic for U.S. stations and their reciprocals.

A460 Yes, smaller messages are downloaded before larger messages.

A440 1. WL2K web page….WebMail (Attachments are not supported)
http://www.winlink.org/webmail [Note: You must have accessed the WL2K system by
radio or “Telnet” at least once after November 13, 2006 to enable this method of
accessing your mail. Your default password for WebMail is your callsign.

2. Internet connection….Telnet…AirMail or Paclink AGW or Paclink MP

3. Radio….packet…..AirMail or Paclink AGW or Paclink MP

4. Radio… packet….Keyboard Access (Attachments are not supported)

5. Radio…pactor…AirMail or Paclink MP

6. Radio…D-Star…Paclink AGW or Paclink MP

A400 All except .exe and .zip. Attachments are not available when accessing with the Winlink WebMail page or when using the Keyboard method.

A380 The WL2K outbound e-mail (SMTP) client will try and send your outbound mail directly (no relays) to the end recipient 10 times over a period of 5 hours. If it still fails (in this case because it appears the recipient's ISP is not accepting or blocking the connection) it gives up and sends a failure notice to the originator.

Most of the time these failures are due to:
(a) Improperly listed public MX record for the destination domain
(b) Some form of spam or other filtering mechanism used by the ISP
(c) The server is off line or otherwise down. If multiple servers for a
domain are available (as listed in the MX records) all are tried.

A370 Yes. From the WL2K web page go to …Reports …..CMS Status
http://www.winlink.org/CMSStatus

A360 Message size maximum, including Attachments: 120000 bytes (compressed)
[If a message exceeds the absolute compressed size limit, a service message will be sent to the sender advising that the message has not been accepted. There is no message number limit or overall byte limit.]

Attachment name size maximum: 50 characters (including extension)

Message Routing (retention period) from the CMS to a PMBO, for a particular Winlink
user address: 90 days

Life of an Unread message: 21 days

Registration period for a Winlink user: 400 days since last access via radio or Telnet

Life of a Tactical Email Address: 400 days since last use

Life of an email address in your Whitelist: 400 days since you last sent a message to that address.

Tactical address name length: Current Tactical addresses are limited to 12 characters total (including any "-") preceding the "@winlink.org". See Q7030.

User daily time limit for HF users is defaulted to 30 minutes. The PMBO operator may change that default, or customize it for different modes (pactor 1, pactor 2, pactor 3) and different users. If you have specific larger needs, email your request to the PMBO or RMS operator (pmbocallsign@winlink.org). There are no User daily time limits associated with a RMS packet gateway or Telnet.

A340 If you have access to the web, go to the WL2K web page….Maps….User Positions…
http://www.winlink.org/userPositions

Click on the dot of the approximate position of the station you are looking for.

Click again on “View Position Reports” to see all of the recent reports from that station.

If you do not have access to the web, and are using AirMail, send a “Position Request” message via Message Index….Window….Winlink-2000….Position Request.

A320 It either be embedded in the body of the message, or attached to the message.
AirMail can be used to send and receive NTS radiograms via the NTSD system, by
accessing the NTSD “Area Hub” pactor stations. See the instructions by AE5V at:
http://home.earthlink.net/~bscottmd/airmail_ntsd.htm Also see Q6100.

A300 No, it is not compatible. The Winlink 2000 system is an off-spring of Winlink 2.9 (Winlink Classic). AirMail is similar to Winlink 2.9, but has MANY differences. A major difference is the message routing process. Winlink 2000 does not support “H-routing”. Winlink 2000 is centered on the SMTP email standard.

Winlink 2.9 was written by Victor D. Poor, W5SMM, who has continued to write software
for Winlink 2000. You can read more about the history of Winlink at:
http://www.winlink.org/node/1

AirMail can be used to send and receive NTS radiograms via the NTSD system, by
accessing the NTSD “Area Hub” pactor stations. See the instructions by AE5V at:
http://home.earthlink.net/~bscottmd/airmail_ntsd.htm

A280 What you're seeing is a BBS forwarding exchange where the two connected systems propose transmission of messages they have available for the other user, and list which messages they wish to receive of those proposed.

For documentation of the basic F6FBB BBS proposal exchange, see:
http://www.f6fbb.org/protocole.html

For a documentation on the B2F (FC proposal) enhancements implemented by WL2K software, see: http://www.winlink.org/B2F

WL2K uses the standard FBB protocol with a B2 extension. B2 is simply a specific mechanism for encapsulating a message which allows adding attachments, addressing multiple recipients, and mixing radio and email (internet) recipients. Otherwise it is virtually identical to the FBB B1 protocol and it uses the exact same LZW compression algorithm as FBB B1. The B2 protocol (http://www.winlink.org/B2F) was developed in 1999 by the Winlink Development Team to be an efficient mechanism to move text and binary attachments using the FBB forwarding protocol. The FBB protocol and B2 is more efficient than the standard internet SMTP protocol in RF applications such as Packet or Pactor.

A260 The on-air content looks that way because it is a compressed binary format called “B2F.” This format is available to anyone and is not proprietary. The compressed data is not considered encryption for the purposes of concealing content or illegal for radio amateurs. Additional information about B2F is at:
http://www.winlink.org/B2F

Data transferred through Winlink 2000 is not considered to be secure. Data transferred through Winlink 2000 using the Keyboard method is not compressed, therefore it is readable by monitoring operators.

A240 Tests done early in the development process indicated that the B2F format we use
resulted in higher throughput than using the TCP protocol, which has much unnecessary
overhead for radio use.

On the other hand, for all other links that do not involve HF and VHF/UHF radio, we use TCP/IP. The system's building blocks nicely intercommunicate over Ethernet. These design decisions are responsible for the great synergy Winlink 2000 gets from the best of both radio and TCP/IP links.

A220 Yes, but since Windows operating systems are used by the majority of actual and potential users, we feel our limited man-power resources should be used to improve the present Windows based software.

There is a version of the Telpac Gateway software that runs under Linux and
several have used this to add Packet gateways to WL2K...again this is a server function and not user access. See Q9100.

Several starts on Linux user software have been abandoned by their third party authors.

You can use AirMail which runs on a Mac using the Windows emulation, such as Soft
Windows or Parallels. This may be a bit sluggish, depending on the speed of your computer, but will work. AirMail also runs fine on a Mac under Virtual-PC. The only wrinkle has to do with USB/serial adapters not AirMail, either map the serial port from the Mac side OR enable VPC's USB support and install the Windows USB drivers. But don't do both, that ties the serial ports into knots.

You can also run AirMail under WINE on Linux.

If you mean as a WL2K PMBO or RMS station the answer is no; those are only Windows .NET programs running on Win 2000 or Win XP. Perhaps someday there will be a .NET runtime for the Mac which would make things a lot more transferable.

As a last resort you can access WL2K via any dumb terminal program on packet in
keyboard mode. This is not recommended...it is error prone, does not allow attachments, etc; but it will work in an emergency. HF access via keyboard is very restricted due to its inherent inefficiency.

The Winlink Development Team is open to other user programs that operate using other operating systems. If you are or know a good Mac programmer we will encourage him and help him if he would like to write a Native Mac client. If you have such programming expertise and want to donate your time, please contact the
System Administrator, K4CJX.

A200 Principles include:
1. A message system compatible with SMTP e-mail.

2. Enable messages to be transferred to the destination party in a VERY accurate
manner, within a short time duration (several minutes).

3. Enable use of the available internet infrastructure, if available.

4. Encourage use of VHF/UHF/SHF radio spectrum, if an internet path is not available.

5. Enable EFFICIENT use of HF radio spectrum, if VHF/UHF is not available or suitable to the path. Use as small as possible “RF Footprint”. See http://home.earthlink.net/~k7bfl/RF_Footprints.pdf

A180 The message is immediately deleted from the PMBO you are connected to. The PMBO notifies the CMS that the message has been delivered. The cancelling of messages at other PMBOs in your Routing Table may take up to 10 minutes depending on loading and PMBO polling cycles. If you connect to another PMBO before that time it will try and PROPOSE the message again but AirMail or Paclink AGW should always reject it as having already been received. This is not that uncommon.

If you connect to another PMBO using a different computer or installation of Paclink AGW or AirMail or do a completely clean re-install of those programs then of course the duplicate blocking feature is lost since there is no longer any record of MIDs (Winlink message identifier) received. In other words, if you connect and retrieve a message from your favorite PMBO “A” with AirMail and then connect to favorite PMBO “B” with Paclink AGW there will be no duplicate message blocking possible since the two programs are not communicating the MIDs received between themselves.

In the case of RMS stations used for contact, a delivered message is marked delivered immediately at the CMS and will not be proposed again, no matter which RMS you connect to.

A170 Due to the much slower transfer speeds of most common radio paths (compared to dial-up, etc.) it is better if messages are kept as small as practical, while still accomplishing the communications objectives of both users. Following are approximate air times needed to transfer a 4K message (after compression) for several modes of operation, under ideal conditions:

Packet (1200) direct ->2 minutes
Packet (1200) 1 Node ->2.5 minutes
Packet (9600) direct ->1 minute
Pactor 1 ->30 minutes
Pactor 2 ->10 minutes
Pactor 3 ->1 minute
Telnet (D-Star, HSMM, Internet) ->seconds

Messages containing “emoticons” and “backgrounds” contain embedded image files and should be avoided, if possible. These images can be stripped from your incoming messages by setting your account Attachment Limit to 0. However all other “useful”
Attachments will be stripped also!

Winlink 2000 (except when using Keyboard or WebMail Access) will process Attachments of many file types. Some file types comes with significant “overhead”. This overhead can be reduced by changing the file to a txt, rtf, or csv file, if appropriate. Image files should be as small as practical!

A160 The CMS consists of four different computer systems in four widely-separated physical locations. In 2008 these were San Diego, Washington DC, Halifax, and Perth. They are backing each other up on a continuous basis. If a failure occurs at one location, PMBO’s and RMS stations will be transparently re-directed to one of the other locations.

A150 No guarantees, but if one of your intended recipients is NOT a Winlink user (has a non-Winlink domain in the address), you will get a service message from the CMS telling you of that problem. Assuming that you have addressed the message correctly, there are still a multitude of reasons why the intended person might not get the message; or got it and has not read it. The Winlink system is good, but not infallible; ditto for the rest of the internet infrastructure.

Some e-mail servers’ spam filters are very aggressive. Some may reject email
originating or from a server located in specific countries. It is the responsibility of the message originator to verify that the message path is working – ALL THE WAY to the recipient of the message. This is no different than using any e-mail service.

A145 Yes, if fact you can have multiple Winlink addresses, such as K3ABC@winlink.org and K3ABC-3@winlink.org. The system should treat those two call signs as separate users. There are some areas of confusion that need to be discussed.

1) If you are registered in the system as callsign and then connect as callsign-ssid, if THAT –ssid registered in the system as a separate user it will treat you as a separate user. There are some specific reasons for this having to do with PMBO’s etc.

2) If you connect with a –ssid and THAT –ssid is NOT registered in the system it treats you as the BASE call sign …no ssid.

3) If you connect through a packet network or some switches (packet nodes) that ALTER your –ssid then this can pose a problem. Paclink MP (and its predecessor Paclink AGW) has an extended feature added (signified by the N in the SID) that tells the target PMBO/RMS what your real –ssid is even if the packet network altered it in the connecting process.

If you want your Paclink MP software to really operate as K3ABC and not as K3ABC-3, then simply change the call sign in the site properties. You will also have to change any accounts on your e-mail client (Outlook Express, Thunderbird, Outlook etc.) to match the new base call sign. See Q3560

A140 It may be because you have not used that PMBO is the past 90 days. If this is the case, just connect again in a few minutes. The message should be there waiting for you.

If you are using AirMail (HF) or Telnet (Internet Access) to a PMBO, you should also note on your connection log how many minutes have elapsed since the PMBO has connected to one of the Common Message Servers. If that duration is greater than 15 minutes, the PMBO may be having a problem communicating with the CMS; use another PMBO.

Also, the mail may be waiting for you at the PMBO, but the PMBO sees you as
Usercallsign-15, caused by your going through a packet node (using either Airmail or a terminal (keyboarding) program). See Q145. If that is the case, and you are using
Airmail, you might try connecting to the packet node as Usercallsign-1. Somehow, the WL2K database has you with two email accounts. You can request the System Administrator to delete Usercallsign-15@winlink.org, and your “node problem” will go away!

If you connect to an RMS station, the database you are connected to is the CMS. If there is no message for you, there really is no message for you!

A135 90 days after you last used that PMBO. Routes are not required if you contact an RMS station.

A130 Winlink 2000 has changed it's topology in 2008. It formerly used dynamic routing where a routing table was maintained for each user, by the Common Message Servers (CMS). It contained a list of all of the PMBO stations that you assessed in the past 90 days. A copy of all e-mail for yourcall@winlink.org was sent to each of the PMBO’s in your routing table, shortly after the message arrives at the CMS. After you successfully downloaded a particular message, that message was deleted at each PMBO in your routing table. The message was marked delivered at the CMS.

With RMS Pactor and RMS packet software in place of PMBOs, there is no routing required. When a contact with an RMS station occurs, a real-time connection with the CMS database occurs, where all messages are stored. No matter which station you contact, your messages are instantly and always available. No more waiting for a PMBO to sync its database with the CMS.

A125 In February 2008 there were exactly 19,503 registered stations with unique callsigns... and growing!

A120 “Registration” is automatically done when you connect to the Winlink system via radio or via a telnet session. Webmail browser access does NOT automatically register a new user. Neither does registration on this web site. Your User information will remain in the database for 400 days after your last interaction with the Common Message Server via radio or telnet. User radio privileges are spot-checked by volunteer Winlink station operators. Use of the Webmail browser access does not “update” the 400 day limit; this must be done by connecting by radio to a PMBO or RMS station or connecting directly to the CMS via telnet.

A115 No. Its original purpose was to provide a very long range radio path for radio amateurs who did not have access to “land-line” communications needed to send and receive e-mail messages. Subsequent uses have been oriented toward providing partial backup of e-mail services for ARES/RACES and MARS “served agencies” during a local commercial communications outage or communications overload. Transfer speeds and available bandwidth do not allow for complete replacement of internet e-mail services. This may change with increased use of D-Star, satellite, and other high-speed RF paths to Winlink 2000 stations where the internet is working.

A107 “RMS” is a Radio Message Server. It is a direct radio port or gateway to a CMS site. Early in 2008 software relating to PMBO and Telpac will be replaced by software relating to RMS. PMBO software will be replaced by RMS Pactor software. Telpac software will be replaced by RMS Packet software. A benefit to WL2K users of these changes is a reduction in the “latency” of messages, as they move between the user and the Common Message Server (CMS). See Q4010.

This FAQ file will be updated as the new software is rolled out. See Q930.

A104 PMBO means "Public Mailbox." This is a radio station which functions as a port to the rest of the Winlink system. A PMBO can be an amateur radio station, or operate on government or military frequencies, such as MARS stations. It is a “bridge” between user radio stations and the email part of the internet, using HF Pactor and/or VHF/UHF packet radio with a telnet server for connections over the internet or by high-speed data radios, like HSMM (High-Speed Multimedia) or D-Star. Winlink PMBO software is depricated in 2008 in favor of RMS Packet and RMS Pactor software with sysop utilities.

A102 Not yet! But there is a short “Winlink made Simple” publication available at:
http://home.earthlink.net/~k7bfl/tfctools.html

Bud Thompson, (N0IA) has written an online course “WL2K For Dummies” for those who
have not yet installed the various client (end-user) programs for using the Winlink 2000 system. See: http://www.winlink.org/node/23

This Group is specifically designed for those who have not yet installed the various client (end-user) programs for using the Winlink 2000 system. There is no TNC, data terminal, or radio required for this on-line course. When there is sufficient interest, this group may expand to details of wiring computer-TNC-radio for using the Winlink 2000 client software components over the air.

The first thing to do is go to the "FILES" section of this group, and look for E-Mail
Assignments. Start working on the assignments at your own pace, and use the facilities of this Yahoo Reflector group to obtain assistance.

No, but see Q220

http://www.winlink.org:8080/Help_Info/Center%20Frequency.htm

Steve, k4cjx

A2650 The throughput of pactor 2 is about 3x the throughput of pactor 1. The throughput of pactor 3 is about 30x the throughput of pactor 1. See Q170. If a PMBO or RMS operator can keep his station relatively “busy”, accepting only pactor 2 or 3 connects, he will probably choose to go the “no pactor 1” route. By doing that, his station is providing the “most data transfer” for the “most users”. Each PMBO or RMS station owner/operator independently makes a decision regarding the use of pactor 1. PMBO and RMS stations have given special considerations to pactor 1 users during unique events. Email a PMBO or RMS sysop with your special requests. They have the software ability to accept pactor 1 Connects on specific bands, and/or during specific times during the day.

A2600 Yes, like most hardware and software, revisions occur.

• Frequency List. See Q2560 and Q2570. This should be done every 1-2 months, only
  if you are using the HF part of WL2K

• AirMail Catalog. You should probably update this 2-3 times each year. See Q1580
  and Q1600.

• If you are using a TNC, update the Firmware. If you have a SCS TNC, it is updated
  about every year. Check the SCS web page for news about a new release. The latest is
  version 3.7. Your version number will show on the Terminal Window when you start up.
  The updating process is a shore chore, using the internet
  a) download from the SCS web page
  b) start AirMail
  c) Tools....Update PTC Firmware
  d) AirMail software. The latest version is 3.3.081. Available from www.winlink.org ....

A2580 See the AirMail Help files; or ---:

1. Make sure that the new list is in the “Program Files…AirMail….Import” folder.
2. Open AirMail. The new list should be in your In Box. Select it.
3. Go to “Tools….Make Frequency List”.
4. Scroll through the list, verify that it is the “new” list.
5. Click the "Update" button, the program will go into a frenzy of formatting.
6. Click "Save" the frequency list.

A2570 See the AirMail Help files; or you can order a Help file from the Catalog:
[from the AirMail Message Index Window…..Window….Catalogs…WL2K…Global…WL2K
Help...”How to Download and Import a new PMBO Frequency List”]

To download a new Frequency List for inclusion in AirMail, follow the instructions below:

1. Go to Inbox and delete any previous Frequency list message (subject) INQUIRY:LIST.
2. Go to Menu items: "Windows>Catalog"
3. Double Click on folders: "WL2K>Global>ZS5S_Bulls" and then check "PMBO" (on right
   screen.)

4. Check into a PMBO to send the request.
5. Check back into any PMBO to obtain a new frequency list, subject: "ZS5S Directory of Winlink-2000 PMBOs (INQUIRY:LIST)"
6. Go to inbox and highlight the Frequency List, "SERVICE@WL2K INQUIRY:LIST"
7. Go to menu item "Tools>Make Frequency List." The list will appear on the screen.
8. Click "Update" and then "Save" the frequency list [see Q2580].

A2560 Subscribe to a free monthly email updated list from ZS5S. See:
http://users.iafrica.com/z/zs/zs5s/bulls/PMBO.TXT

A2550 AirMail has a built-in frequency list of all PMBO Stations. The scanned frequencies of a particular PMBO or RMS show up in the HF Terminal Window, when selected. Be sure to set your radio dial to the “Dial Frequency” shown at the bottom of the Terminal Window. The frequency shown above is (depending on setup) the center Frequency.

A2540 It doesn't. PMBO and RMS stations are "listeners" only, scanning several frequencies on several bands. They do not send out any beacon messages. They just sit and scan and scan and scan, waiting for someone to call them. You need to call the PMBO or RMS station to initiate a connection.

A2535 To fix the scrolling problem:

1. Maximize the Terminal window.
2. "Restore Down" the Terminal window (the box next to the Close Box)
3. Scroll down to the bottom of the Terminal window.

The Terminal window should then scroll up automatically with new information.

A2530 If you are “almost done” with the transfers, hang in there and wait for the finish.

If you will have a significant estimated time left to finish the transfer, do a Hard Disconnect (hit the Button twice). Pick another PMBO, another frequency for the same PMBO, modify your equipment for a better signal, or wait until propagation conditions improve.

There are many PMBO’s and frequency bands available; something usually works
better…now.

When you make the next connection, AirMail tells the PMBO how much of the message(s)
have already been transferred, and the process will continue from where it left off on the previous connection.

A2520 Several items might improve the performance:

See the AirMail Help files
• Change to a difference frequency band for that PMBO
• Try a connection at a different time of day.
• Use another PMBO. It does not matter. They are all transparent to the system.

A2510 Several items could affect the performance:

See the AirMail Help files.
• Are you on the correct EXACT center (not dial) frequency? The main frequency chart is listed as center frequency. In the lower right hand corner of the Terminal screen on the AirMail Terminal form, you will find the actual dial frequency. The dial frequency varies with modem type and other factors, while the center frequency is always the same, regardless of mode of operation or sideband used.
• Over modulation of the transmit audio? You should barely see any ALC with full
  output to your transceiver. This can be set up in AirMail. Read the AirMail help
  files. Reduce the transmit audio gain level. Less is Better.

• Maybe you need a better antenna?
• Maybe you have an “RF or Audio” problem due to RF feedback into your system. Use ferrite chokes and/or less power output.
• Better earth ground connection or counterpoise.
• If you are using a battery for power, is the battery voltage too low? In this case maybe a lower power output setting may work better.
• Turn off all processors, compressors and filters on both the receiver and
  transmitter.

• Is your receive bandwidth filter wide enough for the mode used? Pactor 3 needs
  2.4 KHz.; Pactor 2 needs 0.7 KHz; Pactor 1 needs 0.6 KHz. Some radios do not perform well with both the microphone and the TNC connected simultaneously to the radio. Disconnect the microphone.

A2500

• Use the data from the AirMail propagation module (View…Propagation) to give you
  guidance on which stations and frequencies are better than others, at the time of day you want to connect.

• Do NOT try to connect on a frequency that is in use!
• Use PMBO stations which are close to you.
• Use lower frequencies (80 and 40 meters) if possible. 30 meters is a very useable “forgotten” band.
• Use Pactor 3 or Pactor 2 if you have them. It saves everyone time, and makes more PMBO time available for other users.
• Use one of the PMBO stations that are not quite so “busy” as others. You can get a feel for this by going to the WL2K web page and looking at a real-time map of PMBO or RMS stations. Look for “Show 24-hour Station Activity”.

A2050 The early PK232mbx models with firmware rev. of 7.0 and 7.1 have code in them that affects how binary files are transferred. The Winlink Development Team found that the B2F protocol is the most effective way to transfer files. However with older code in the firmware, the PK232 cannot use this protocol so it switches to the FBB protocol, which is slower.

The whole point is that you get a slower throughput with the older firmware. In revision 7.2 the code has been changed to accommodate B2F, but do not expect to see a major increase in throughput because it is still only Pactor 1. To see a major increase in throughput you need to go to Pactor 2 or 3 (with a SCS tnc). The PK232mbx will not support use of the GetFAX function.

A1700 Create an address-book entry called "Group" or whatever, enter one to-address and as many cc-addresses as you want, one per line. To copy/paste; use the right-click menu (or the usual windows shortcut ctrl-V to paste).

A1660 Save the message, then select View menu, Message-header, and re-open the message. You will see the complete headers with word-wrap, easy to check or copy.

A1630 No; however keep in mind that most folks use some sort of spam-filter on the receiving end, and most spam-filters are sensitive to messages with a bazillion "to" or "cc" addresses- lots of cc's is something often used by spam. So keeping the number of recipients down to a reasonable number per message will increase the chances of getting it through.

A1600 Every time there is a small change, deletion or addition to the Winlink Catalog displayed in the AirMail menu "Window>Catalog," the list should be updated to take advantage of the changes and additions.

The Update is relatively short, while obtaining a new List is a bit longer. Either way, once the change is received, AirMail automatically updates your existing Catalog list. The proper method for updating or obtaining a new list is as follows:

1. Go to the AirMail menu item "Window>Catalog."

2. On the left, expand the directory tree to show "catalog>WL2K"
3. Under Catalog, expand "WL2K' further to show all the PMBO call signs.
4. Pick a PMBO that you wish to use and Click on that PMBO callsign.
5. On the right hand side you will see both "LIST" and "UPDATE."
6. Check "UPDATE" or "LIST." If you choose "UPDATE," all changes & additions will be shown, BUT the deletions will NOT be taken away. However, if you choose "list," then you will have a fresh new shorter list. Unless otherwise instructed, an update will be adequate.
7. When you have checked either "UPDATE" or "LIST," find the same PMBO you placed
   the request under and send that PMBO the request.

8. Wait, and then at another time, check back into any PMBO and retrieve the information you requested. NOTE: Once the update or new list has been received, it will automatically update your AirMail Catalog List. If it does not, then YOU did something incorrectly.
   

A1580 AirMail's "Catalog" window can be used to request weather bulletins and other documents from the Winlink-2000 system for hams, and also from the Saildocs server operated by the Sailmail association but also accessible via email by Winlink users. The AirMail catalog is found under the Window menu, Catalog selection. The catalog window is divided into two panels- on the left is a "tree" showing various folders, similar to AirMail's message-index tree or Windows Explorer. These folders represent categories of documents which can be requested.

The catalog entries are organized first into sections for "WL2K" and "Saildocs". Clicking the little "+" will expand a selection, clicking a "-" will collapse it (just like Windows Explorer). The right and left-arrow keys can also be used to expand and collapse folders.

Under "WL2K" are a folder for "global" bulletins, plus a folder for each station which has been seen, containing that stations local bulletins as well as the "update" listings. Under the "global" folder are folders for each bulletin category, click on these (or use the arrow keys) to open that folder and show the contents in the list on the right side. Bulletins or documents are requested by checking the corresponding check-box, see Winlink-2000 Bulletins for more information.

Of particular interest and use for WL2K users are the WL2K_Help and WL2K_Users folders,. These folders contain messages that can request specific Help files and specific “current” information regarding Winlink users.

Under "Saildocs" is a series of category-folders. The "Grib files" category is a special folder which brings up a grib-request window with a world map for requesting grib weather-data files. See "Grib Weather Files" for more information on requesting grib data.

Saildocs also includes a large number of text weather-bulletin documents which can be requested. These are organized into folders under "Saildocs" for the different ocean regions. Some areas have sub-folders to further divide the selection for easy browsing.

Also, many bulletins are listed under more than one heading, for example Atlantic hurricane bulletins are listed under both "Atlantic" and "Tropical". See "Saildocs Catalog" for more information on requesting documents from Saildocs.

A1500 Sometimes a very large message (with or without Attachments) gets sent to a WL2K user and attempting to retrieve it results in very long air time and the inability to download other messages. There are several methods available to fix this problem:

Method 1

1. Set your program to the "Keyboard" mode. (AirMail is normally in the "Handshake" mode.
2. After connecting to a PMBO station (directly or through a Telpac Gateway), type LM. This will give you a listing of the messages waiting for you, complete with Message ID, size, and origination.
3. Find the number of the offending message. Copy and Paste its Message number into a line to be sent back to the PMBO as:
   K xxxxxxxxxxxxx [xxxxxxxxxxxxx is the Message ID]

4. The message will then be Killed (Deleted). You will get a confirmation of that back from the PMBO.
5. Repeat (2) to confirm that the message is no longer in the queue for you.
6. Disconnect (Disconnect Button or type BYE)
7. Connect again, in the normal Handshake mode. The Pipe will be unplugged!
8. Send a note back to the offending Sender.....

Method 1a
The KM command will work also, but ALL of your messages will be deleted.

Method 2
Download the message via Telnet (Internet Access) or the Winlink web page, if an internet connection is available.

Method 3 (not recommended)
In the AirMail Message Index Window, go to Tools…Options…Settings. Change either “Defer Incoming larger than… or
Reject Incoming larger than… to a small number larger than 0.

Method 4
Request a PMBO sysop or the System Administrator to delete the message.

A1090 First, a comment on upgrading to Windows Vista: If your new computer came with Windows Vista then that's great. If you are contemplating upgrading your computer to Windows Vista then make sure that is what you want to do. Windows-XP is robust and reliable; if yours is not then something has been compromised. And upgrading a compromised system results in a compromised system with fancy new drapes. But if you have a fast processor and at least a gigabyte of memory, then go for it.

The next question is an upgrade-installation or a clean install. Generally we prefer a clean install, but only if the computer manufacturer supports Win-Vista for your computer, and provides driver updates. For example, upgrading our three-year-old IBM Thinkpad was a piece of cake-- do a clean install for Win-Vista, go to the Lenovo website support/downloads page and install the system-update file for Windows Vista. We were impressed, but your mileage will vary.

There are a couple of issues when running Airmail under Windows Vista, mostly related to new Vista security features. The short answer is that Airmail works fine under Win-Vista when run as an administrator. A new security feature of Windows Vista is "User Account Control" (UAC). Remember, if you can do anything useful with your computer, it is not sufficiently secure. "User Account Control" is a watchdog service that does two things: warns you if you are trying to do something useful, e.g. run a program. And, if a program attempts to write into protected areas (e.g. the "program files" folder), a virtual copy of the file or folder is created instead for that user. The result, for Airmail, is severe schizophrenia, and release-notes that just keep reappearing. Here's how to fix it:

First, install Airmail as usual: Download the file from the website and save it in a "downloads" folder, then open that folder and open the downloaded file. Airmail will go through the install steps, and Windows may show a "not installed properly" warning when finished-- click "Yes this installed normally" and continue.

Once installed, before running Airmail, right-click the Airmail desktop icon and select "properties", click the "Compatibility" tab, and check "Run as administrator". This allows Airmail to write into its own folders (otherwise prohibited). For Airmail versions prior to 3.3.090 also check "Run this program in compatibility mode" and select Windows-XP SP2 (this will enable com-port descriptions).

You will continue to get warnings from UAC about an "unknown program" each time you
start Airmail, and you may want to disable UAC. You can disable UAC in Control panel:

open "User Accounts" and turn "User Account Control" off.

Help file: Vista does not include the program to display the traditional help files, "Winhlp32.exe". This may be available for download, alternately it can be copied from Windows-XP C:\Windows folder. To do this you will first need to set the permissions for the C:\Windows folder to allow Administrators full access, and to do this you will need to first take ownership (right-click the Windows folder, select properties, then Security tab, Advanced button, Owner tab, Edit button). Then copy the complete (277KB) Winhlp32.exe from Win-XP over the 9KB "stub" Winhlp32.exe on Win-Vista.

The propagation program installs OK and runs properly under Airmail. It will not likely run correctly under its own desktop icon without some fiddling similar to the above.

Upcoming versions of Airmail will move the user-folders into Win-Vista's user-space, while maintaining the basic hardware settings in a common file. This will avoid issues with UAC as well as permitting separate "personalities" if desired. The Help file will also be converted to HTML format. The goal is for Airmail to run smoothly under Vista's highest security settings but this will take some effort.

[from Jim Corenman, author of AirMail; February 1, 2007]

A1080 [from WA9OTP] A handy way to transport the AirMail program between computers is in a small USB flash drive. These drives are very inexpensive now, compact, and durable. When AirMail 'installs' it copies programs to your computer, it does not add complex links (DLLs).

According to Jim Corenman, KE6RK, who wrote AirMail:
"The only caveat is that if AirMail has never been installed on the machine, then a library file might be missing- vcl50.bpl which normally lives in the Windows/System32 folder. The fix is to copy that file into the Airmail folder on the USB-drive. 73, Jim"

I have tried this, and included the vcl50.bpl file as Jim suggests, and found that AirMail will boot and run from the flash USB drive on any other machine. Of course, you may have to adjust the comm ports for your new situation.

A1060 No, sorry. Windows CE (for mobile devices) is completely different from the Windows 95/98/ME or Windows NT/2000/XP families.

A1040 The original Earthmate was connected via a serial port, used a Rockwell chipset and a non-standard interface at 9600 baud. Airmail can communicate with that device if you check the "Earthmate" box.

The 2003-vintage USB Travelmate was different, and worked in NMEA mode if you told
the DeLorme installer that you wanted to use the GPS with other applications also. If you made that selection when DeLorme was installed, then special drivers were installed that created a virtual com-port that would speak standard NMEA. In this mode the "Earthmate" box should NOT be checked, it is behaving as a standard NMEA GPS.

Apparently the same is true of the LT-20, except that the special NMEA-drivers are not part of the DeLorme installer. You can download the “DeLorme Serial Emulation Driver for USB Earthmate® GPS and Earthmate® GPS LT-20 Receiver” from
http://www.delorme.com/support/search.aspx
After the new driver is installed, start AirMail and configure the proper COM port for the LT-20 in the Message Index…..Window….Position Report…Data Input….Setup window.

Check the “GPS/NMEA Port Enabled” box, and select the proper COM port. Do NOT
check the “Earthmate” box. Also, be sure the “Data Input…Enabled” box is checked.

A1020 No; just copy the new file into your main AirMail Folder. Double click on the new file. Installation will begin. All of your previous settings and frequency lists will be preserved.

A1010 Some serial/usb converters work ok; some don’t. Good results have been reported for those brands of Radio Shack, Manhatten, Keyspan, Edgeport, IBM and Startech. Many folks are having difficulties with those sold by Belkin, but that may have changed.

The Keyspan and IBM devices have been tested and listed on the Microsoft Hardware
Compatibility List (HCL). Since only “listed” hardware has been tested and found to be substantially compliant, buying unlisted equipment is a gamble at best.

You can find which converters are on the HCL by checking at:
http://www.microsoft.com/whdc/hcl/default.mspx

Things like COM ports floating (or, being able to be assigned and reserved unchanged by the driver) are symptoms of software that can't get on the approval list because someone wrote drivers that do not meet minimum standards.

A1005 The “Telnet Client” module is used to communicate via the Telnet protocol, using an internet connection. The “setup” for this is via the Tools…Options…Modules…Telnet Client…Setup window. This module is the easiest to set up, and is suggested as an initial means to get AirMail working. See Q4000.

The “Terminal” or “HF Terminal” module is used to communicate via HF, using pactor 1, 2, or 3. The “setup” for this is via the Tools…Options…Settings window. See Q2000.

The “VHF Packet Client” module is used to communicate via packet radio. The “setup” for this is via the Tools…Options….Modules….VHF Packet Client…Setup window. See
Q3000.

A1000 Windows 95 is the “minimum” operating system, although a more modern Windows
operating system is always encouraged.

A410 Go to Tools….Options….Settings. Make sure that “B2F” is selected for the BBS
Forwarding Protocol.

A190 Each message "alive" within a PMBO and the Common Message Server must have a
unique message number, referred to as a "MID". You should not "reset" the starting
message number when re-installing or updating the AirMail software.

However, if you are using multiple computers (like your laptop and your desktop) with the same callsign, keep the message numbers significantly different from each other in the two computers.

A3680 See A1700

A3660 See A1660

A3640 See A1630

A3600

1. Stop AirMail
2. Navigate to C:\Program Files\Airmail
3. Open airmail.ini with Notepad.
4. Scroll down until you see a bunch of CONNECT TO entries.
5. Delete at will.
6. Renumber the list, in sequence.

A3580 Tactical email accounts are not useable with the AirMail program.

A3560 AirMail versions prior to 3.3.048 will not support dash-number calls (as a Winlink user). 3.3.048 will support dash-number calls as independent user callsigns (not to be confused with packet dash-number SSID's). Note that for Pactor use, 6-char callsigns can only use a single-digit suffix (i.e. 6 letters plus a dash plus 2 digits won't work for Pactor, but will work for packet).

All recent versions of AirMail will support the use of packet SSID numbers for packet
connection purposes only. See Q140.

A3550 Yes, AirMail will work when going through another packet station acting as a digipeater. The procedure:

1. Select the Handshake mode.
2. Enter into the "Connect To:" box…gatewaycall via digicall

Messages will now flow automatically (but SLOW....). Use MAXFRAME=1

A3530 AirMail does not need any special licenses. You got that error message because you tried to connect to a node “alias” name, instead of the node’s call sign.

Q3520 The messages also may need to be Posted to the FIRST station (WR7VHF-4) you
connected to in the connection process.

A3500 Where are two pages on the WL2K web site that will give you the information. The first one is a map of Telpac Winlink Gateways that have reported to the Common Message Server within the past 24 hours. It is a link off of the “Maps” tab. The link is:
http://www.winlink.org/RMSPacketPositions

Select the station symbol on the map or select the station call in the list to obtain detailed information about the station’s location, frequency, etc. A “RMS Packet Station Status” tells you the time since a station last checked with the Common Message Server. It is from the “Reports” tab:
http://www.winlink.org/RMSpacketStatus

Many PMBO Stations also provide connections for packet users, but they are not listed as a “Telpac Winlink Gateway”. See the frequency list from ZS5S:
http://users.iafrica.com/z/zs/zs5s/bulls/PMBO.TXT

Many PMBO Stations also provide connections for packet users, but they are not listed as a “Telpac Winlink Gateway”. From the Winlink web page go to “Winlink Stations” to get the info regarding a particular PMBO station. Another option is you can request of list of nearby Telpac Winlink Gateway stations from the AirMail “Catalog”.

1. To use this you must have a recent update of the WL2K catalog. You can do a list update or a full list in AirMail. Once the list is updated you will find a new bulletin called WL2K_PACKET under the category WL2K_USERS.
2. To use the new WL2K_PACKET function you will need to have posted a position report. This can be done with AirMail using the position report menu. If you have posted a report recently (within 30 days) and have not moved substantially that will be sufficient.
3. Now request bulletin WL2K_PACKET using AirMail’s catalog feature. This will put the request out and it should be available for pickup in a few minutes. The request will have all active Telpac Winlink Gateways and all RMS Packet servers within 100 miles (statute miles) of your posted position. The call sign, Grid Square, distance and bearing, Frequency and Baud rate will be in the list (example follows this message). Only those Telpac Winlink Gateways or RMS Packet stations that have reported in the last 30 days will be considered in the list….normally stations report about once per hour or so.

A3080 AirMail turns off several functions that it does not need, such as Monitor. To restore those functions you need to reset the TNC. Here is how:

1. Close the Packet Client window
2. Go to Tools….Dumb Terminal and wait for the cmd prompt to come up.
3. Type RESET and hit the Enter key. You will see many boxes with zeros and eight’s in them.
4. Now send the auto baud command and you will see the TNC sign on message. Now close the dumb terminal and close AirMail.
5. Open your terminal program. You may need to enter you call and the date/time again. Your terminal program should be ready to go.

A3050 Most likely the problem is that your serial port was configured using your Terminal Program and those settings do not match those required by AirMail. There are a few different approaches to fixing this problem. Here is one.

1. In you Terminal Programs, such as WinPack, go to the cmd mode and type RESET. This will reset you TNC.
2. Change the setting in your program to the following: Baud rate=9600, Start bit=8
   parity=none, Stop bit=1 and Handshake=Hardware. Save the changes.

3. Now send the Autobaud “*” cmd to the TNC and you should get the sign on message.
4. Close your Terminal Program and open AirMail. Make sure you have AirMail set
   up to the correct serial port and the right baud rate. You can check this by going to
   “Tools-Options” and going to the “connection tab” and check the settings. Also go to the “module tab” then to VHF Packet Client and then to the “setup” box and check the settings there. Make changes if needed and save the setting. Now AirMail should work for you.

NOTE: Make sure you make the changes before you send the Autobaud command or you will be right back to where you started from.

A3030 Tell AirMail that you have a KAM+.

Here is another solution to the problem (from VA3RSA):

REASON FOR THE PROBLEM: When setting up the "VHF Packet Client", the KPC-3+ user will usually select the KPC-3 type TNC (nearest to KPC-3+). The TX Audio Level selection box is "greyed out" (can't be changed) with a fixed value of 500 (millivolts). The results are saved to the AirMail.ini file under the [Packet Client] section with TX Level 500. When the "Packet Client" is started, AirMail will initialize the TNC. The value that has been set for XMITLVL will be 280 (a result of the KPC-3+ converting 500 into digital setting 280). This can be verified by closing the "Packet Client" and opening the "Dumb Terminal". At the command prompt cmd: type 'xmitlvl' and it reports 280.

SIMPLE FIX (WORKAROUND): On my own KPC-3+ (ver. 9.1 ROM) I use XMITLVL 48 in combination with the radio's digital drive level setting (other users may have completely different settings). I observed that the "TX Audio Level" box can be "ungreyed" (i.e. made active/changeable) by selecting the TNC type as any one of the PTC-II types. Non-PTC-II TNC's leave the box "greyed out" (unchangeable). I selected the PTC-IIe (one-port type) and set the drive level to desired value (may require experiment etc.). In my case entering 24 millivolts sets my XMITLVL to 48 which is what I want. Go back and select the "KPC-3" TNC and save all settings.

CONFIRMING THE CHANGES: Checking AirMail.ini will confirm the setting TX level 24
(which will get converted to xmitlvl=48). Next, start up the "Packet Client" and let the TNC initialize. Then close down the "Packet Client" and start the "Dumb Terminal". You should find that XMITLVL is 48.

NOTE: The user must determine by experiment the correct setting of XMITLVL for their KPC-3+/radio combination resulting in the correct TX deviation level (for my radio it happened to be 48). Then adjust AirMail's "TX audio level (millivolts)" setting to give the required XMITLVL number (for my case it was 24 millivolts).

A3025 Laptops DO generate an incredible amount of noise. If you are using an HT the best solution is to use an external antenna. This puts some distance between the laptop and the transceiver’s antenna. A 20 foot distance may help.

Other possible remedies:

• Switching power supplies for Laptops. Use an Aircraft grade supply.
• Put ferrite chokes (snap ons) on all the cables coming from the computer serial, mouse, power etc.
• Use a RF filtered DC source for the Transceiver....make sure it has 20+ ampere capability.
• Bypass other sources (Refrigerators, bilge pumps, chargers, alternator etc.) at the source with good quality RF bypass capacitors.

Get a good book on RF Interference. Read the AirMail Help files. There is usually no one silver bullet...normally several things each reduce the noise a smaller amount. Useful information about RF ground systems is available at: http://www.radioworks.com/nbgnd.html

A3020 You may have some basic packet setup deficiencies. With the same equipment, can you connect to ANY other packet stations? Are you on the correct frequency? Is your transmit audio level set properly?

There are a couple of books available which describe some of the basics of setting up and operating a packet station. They are: "Your Gateway To Packet Radio" and “Practical Packet Radio”, both written by Stan Horzepa, WA1LOU. Both books are out of print, but can be obtained at reasonable prices from your local used book store or on-line book sellers.

N8UR has excellent basic packet audio level setup information available at:
http://www.febo.com/packet/layer-one/transmit.html

VK1OD has an excellent web page on “Amateur Radio application of Frequency Modulation” at:
http://www.vk1od.net/FM/FM.htm

KC2RLM has a great web page regarding “Sound Card Packet” at:
http://www.kc2rlm.info/soundcardpacket/

Larry Kenney (WB9LOZ) has an excellent “Introduction to Packet Radio”, available from:
http://www.choisser.com/packet/

Some radios do not perform well with both the microphone and the TNC connected
simultaneously to the radio. Disconnect the microphone.

A3015 Yes! KG9OG has come up with additional software to enable the AirMail Packet Client to work through the AGW software to your Sound Card device or any TNC that can be placed in the KISS mode. An additional benefit of using this method with any TNC is that you will be able to monitor all packet traffic on the frequency, using the Monitor function of the AGW software. N7XOO has written the following instructions to use for AirMail 3.3.081 and Windows XP, 2000, or Vista.

Configuring AirMail 3.3.081 Packet Client to work with AGWPE or AGW Packet
Engine Pro For Windows XP,2000 and Vista 32-bit (Vista 64-bit is untested):

The purpose of this process is to enable the AirMail software “Packet Client” module to work with most any sound card device or TNC that can be placed in the KISS mode, and with enough buffer memory to handle the demands of AirMail, and your computer CPU is quick enough for AGW.

This configuration requires the addition of two additional pieces of software, each
approximately 3M in size. Both are free-ware. The following assumes that you already have AGW working well on your computer.

1. Download, unzip, and install the “AirMail to Packet Engine” program (AMPE),
   AMPE162.zip. The link to the AMPE program (written by Brian Smith KG9OG) is
   http://www.qsl.net/mararc/ampe.htm

   After installing, read the excellent Help File and look for the Startup Command string.
   An Example would be:
   C:\ampe\AMPE16.EXE MYCALL,1,TRUE,8000,8100 where MYCALL is the call you are
   using for AirMail, and “1” is the AGW Port you are using.

   If a shortcut for AMPE is not on your desktop, create a shortcut on your desktop to
   AMPE16.EXE. Then edit that shortcut, by right clicking, selecting “Properties” and then on the “Shortcut” tab in the “Target” box add the information as above, substituting the call you are using in AirMail for MYCALL, click Apply and then Ok. (NOTE: Be sure to add a space after AMPE16.EXE before entering the first letter of MYCALL).

   Another alternative…
   AGW Packet Engine or AGW Packet Engine Pro may also be used to define the Command String. Within AGW…Setup…AutoStart….ampe16.exe the Startup Command String would be “MYCALL,1,TRUE,8000,8100”

2. Download and install the Lantronix CPR (Com Port Redirector) version 3.1.0.4
   The link to the Lantronix file is;
   http://ltxfaq.custhelp.com/cgi-bin/ltxfaq.cfg/php/enduser/std_adp.php?p_...

   Be sure to use the 3 version; the 4 version doesn’t seem to work for this application. The purpose of this software is to enable you to create a “Virtual Com Port” on your computer (with a number than is not already being used), and to “re-direct” that Virtual Com Port to the actual Port number (1, 2, 3, etc) that you have previously configured as part of the AGW software. IGNORE all the install and setup error messages when installing on Vista 32-bit. The program will still install. Unblock ports in any Windows Firewall messages.

3. Reboot the computer.
4. Open the Lantronix Com Port Selector Program and click the “Com Setup” button Select a com port number that is not used by your computer. Click the Port settings box and check "Raw", click the “Add IP” button and enter 127.0.0.1 for Host and 8100 for Port. Click “OK” and then click “Save”. IGNORE any setup error messages when installing on Vista 32-bit.
5. Reboot Again. The Lantronix software will now be running in the background. Verify the existence of your new “Virtual Port” by looking at Control Panel….System…Hardware…Device Manager….Ports.

   NOTE: For Vista 32bit, Device Manager will not show the Virtual Com Port, but it IS
   operational.

6. Configure AirMail Packet Client to use the virtual com port you set up in the Lantronix CPR and choose KAM+ for the TNC. You may not really be using a KAM+ but that's what's recommended for a choice. [The actual interface with your TNC is
   determined by the port settings in AGW.]

7. Close AirMail and edit the Airmail.ini file Backup your airmail.ini file; then do the following editing. Within the [Packet Client] section “comment out” lines by inserting a semi-colon at the beginning of these lines. See the Example below. Note that in this example COM12 is your “Virtual Port”; not the com port of the device you will actually use. All other settings remain the same, just add semi-colons starting with Tx Delay and ending with Packet Length.

   [Packet Client]
   DecoderType=KAM+
   Port Settings=COM12:9600,N,8,1
   Show Link Messages=1
   ;Tx Delay=600
   ;Persistence=64
   ;Slot Time=300
   ;Max Frames=2
   ;Frack Time=6000
   ;Max Tries=10
   ;Response Delay=2000
   ;Check Time=30000
   ;Radio Baud=1200
   ;Tx Level=500
   ;Packet Length=120
   ;Tx Delay 2=600
   ;Persistence 2=64
   ;Slot Time 2=300
   ;Max Frames 2=2
   ;Frack Time 2=6000
   ;Max Tries 2=10
   ;Response Delay 2=2000
   ;Check Time 2=30000
   ;Radio Baud 2=1200
   ;Tx Level 2=500
   ;Packet Length 2=120

   Save and Close the airmail.ini file.

8. Start AGWPE, then AMPE, then AirMail; then start the AirMail Packet Client
   Module. You should see a pop-up message from the Lantronix Com Port Redirector, and then in the Packet Client window it should say “Packet initialized OK”.

You should now be up and running. When you click “Connect”; AirMail will be using the port and device you have configured in AGWPE (or AGW Packet Engine Pro).

[written by Gary Harrison, N7XOO; January 9, 2008]
[edited by Don Felgenhauer, K7BFL]
Last revised April 29, 2008

A3010 Version 3.0.48 and some versions beyond that do not support AGW-PE. The reference to “AGW-PE” was mistakenly left in the code by the AirMail author, who is in the process of writing code to enable FUTURE versions of AirMail (Packet Client module) to work with Sound Cards and TNC’s using KISS, with the addition of the AGW-PE software. However KG9OG has come up with additional software to enable the AirMail Packet Client to work through the AGW software to your Sound Card. See Q3015.

A3000 Yes, but proceed very cautiously. The first versions of the D700, TH-D7, etc. have a very small buffer. If you use the software associated with Q3015, the radios will work with AirMail, if you use a very short packet length, and Maxframe of 1. More information is in the release notes that came with your AirMail version 3.2.035 download. Other radios which have this same packet performance are the Kenwood TS-2000, THD7, and Alinco DR-135. The radios will work fine if used with an external TNC supported by AirMail. See http://home.earthlink.net/~k7bfl/TascoModem.pdf

The built-in TNC will can also access WL2K via the “Keyboard” method (see Q8000).
It can also access WL2K in a limited manner by using the special APRSLINK method
described at: http://www.activeham.com/winlink/wiki/index.php?title=APRSLink

A4720 Four CMS servers are in operation, and they may be set with a single setup to alternate connections between them. This is the method automatically used by Paclink MP.

Go to Airmail 3.x menu item: "Tools>Options>Modules" and check the "Internet ACCESS (Telnet)" Option. Then go to the main "Modules" menu and click on "Internet Access (Telnet)."

Once the Airmail "Internet Access" module FORM is up, click on "NEW" and input the configurations for Telnet Servers:

WL2K (Remote Call Sign)
Server.winlink.org (Remote Host)
8772 (PORT)
120 (Timeout in seconds)
CMSTELNET (Password)

Using the above configuration in Airmail's "Internet Access" option will allow the continued use should one or more CMS not be operative.

A4700 The PMBO logic bypasses the Attachment Limit filter when downloading to a user who is connected directly to the PMBO via Telnet. The filter is intended to protect from large unwanted downloads over radio.

A4680 See A1700

A4660 See A1660

A4640 See 1630

A4500 The PMBO station you are trying to connect to may be having trouble with his connection to the internet. Try connecting to another PMBO or a Common Message Server.

In early 2008 most PMBO stations no longer accept Telnet connections from Winlink users, since it is possible (and recommended) that users access the Common Message Server directly. See Q4010. The advantage is going directly to a CMS is to reduce the latency of messages from minutes to seconds. It is the recommended method.

A4010 (This Telnet information may also be found in the Global Catalog under WL2K_Help).

AirMail Telnet Client setup
Go to AirMail menu item: "Tools>Options>Modules" and check the Telnet Option. If you wish you can also set the module to initialize when bringing up AirMail by also checking "autostart." However, if you wish to start the module manually, then go to menu item: Module>Telnet client."

Note: It is now possible for users of the AirMail Telnet (Internet Access) module, Paclink AGW, Paclink MP, and Telpac to access one of the four Common Message Servers (CMS) without going through a PMBO. The setup for accessing the San Diego CMS is:

WL2KS (Remote Call Sign; not case sensitive)
Sandiego.winlink.org (Remote Host; not case sensitive)
8772 (TCP Port Outbound)
30 (Timeout in seconds)
CMSTelnet (Password; not case sensitive)

Remote Call Sign and Remote Host information (case insensitive) for the other CMS sites are:

WL2KH Halifax.winlink.org (Halifax)
WL2KP Perth.winlink.org (Perth)
WL2KW Washington.winlink.org (Washington)

Going directly to a CMS reduces the latency of messages from minutes to seconds. It is the recommended method. All of the active Common Message Servers are continually updating each other with new information.

You may also access a PMBO Telnet server, which ultimately “relays” your messages to the CMS. Below are the settings for AirMail Telnet module option for the PMBOs supporting a Telnet Server:

W7IJ (Remote Call Sign; not case sensitive)
w7ij.no-ip.org (Remote Host; not case sensitive)
12001 (TCP Port Outbound)
120 (Timeout in seconds)
WL2KTELNETCLIENT (Password, not case sensitive

The full help file may be downloaded from the Global Catalog list under WL2K_HELP..
Use the same configuration as with W7IJ, except a different callsign, and a different IP address. Review the text version of the PMBO Frequency List in AirMail
(“View….Frequency List”) to find available PMBO’s with Telnet capability for you.

Note: Early in 2008 is will not be possible to access many of the PMBO telnet servers. Only those PMBO’s which will supply a HF/VHF “Hubbing” function will allow telnet access from users. Most WL2K users needing Telnet (Internet) access should connect DIRECTLY to the CMS (see above).

A4000 Telnet is an Internet protocol that allows the user to connect to a remote computer. AirMail has a communications module called the “Telnet Client”, or in later versions “Internet Access”. This module enables the AirMail user to send and receive messages with a PMBO, an RMS/RMS Relay station, or directly with the Common Message Server, using an internet “non-radio” path, or using a local high-speed radio link that transports TCP/IP like D-Star or HSMM. This results in a much faster throughput speed.

A6100 NTSD (National Traffic System – Digital) stations are NOT the same as Winlink network stations. They are not affiliated with WL2K in any way, scan different frequencies, and forward messages to other NTSD stations using precious HF frequencies. NTSD generally does not take advantage of the synergies using the Internet when it is available….radio only.

See the web pages by AE5V: http://home.earthlink.net/~bscottmd/airmail_address.htm

Also see Q320.

A6000

• The other station should make sure that its “Tools…Options….AutoAnswer” box is checked for “Accept Incoming Connects”.
• Both stations should be using the Handshake mode.
• The message should be Posted to the Receiving station.

A5580 Not really. The “Keyboard” method is very slow, compared to using the “Handshake” method. Handshake results in a MUCH higher efficient use of a frequency channel, and results in a complete “saved” documentation of the information shared between the two stations. If possible, use a voice channel for Chatting, especially on HF.

A5550

1. In the Terminal window, select the correct “system” and the callsign of the station you would like to connect (see Q5040).
2. Select either the “Handshake” or “Keyboard” mode of interaction with the other station.
3. Hit the green “Connect” button. After the station answers, the contact should proceed as with connecting to a CMS station, if you are using the “Handshake” mode.

If “Keyboard” is being used, you will be the initial “sending” station. Send a CTL O to transfer control to the other station.

If you both are in the “Handshake” mode, messages in the Out Box and the Transit Box will automatically flow to the other station, IF they have been Posted to the other station, and have not been previously sent to that station.

A5520 They were probably addresses to someone other than YourCall. Check the Transit Box, if you think the messages were actually sent to your station. If the messages were not sent, then they were not “Posted” to you.