Winlink Compatibility - X-Source Header Support

RadioMail Roadmap
,
1

Roadmap Item: Winlink Compatibility - X-Source Header Support

User Story
As a Winlink exercise coordinator and downstream message analyst,
I want RadioMail to include the X-Source MIME header in outgoing messages,
so that messages remain fully compatible with Winlink Express workflows and can be correctly analyzed when tactical addresses differ from sender identities.

Problem
RadioMail currently omits the X-Source header from outgoing messages. While messages transmit successfully, this creates a compatibility gap with Winlink Express and affects workflows that distinguish between:

  • Sender (potentially a tactical address)

  • Source (originating callsign/station)

This becomes important for exercises and automated parsing systems that rely on X-Source metadata.

Use Case

  • EmComm and Winlink exercise operators parse hundreds of messages weekly.

  • Future exercises will require use of Winlink Tactical Addresses (TA) as the Sender.

  • Without X-Source, message attribution and reporting become less reliable.

Proposed Solution

  • Add X-Source MIME header to all outgoing RadioMail messages.

  • Populate with originating station/callsign consistent with Winlink Express behavior.

  • Maintain existing message transport and interoperability.

Acceptance Criteria

  • Outgoing RadioMail messages include X-Source.

  • Header value matches originating station identity.

  • MIME output is compatible with Winlink Express and downstream Winlink tooling.

  • No impact on message delivery or protocol interoperability.

Priority
Nice-to-have compatibility improvement.

Target Consideration
Preferably before August 20, 2026 to support upcoming EmComm exercises.

2

Support for x-source header has been added to Beta build 1.6.0 (5) on TestFlight

1 Like