WinLink

After all of these detailed instructions, where does this lead ?   

Ironically, this first scheduled event didn’t yield an acknowledgement at ARS NV6W, which suggests that something was awry at the ARCPACIFIC
server. An otherwise reasonable inquiry sent to the system administrator did not yield a response. There was no QSL, via bureau or otherwise.

No matter. I went ahead with the second event that was scheduled during the following week, and behold — an actual response or “ACK” from the ARCPACIFIC server —

ACK: ARC213-DR#: 999-21, Hurricane Gail, Msg#: 1, Routine Inbox

[email protected]
10:35 AM (9 hours ago)
to nv6w

Winlink has automatically forwarded this message…

Subject: ACK: ARC213-DR#: 999-21, Hurricane Gail, Msg#: 1, Routine
Message ID: SHM3UT8EXJTR
Date: 2021/01/15 18:28
From: ARCPACIFIC
To: NV6W
Source: ARCPACIFIC
CMS Site: CMS-A

[message acknowledgement]

The following message was received by ARCPACIFIC

Subject: ARC213-DR#: 999-21, Hurricane Gail, Msg#: 1, Routine
Sender: NV6W
To: ARCPACIFIC
Received: 2021-01-13 23:31 UTC
Acknowledged: 2021-01-15 18:28 UTC
Message-ID: CAFMXR9WCA5G
Number of attachments: 1
Size: 1218

Bottom line:  Due diligence is central here. Make sure that your Winlink electronic messages are actually being received at the division clearinghouse.