Yes, I have much of that going already, but I am not having luck with
the zip code in the to: field. I get matches say K6HTN lives in
91104, and she gets tons of messages. I forward her matches to a file
(because we are still trying to get her setup), despite 91104 being
set in my forward settings for her call, I have to manually go in and
tag each piece of traffic to be forwarded. They don't automagically
get tagged green like @NTS* does in the AT field.
-Chris KQ6UP
On Wed, May 3, 2023 at 8:54?AM Mark Taylor <mtaylor@...> wrote:
Chris,
From memory so you may have to play around with these and read the documentation.....
In your telnet config you should have the directives to be a Winlink gateway.
CMS=1
CMSCALL=xxxxxx
CMSPASS=xxxxxx
Then you need to provide a relay directive...
RELAYAPP=BBS
Read up on FALLBACKTORELAY as that might be needed in your case.
That will put all Winlink messages in the BBS where users can pick them up. You may need an APPLICATION line to answer Winlink connections.
For NTS messages it is just a matter of forwarding records. A zip code in the TO field will forward to that station and the station probably should be a NTS digital station expecting NTS messages.
In the AT field you can put NTS* to forward all NTS messages, or you can use NTSxx where xx is a specific state to forward NTS messages for that state to a NTS digital station.
There are most likely other ways to do this, I'm sure. I actually run RMS Relay along side of one of my installs as it acts as a Local Post Office and I have not found a way for BPQ to completely simulate the actions of Relay.
Using those hints you can probably get it working the way you want, and may get a few more hints from other users more experienced than me.
73,
Mark
--
Thanks,
Chris Maness
