Cruising Services &
Topics: Spam Controls for AirMail (ham users only) and Telnet Settings (Internet Access ham users only)
This discussion is primarily for ham users. SailMail users have Spam and Telnet (Internet Access) pre configured in their software. Both ham and SSB marine users should always use the Internet Access module whenever they have internet access via an "plugged in" RJ-45 ethernet cable connection (LAN, router or broadband modem), WiFi, or cell phone broadband connection......save your radio connection time for when you need it. Telnet is super fast and does not use your "connect time" in SailMail or AirMail.
Using Winlink Webmail, Telnet (Internet Access) or the HF Terminal window to control SPAM Options:
It is strongly recommended that each Winlink 2000 user (AirMail ham user) set up a password for their Winlink account. This may be done in Webmail since your Webmail account has a page (User Settings ) that controls your Whitelist. See http://www.winlink.org/webmail. Whitelist management is very easy in webmail.
Airmail via HF Terminal or Telnet Access has an OFF and ON condition for the whitelist and the whitelist notice. These are no longer meaningful since the Whitelist option is no longer optional. The window below is clipped from AirMail
In addition to whitelist management, many users overlook the need to add an incoming message limit size in AirMail (ham). You can easily set you limit size in AirMail in the menu "Window" drop down menu. This is the same menu control that manages your SPAM controls. Winlink uses a concept of the whitelist to manage who can contact you via Winlink.
Winlink 2000 SPAM Control Options are manadatory as of August 1, 2008.
The whitelist controls only involve addresses from the internet and not the Winlink to Winlink user connections or outbound email from a Winklink user to the internet. Essentially, the Winlink User must have the sender's email address or domain name in their whitelist. For example, if you have not sent an email to someone on the internet, then they will not be able to contact you! There is a way, however, for someone to contact you if they are not in the whitelist. The sender must include the character sequence //WL2K in the subject line of the message. If //WL2K is found in the subject line, the message will be accepted and forwarded to all of the Winlink users of the message with an amateur callsign.
Subject://WL2K (then any other normal subject content to follow).
If the sender is not in the recipient's whitelist and no //WL2K is found in the subject line the message will be rejected with a reference to the Winlink WEB page where instructions for sending WL2K messages will be found. Whitelist notices are no longer being created and forwarded to recipients. There will be certain exceptions. Messages from the saildocs.com, sailmail.com, and other specific domains will be accepted unconditionally except where a recipient specifically blocks the domain name in their whitelist.
Under these conditions, unless the subject line contains //wl2k, you will ONLY receive E-MAIL messages that you have recorded in your own whitelist.
Winlink rules for creating the whitelist:
1. Each message you send to an
Internet E-mail address from Winlink will be recorded in your whitelist.
2. You may send a special message to the SYSTEM, giving it instructions for changes to your whitelist. See the AirMail Winlink-2000 options example below.
3. You may manipulate your individual whitelist via your WEBMAIL account.
To change the whitelist over-the-air or via Telnet (now called Internet Access in modules), the special email message should contain the information below, one line per individual instruction:
Examples are given below. These are not case sensitive.
Whitelist will contain all e-mail addresses sent FROM your Winlink e-mail address, and retain these Internet e-mail addresses for a period of 400 days from your last e-mail to that address. You may also send a special message to activate, delete, or reject an e-mail address. This is described below.
From "inside the system" such as via Webmail (internet), Telnet (Internet Access) or via the HT Terminal (radio), sending the following message:
To: System (note....this is all you need, just the word
system, not case sensitive)
In the message body of this special message, you may put the following commands (capitalize words) below but in your email the capitalization is not require and the commands are not case sensitive:
LIST - will return a list of all whitelist entries for the user. Went you connect and send your email, this simple one command will cause the Winlink server to generate your whitelist and send you a reply with accept and reject entries. Give it try, it will be obvious after you send one and receive the Winlink reply.
Note: Domain Entries without the "@" will be treated as "domain names" only. For example if "ACCEPT: arrl.org" were entered, then ANY message from that "domain name" (arrl.org) would be accepted.
Examples of messages to control the Whitelist:
------------------message body below----------------
-----------------end of message body----------------
-------------------message body below----------------
-----------------end of message body----------------
Below is the normal window that opens with AirMail/Modules/Internet Access:
If you did not activate the module previously in AirMail options, then Telenet Access is setup in the AirMail / Tools / Options/modules tab:
After bringing up the Internet Access window, first click on the "settings" box and fill in the Telnet Settings as below.
Using the above configuration in Airmail's "Internet Access" option will allow the continued use should one or more CMS servers are not be operative.
However, there may a reason to use a specific CMS server. Currently there are five CMS locations, each with a specific remote callsign. To use the San Diego CMS site, the settings would be:
WL2KS (Remote Call Sign; not case sensitive for
San Diego CMS server)
sandiego.winlink.org ..... see below for the CMS settings of other servers (you have to match the remote callsign with the server)
8772 (TCP Port Outbound)
30 (Timeout in seconds) -- note, I have 120 in the illustration above due to some slow connections via WiFi
Local Callsign is your Ham callsign
CMSTelnet (Password; not case sensitive)
Remote Call Sign and Remote Host information (case insensitive) for the specific CMS Sites are:
|Remote Call Sign||
Remote Host and (CMS Location)
|WL2KS||SanDiego.winlink.org (San Diego)|
|WL2KW||Washington.winlink.org (Washington) -- not DC|
|WL2KV||Wien.winlink.org (Wien -- better known as Vienna)|
All of the "active" Common Message Servers are continually updating each other with new information.