so ive been trying to get Winlink going for a few weeks now and i think i understand the basic concept — email over radio, messages get routed through an RMS gateway and then delivered to a regular email address or another Winlink user. but the actual setup is where im getting lost.

right now i have Winlink Express installed and i can see gateway stations in the list when i use the RMS Relay map, but when i actually try to connect via VHF (im running a TM-V71A into a Signalink) it either times out or i get a partial handshake and then it just drops. tried a couple different gateways in my area, one about 14 miles away which should be plenty strong enough. my VARA FM is configured and i can see audio levels moving when i key up so i dont think its a levels issue.

the other thing im not clear on is message handling — like when i send a message through Winlink, does it sit in a queue at the RMS until the recipient connects, or does it actually forward to their email in real time? trying to understand this for potential ARES use and i want to make sure im not missing something fundamental about how the store-and-forward works.

the timeout issue on VHF is almost always either a tone level mismatch or the gateway is just down/busy — a lot of the RMS gateways around here are volunteer-run so they go offline without warning. try checking the gateway's last heard time on winlink.org before connecting, if it hasnt been heard in more than a few hours its probably down.

for the VARA FM thing, make sure your drive level in the VARA settings isnt too hot. a lot of people crank it thinking more is better but it actually causes the modem to reject the connection on the other end. somewhere around 50-60% drive is usually a good starting point and then you tune from there by watching the waterfall. also double check your PTT delay, the Signalink has that little trim pot and if the radio isnt fully keyed up before the tones start going out youll get a garbage handshake every time.

as for the store and forward question — yes it queues at the CMS (the central server, not the RMS) and the recipient doesnt have to be on at the same time. when they connect next time their client pulls down waiting messages. if youre sending to a regular email address it forwards pretty much immediately once the CMS receives it from the RMS gateway. the RMS is just the radio-to-internet bridge, the real routing happens at the CMS infrastructure on the backend.

yeah what he said about the gateway being offline is real, i wasted like two hours one evening thinking my setup was broken and it was just the local gateway had been down since that morning. the winlink.org map shows a last-activity timestamp, definitely worth checking that first before you go down a rabbit hole reconfiguring things.

one thing i'll add — if you have access to HF at all, sometimes its actually easier to get your first successful Winlink session going on HF using VARA HF or even Winmor just because theres way more gateway coverage and if one frequency isnt working you can just try another. not saying VHF is wrong for what you want to do with ARES, thats totally the right call for local emcomm, but for just proving out your setup and understanding how the message flow works it can be less frustrating to start on HF.