so ive been messing with Winlink Express for the past couple weeks and i think i mostly have it figured out but the gateway selection stuff is still tripping me up. like i get the basic concept — you connect to an RMS gateway, it relays your message through the Winlink system, eventually lands in the recipients inbox. fine. but when i pull up the RMS list in the client it shows me like 30 stations sorted by distance and i have no idea which ones are actually good to connect to vs just showing up on the list because they exist somewhere.

my setup right now is a Signalink USB into a Yaesu FT-991A, running Vara HF as my modem. ive gotten a few connections to work on 20m but sometimes it just times out after like 4 or 5 attempts and i dont know if thats a propagation thing or if the gateway is just dead. is there a way to tell if a gateway is actually active before you try connecting? the last heard timestamp in the system doesnt always seem reliable to me, had one show a recent timestamp and it just wouldnt connect at all.

also the message handling side — when i send a message to a regular email address does it just go, or is there a delay? asking because im trying to figure out if this is viable for our ARES group to use for actual traffic handling during an exercise next month and i want to know what to actually expect instead of finding out the hard way during the drill.

the gateway timeout thing is almost always propagation or the gateway being busy, not necessarily dead. those RMS nodes get hammered sometimes especially on 20m during busy hours. what i do is sort by distance but then also cross-reference with the Winlink maps page — winlink.org has a live map that shows recent gateway activity and you can usually tell which ones are healthy vs just technically on the list.

for your VARA HF setup specifically, try adding a few backup channels in your session settings for the same gateway on different frequencies. 40m is often more reliable for regional stuff than 20m depending on time of day and your location. also make sure your VARA is registered if you havent done that, the unregistered speed cap makes a pretty noticeable difference when youre trying to move actual message traffic under time pressure.

on the email delay question — generally pretty fast once the message clears the gateway, like regular email delivery times. ive had messages show up in a gmail inbox within a minute or two of the radio session completing. the slower part is just the over-the-air connection itself. for an ARES exercise it should be totally fine, just practice the workflow a few times before the drill so people know what the client looks like and dont panic when VARA is negotiating speeds.

yeah the last-heard timestamps are kind of sketchy sometimes, i noticed that too. i think it updates based on when the gateway checks in with the CMS servers and not necessarily based on actual RF activity so a gateway can look current but have its radio offline or something. the Winlink sysop mailing list occasionally has posts about gateways going down, thats one way to know but its not exactly real time either.

one thing that helped me was just building a short list of like 3 or 4 gateways that i know work reliably from my QTH and just cycling through those manually instead of letting the auto-connect logic pick randomly. takes a bit of trial and error upfront but once you know which ones actually respond to you consistently its way less frustrating.