Issue After vmails are retrieved, the RELAY indicator clears, but the vmail waiting flag in the beacons list remains ON. This behavior is inconsistent and confusing. Discussion I understand that the original design was probably to statically list the beacons as received. However, it is confusing to the end user. Therefore it appears to the end user as a GUI bug. Solution I recommend to update the flags in the beacons list dynamically, when the vmail has been retrieved. This will improve the user experience.

Issue VarAC transmits unexpected data (from the previous session) on each reconnect, and it is hard to stop it! This could include text, commands, and vmails, that were still in the transmit buffer when it was disconnected.... A fix is described in Transmit buffer remaining after QSO: https://www.varac-hamradio.com/forum/bugs-fixed/transmit-buffer-remaining-after-qso?searchTerm=Buffer&origin=member_posts_page However, from my experience, it is my view that the fix there is incomplete and problematic. Suggested fix: 1. Instead of sending the old transmit buffer without confirmation - move it to the New Message text entry pane, and do NOT send it unless the person presses SEND! 2. For consistency, you should do the same with any unsent text, even if it was not in the transmit buffer yet. 3. If you want to be elegant: A. Ask the user if they want to save the unsent text for next connection. In most cases, the answer is probably no! B. You could then add it labeled as as Unsent Text in the chat history window, highlighted it in a different color, with the option to send it by double clicking. Example: I was disconnected while sending a vmail. Now when I reconnect, it continues - sending the vmail on the calling frequency! I could NOT stop it! CLR did not work! Every time I connected, it did the same thing! And it almost completed, but within a few seconds before completion, it timed out and disconnected! Of course, this is unexpected and dysfunctional behavior!

Issue M7SJO reports "Email is working well although it is still sending two emails to my Outlook inbox every time!" Cause It turns out he is using an email address as the name - and it happens to be the same email address! So I didn't look up the RFC / protocol, to check what is allowed. But apparently in Gmail at least, the name cannot be an email address. The Gmail client actually flags this as an error! Suggested fix So, you should run input sanity checks. If the addressee or name is disallowed, then reject or return the message. Ideally, you should catch this even earlier - in the composition stage, and not allow them to enter or to send to an illegal name/addressee. Error Message in Gmail Log file - Example 1 22/07/2025 20:47:59 - (CN:1) Incoming message. 22/07/2025 20:48:02 - Email sent to M7SJO@OUTLOOK.COM through Email gateway successfully. 22/07/2025 20:48:03 - (CN:1) Email sent to M7SJO@OUTLOOK.COM through Email gateway successfully. 22/07/2025 20:49:36 - (CN:20) KISS BEACON received from PD0WAG 22/07/2025 20:49:36 - (CN:20) PSKReporter: Logged successfully (PD0WAG) 22/07/2025 20:49:36 - (CN:20) PSKReporter: Sending accumulated records 22/07/2025 20:49:36 - (CN:20) Logging Contact to DB: PD0WAG 22/07/2025 20:51:23 - (CN:20) KISS BEACON received from PD2GCM 22/07/2025 20:51:23 - (CN:20) PSKReporter: Logged successfully (PD2GCM) 22/07/2025 20:51:23 - (CN:20) PSKReporter: Sending accumulated records 22/07/2025 20:51:23 - (CN:20) Logging Contact to DB: PD2GCM 22/07/2025 20:52:25 - (CN:20) PSKReporter: Logged successfully (EA5URB) 22/07/2025 20:52:25 - (CN:20) PSKReporter: Sending accumulated records 22/07/2025 20:52:51 - (CN:1) Email gateway: incoming email through IMAP server detected: Destination callsign: M7SJO. Pulling to the VMailbox. 22/07/2025 20:53:51 - (CN:1) Email sent to M7SJO@outlook.com through Email gateway successfully.

Issue 1. Vmails waiting RELAY indicator is red. 2. There is a mail icon in the Beacons list. 3. The Vmail Relay Notifications are missing from the list - even though there are vmails waiting. The list is empty! 4. I connect to the station, and it transmits a vmail. Then the RELAY indicator clears. Example:

Issue 1. M7SJO reports that his emails relayed through my station are duplicated - two copies of each email are sent. 2. It turns out that my VarAC station sends to his email address twice per email message. 3. VarAC is sending to "email <email>" i.e. VarAC is copying the email address and prepending it, which is in the position of the addressee name. 4. Gmail interprets this as an additional email address, and sends two copies to the addressee. 5. When he sends email through SM3ULU, this issue does not happen. The message is sent to only one addressee. 6. I am using VarAC v12.0.4. They are both using v12.0.0. Originally, I thought it was an addressee + name validation issue on his end. (I submitted a bug report requesting to add validation.) But after reviewing the Chat History it appears that VarAC is sending to "email <email>" i.e. VarAC is copying the email address and prepending it, which is in the position of the addressee name. And Gmail interprets this as an additional email address, and sends two copies to the addressee. Chat History

I noticed issues in the Last Heard Peeking (LHR) functionality: 1. The message is sent in local time - but it should be sent in UTC! 2. The message is too verbose - abbreviate the message, to reduce airtime. A. Do not report seconds. HH:MM is enough. B. Delete BEACON, it is redundant. If you can report also broadcasts - that would be best, so then it is not redundant, but should be abbreviated (e.g. BCN vs BRCST). But maybe it doesn't matter how it was heard? Just delete it! C. Remove "dB". It doesn't appear under SNR, why send unneeded data here? D. After all this, remove ">" and "/" and just use white space to separate the columns. E. Ideally, pretty print it, so the columns are aligned and human readable. F. If you do this, you could pretty-print it in the client, to save airtime. G. Compress the message before transmitting over the air: e.g., most of the time the band will be "20m" so why it is redundant to send the same text - just replace it with a short unique symbol for each band! Example

Bug CQ + Slot selector buggy on the satellite! This causes a bunch of issues: 1. The slot number is appended to the callsign instead of appearing in the slot column. 2. Failure to connect upon answering the CQ. 3. The RELAY indicator may NOT clear after retrieving vmails. Spotted in v12.0.4 Workaround and Suggested Fix Enabling Skip Slot Selector makes things work, though of course you lose the slot selection functionality. At the moment, most stations don't have auto-qsy ability on the satellite yet (though a few e.g. Pluto SDRs do). So probably best by default to disable CQ slot selection and requirement to QSY when on QO-100 satellite. And if it is on, warn that it may cause issues with stations that lack the capability. Example Effect of Skip Slot Selector

Issue Unhandled Exception Exception details See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary. at System.Collections.Generic.Dictionary`2.get_Item(TKey key) at VarAC.Form12.combobox_canned_messages_SelectedIndexChanged(Object sender, EventArgs e) at System.Windows.Forms.ComboBox.OnSelectedIndexChanged(EventArgs e) at System.Windows.Forms.ComboBox.WmReflectCommand(Message& m) at System.Windows.Forms.ComboBox.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) ************** Loaded Assemblies ************** mscorlib Assembly Version: 4.0.0.0 Win32 Version: 4.8.9310.0 built by: NET481REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll ---------------------------------------- VarAC Assembly Version: 1.0.0.0 Win32 Version: 1.0.0.0 CodeBase: file:///C:/Program%20Files/VarAC/VarAC.exe ---------------------------------------- System.Windows.Forms Assembly Version: 4.0.0.0 Win32 Version: 4.8.9251.0 built by: NET481REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll ---------------------------------------- System Assembly Version: 4.0.0.0 Win32 Version: 4.8.9310.0 built by: NET481REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll ---------------------------------------- System.Drawing Assembly Version: 4.0.0.0 Win32 Version: 4.8.9037.0 built by: NET481REL1 CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll ---------------------------------------- System.Core Assembly Version: 4.0.0.0 Win32 Version: 4.8.9297.0 built by: NET481REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll ---------------------------------------- System.Configuration Assembly Version: 4.0.0.0 Win32 Version: 4.8.9037.0 built by: NET481REL1 CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll ---------------------------------------- System.Xml Assembly Version: 4.0.0.0 Win32 Version: 4.8.9037.0 built by: NET481REL1 CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll ---------------------------------------- Accessibility Assembly Version: 4.0.0.0 Win32 Version: 4.8.9037.0 built by: NET481REL1 CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll ---------------------------------------- WindowsFormsIntegration Assembly Version: 4.0.0.0 Win32 Version: 4.8.9195.0 built by: NET481REL1LAST_B CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/WindowsFormsIntegration/v4.0_4.0.0.0__31bf3856ad364e35/WindowsFormsIntegration.dll ---------------------------------------- PresentationFramework Assembly Version: 4.0.0.0 Win32 Version: 4.8.9297.0 CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/PresentationFramework/v4.0_4.0.0.0__31bf3856ad364e35/PresentationFramework.dll ---------------------------------------- WindowsBase Assembly Version: 4.0.0.0 Win32 Version: 4.8.9297.0 built by: NET481REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/WindowsBase/v4.0_4.0.0.0__31bf3856ad364e35/WindowsBase.dll ---------------------------------------- PresentationCore Assembly Version: 4.0.0.0 Win32 Version: 4.8.9297.0 built by: NET481REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/PresentationCore/v4.0_4.0.0.0__31bf3856ad364e35/PresentationCore.dll ---------------------------------------- System.Xaml Assembly Version: 4.0.0.0 Win32 Version: 4.8.9297.0 built by: NET481REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xaml/v4.0_4.0.0.0__b77a5c561934e089/System.Xaml.dll ---------------------------------------- PresentationFramework.Aero2 Assembly Version: 4.0.0.0 Win32 Version: 4.8.9037.0 built by: NET481REL1 CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/PresentationFramework.Aero2/v4.0_4.0.0.0__31bf3856ad364e35/PresentationFramework.Aero2.dll ---------------------------------------- CookComputing.XmlRpcV2 Assembly Version: 3.0.0.0 Win32 Version: 1.0.0.0 CodeBase: file:///C:/Program%20Files/VarAC/VarAC.exe ---------------------------------------- System.Data.SQLite Assembly Version: 1.0.116.0 Win32 Version: 1.0.0.0 CodeBase: file:///C:/Program%20Files/VarAC/VarAC.exe ---------------------------------------- System.Data Assembly Version: 4.0.0.0 Win32 Version: 4.8.9214.0 built by: NET481REL1LAST_B CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll ---------------------------------------- System.Transactions Assembly Version: 4.0.0.0 Win32 Version: 4.8.9037.0 built by: NET481REL1 CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.Transactions/v4.0_4.0.0.0__b77a5c561934e089/System.Transactions.dll ---------------------------------------- System.EnterpriseServices Assembly Version: 4.0.0.0 Win32 Version: 4.8.9037.0 built by: NET481REL1 CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.EnterpriseServices/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.EnterpriseServices.dll ---------------------------------------- System.Numerics Assembly Version: 4.0.0.0 Win32 Version: 4.8.9037.0 built by: NET481REL1 CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dll ---------------------------------------- UIAutomationTypes Assembly Version: 4.0.0.0 Win32 Version: 4.8.9297.0 built by: NET481REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/UIAutomationTypes/v4.0_4.0.0.0__31bf3856ad364e35/UIAutomationTypes.dll ---------------------------------------- UIAutomationProvider Assembly Version: 4.0.0.0 Win32 Version: 4.8.9297.0 built by: NET481REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/UIAutomationProvider/v4.0_4.0.0.0__31bf3856ad364e35/UIAutomationProvider.dll ---------------------------------------- System.DirectoryServices Assembly Version: 4.0.0.0 Win32 Version: 4.8.9282.0 built by: NET481REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.DirectoryServices/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.DirectoryServices.dll ---------------------------------------- System.Speech Assembly Version: 4.0.0.0 Win32 Version: 4.8.9037.0 built by: NET481REL1 CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Speech/v4.0_4.0.0.0__31bf3856ad364e35/System.Speech.dll ---------------------------------------- ************** JIT Debugging ************** To enable just-in-time (JIT) debugging, the .config file for this application or computer (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled. For example: <configuration> <system.windows.forms jitDebugging="true" /> </configuration> When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the computer rather than be handled by this dialog box.

Beacons Load Last Heard History is Inconsistent with the Beacons pane, in a VarAC Cluster. The history loads entried from multiple instances, whereas the live Beacons history only displays the beacons on the current instance number. Suggested Fix I suggest when an instance loads history, the history should select for display only the entries heard by that instance number, not from other instances. The rest should be filtered out and excluded. I.e. it should restore the same entries that were displayed previously. In any case, the behavior should be consistent! Test Close and then reopen an instance and ensure it shows the same entries as before, and not additional entries leaked from other instances. Screen Capture

Screen Capture Log 16/06/2025 18:23:35 - Sending beacon 16/06/2025 18:23:35 - KISS BEACON sent 16/06/2025 18:23:52 - PSKReporter: Sending accumulated records 16/06/2025 18:24:11 - Error: unable to update instance busy status in SQLite:database is locked database is locked at System.Data.SQLite.SQLite3.Step(SQLiteStatement stmt) at System.Data.SQLite.SQLiteDataReader.NextResult() at System.Data.SQLite.SQLiteDataReader..ctor(SQLiteCommand cmd, CommandBehavior behave) at System.Data.SQLite.SQLiteCommand.ExecuteReader(CommandBehavior behavior) at System.Data.SQLite.SQLiteCommand.ExecuteNonQuery(CommandBehavior behavior) at System.Data.SQLite.SQLiteCommand.ExecuteNonQuery() at VarAC.VarAC.update_instance_busy_state(Int32 instance_id, Boolean is_busy) 16/06/2025 18:24:11 - Error: updating instance keepalive in SQLite:database is locked database is locked at System.Data.SQLite.SQLite3.Step(SQLiteStatement stmt) at System.Data.SQLite.SQLiteDataReader.NextResult() at System.Data.SQLite.SQLiteDataReader..ctor(SQLiteCommand cmd, CommandBehavior behave) at System.Data.SQLite.SQLiteCommand.ExecuteReader(CommandBehavior behavior) at System.Data.SQLite.SQLiteCommand.ExecuteNonQuery(CommandBehavior behavior) at System.Data.SQLite.SQLiteCommand.ExecuteNonQuery() at VarAC.VarAC.update_instance_keepalive(Int32 instance_id) Related Issue? https://www.varac-hamradio.com/forum/bug-reports/varac-cluster-breaks-from-last-heard-peaking-multiband-sqlite-conflict-v11-2-0

Issue Datasteam Message: "Error: UNABLE TO DECODE DATA FROM <STATION>. ABORTING." Example: Log: 08/06/2025 05:37:38 - Sending beacon 08/06/2025 05:37:38 - KISS BEACON sent 08/06/2025 05:37:42 - Clearing outgoing queues. 08/06/2025 05:37:53 - Connecting F1GBD 08/06/2025 05:38:04 - Connected to F1GBD 08/06/2025 05:38:10 - Error: UNABLE TO DECODE DATA FROM F1GBD. ABORTING. See VarAC.log for more info. In most cases a VARA packet from another QSO on the same frequency slipped into this QSO and corrupted the link. VarAC will now restart the VARA modem. Standby.... 08/06/2025 05:38:10 - Input string was not in a correct format. at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal) at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info) at System.Convert.ToInt32(String value) at VarAC.VarAC.<connect_varahf_modem>b__126_2() 08/06/2025 05:38:10 - Corrupted data that caused this: RMS Trimode 1.3.58.0 SECURITE CIVILE - STATION SATELLITE - ADRASEC (sysop: F1GBD op:Jean-Louis) 4Z5PE has 116 daily minutes remaining with F1GB 08/06/2025 05:38:10 - Aborting Link... 08/06/2025 05:38:10 - Aborting... 08/06/2025 05:38:10 - Disconnected from F1GBD 08/06/2025 05:38:11 - Logging QSO to DB: F1GBD 08/06/2025 05:38:11 - Unable to log QSO with F1GBD ,missing information 08/06/2025 05:38:11 - Restarting VARA modem 3/3 08/06/2025 05:38:11 - Disconnecting VARA modem... 08/06/2025 05:38:11 - Disconnected! 08/06/2025 05:38:11 - Error in mailbox_send_outbox_thread 08/06/2025 05:38:11 - Thread was being aborted. at System.Threading.Thread.SleepInternal(Int32 millisecondsTimeout) at System.Threading.Thread.Sleep(Int32 millisecondsTimeout) at VarAC.VarAC.<connect_varahf_modem>b__126_6() 08/06/2025 05:38:12 - Opening COM port 08/06/2025 05:38:21 - Connecting VARA Main Modem Command interface... 08/06/2025 05:38:21 - Connecting VARA Main Modem data stream... 08/06/2025 05:38:21 - Connecting VARA Main Modem KISS Command interface... 08/06/2025 05:38:21 - Connected to VARA modem 08/06/2025 05:38:21 - VARA version: VARA SAT v4.4.4