I am doing some research into using Winlink/Pat in peer to peer mode on an AREDN network. My scenario involves accumulating messages at a P2P node that might be operating at a location where both AREDN and internet connectivity are available. The P2P host would normally not be configured to route TCPIP between the internet and AREDN. So, to jump the "air gap" between internet and AREDN, message forwarding is needed.
Because the embedded forms used by Winlink use the B2F format, embedded forms are only decipherable by other Winlink clients. I was hoping to overcome this by specifying that the originating form not be in embedded form format but be attached as a PDF file. This works fine between winlink clients (like pat).
What I have found is that when "forwarding" a message (to cms.winlink.org
) using pat, the attachment is not included when composing the message. My question is: Is this a bug in pat, or is this the way Winlink forwarding is supposed to work?
It's worthwhile to note that winlink.org
reject messages over 120k in size anyway.
It's possible to script something using "pat extract" and send the mail via smtp/binmail or some other API. I'm OK with this if that's the way it's supposed to work.
Other approaches to linking AREDN Winlink to the internet are possible, but this is the one I am testing for the moment. We have a few CMS gateways up on the mesh in the SF Bay area, but they are undocumented hacks (in a positive way!) for the time being.
Off topic, but IMHO what way Winlink handles forms is a disaster. Eventually, form handling should have been split off ages ago and managed as separate application from the core Winlink protocol. But the embedded text+XML is the world we live in now.