I observe this in VarAC v12.0.4, with VARA SAT on QO-100, and with VARA HF. May I suggest to move this discussion, out of the VarAC FM forum, and into VarAC Bug reports? I too, do not wish to disable incoming connection alerts, just to eliminate the spurious ones.

See https://www.varac-hamradio.com/forum/varac-fm-discussion-forum/after-beacon-no-luck/dl-243684d4-7dc3-4d72-aae4-c9880ee4d4ee Please comment there.

Originally, I thought he did it, see https://www.varac-hamradio.com/forum/bug-reports/check-for-illegal-email-names-or-addressees-v12-0-4 But it turns out that I was wrong, and VarAC 12.0.4 did it, but itself. Not user error.

He didn't do it! When he sent through a different station on QO-100 then it only sent once. It's an internal VarAC bug: My VarAC did it! So it is something about my station's software. Possibly related to the alpha version I am running: v12.0.4?

It turns out to be a bug in VarAC, not just a lack of validation. Please see https://www.varac-hamradio.com/forum/bug-reports/duplicated-emails However, I suggest VarAC employ sanity checks any way, to catch these types of issues at whatever stages it can!

In such a case, I would recommend copying it manually and sending a return mail, to let them know they had a typo. It's a good thing that it is hard to edit other people's mail relay etc. :-) Actually, it would be nice to have a "Bounce" or "Return" mail feature, in case messages are undeliverable. I would even consider allowing the message to be CCed to their email address. I sent a bunch of vmails that never got a reply - presumably they are stuck somewhere in a vmail queue or got deleted. I was experimenting trying to relay vmails to the U.S.A. over multiple hops. Unfortunately, it seems they did NOT get manually relayed to their destination.

Here is a new example of this bug - the EMAIL GATE indicators turned ORANGE: 1. Toggling PTT Lock did NOT clear the issue, this time! 2. The QO-100 instance is the email handler. It remained GREEN. 3. All the other instances turned ORANGE! Is it related to incomplete QSO info and automated logging failure? Log file 27/07/2025 08:14:12 - (CN:1) Connected to DL0VBK 27/07/2025 08:14:37 - (CN:1) Incoming message. 27/07/2025 08:14:53 - (CN:1) Disconnected from DL0VBK 27/07/2025 08:14:53 - (CN:1) Logging QSO to DB: DL0VBK 27/07/2025 08:14:53 - (CN:1) Unable to log QSO with DL0VBK ,missing information 27/07/2025 08:14:56 - (CN:1) Clearing outgoing queues. 27/07/2025 08:15:53 - (CN:1) Debug mode disabled 27/07/2025 08:15:54 - (CN:1) Instance number: 1 27/07/2025 08:15:54 - (CN:1) Setting unattended links ON (load) 27/07/2025 08:15:54 - (CN:1) Resetting to Slot 0 27/07/2025 08:15:54 - (CN:1) Opening COM port 27/07/2025 08:16:08 - (CN:1) Sending beacon 27/07/2025 08:16:08 - (CN:1) KISS BEACON sent 27/07/2025 08:17:15 - (CN:1) Error: unable to load QSO data: Value was either too large or too small for an Int32. at System.Convert.ToInt32(Int64 value) at System.Int64.System.IConvertible.ToInt32(IFormatProvider provider) at System.Convert.ToInt32(Object value) at VarAC.VarAC.get_qso_details(String guid) at VarAC.Form15.dg_ch_adif_history_SelectionChanged(Object sender, EventArgs e) 27/07/2025 08:17:15 - (CN:1) Error: unable to load QSO data: Value was either too large or too small for an Int32. at System.Convert.ToInt32(Int64 value) at System.Int64.System.IConvertible.ToInt32(IFormatProvider provider) at System.Convert.ToInt32(Object value) at VarAC.VarAC.get_qso_details(String guid) at VarAC.Form15.dg_ch_adif_history_SelectionChanged(Object sender, EventArgs e) 27/07/2025 08:17:17 - (CN:1) Error: unable to load QSO data: Value was either too large or too small for an Int32. at System.Convert.ToInt32(Int64 value) at System.Int64.System.IConvertible.ToInt32(IFormatProvider provider) at System.Convert.ToInt32(Object value) at VarAC.VarAC.get_qso_details(String guid) at VarAC.Form15.dg_ch_adif_history_SelectionChanged(Object sender, EventArgs e) 27/07/2025 08:17:21 - (CN:1) 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) 27/07/2025 08:17:21 - (CN:20) 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) 27/07/2025 08:17:21 - (CN:40) 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) 27/07/2025 08:17:21 - (CN:10) 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) 27/07/2025 08:17:22 - (CN:1) 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) 27/07/2025 08:17:22 - (CN:40) 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) 27/07/2025 08:17:24 - (CN:1) Error: unable to load QSO data: Value was either too large or too small for an Int32. at System.Convert.ToInt32(Int64 value) at System.Int64.System.IConvertible.ToInt32(IFormatProvider provider) at System.Convert.ToInt32(Object value) at VarAC.VarAC.get_qso_details(String guid) at VarAC.Form15.dg_ch_adif_history_SelectionChanged(Object sender, EventArgs e) 27/07/2025 08:17:35 - (CN:1) Error: unable to load QSO data: Value was either too large or too small for an Int32. at System.Convert.ToInt32(Int64 value) at System.Int64.System.IConvertible.ToInt32(IFormatProvider provider) at System.Convert.ToInt32(Object value) at VarAC.VarAC.get_qso_details(String guid) at VarAC.Form15.dg_ch_adif_history_SelectionChanged(Object sender, EventArgs e) 27/07/2025 08:17:39 - (CN:1) Error: unable to load QSO data: Value was either too large or too small for an Int32. at System.Convert.ToInt32(Int64 value) at System.Int64.System.IConvertible.ToInt32(IFormatProvider provider) at System.Convert.ToInt32(Object value) at VarAC.VarAC.get_qso_details(String guid) at VarAC.Form15.dg_ch_adif_history_SelectionChanged(Object sender, EventArgs e) 27/07/2025 08:19:52 - (CN:1) PSKReporter: Logged successfully (FR4KF) 27/07/2025 08:19:52 - (CN:1) PSKReporter: Sending accumulated records 27/07/2025 08:20:57 - (CN:1) Closing Rig comport 27/07/2025 08:20:57 - (CN:1) Closing GPS comport 27/07/2025 08:20:57 - (CN:1) Closing Rig TCP port

In 2025 (v12) the 30m calling frequency is now 10,133.

How to reproduce the bug: So it turns out VarAC gets confused when I open a new VarAC instance (not in the cluster). All the secondary instances' indicators turn ORANGE! They remain orange, even if select a profile or I close the new instance. However, if I toggle PTT LOCK in the email handler node, they all turn BLUE again! I don't think opening a new VarAC instance should affect other instances - especially if it is NOT part of a cluster! VarAC v12.0.4

Isn't it supposed to be blue (not orange)?

And...it went back to ORANGE again! 26/07/2025 20:22:20 - VarAC base directory: C:\Program Files\VarAC\ 26/07/2025 20:22:20 - Checking for VarAC update. 26/07/2025 20:22:31 - Shutting down VarAC... 26/07/2025 20:22:32 - Starting VarAC (V12.0.4) 26/07/2025 20:22:32 - OS: Microsoft Windows NT 6.2.9200.0 26/07/2025 20:22:32 - OS: Microsoft Windows NT 6.2.9200.0 26/07/2025 20:22:33 - Debug mode disabled 26/07/2025 20:22:33 - FREQ Schedule off 26/07/2025 20:22:34 - (CN:40) Instance number: 40 26/07/2025 20:22:34 - Exiting - Closing email gateway thread 26/07/2025 20:22:34 - Exiting - Closing Relat notifications and broadcast thread 26/07/2025 20:22:34 - Exiting - Closing Load datastream history thread 26/07/2025 20:22:34 - Exiting - Closing check for update thread 26/07/2025 20:22:34 - Closing VarAC 26/07/2025 20:22:34 - (CN:40) Away status set to true 26/07/2025 20:22:34 - (CN:40) Setting away status to true (load) 26/07/2025 20:22:34 - (CN:40) Unattended links enabled 26/07/2025 20:22:34 - (CN:40) Setting unattended links ON (load) 26/07/2025 20:22:34 - (CN:40) PSKReporter: logging enabled 26/07/2025 20:22:34 - (CN:40) PSKReporter: Connected 26/07/2025 20:22:35 - (CN:40) Advanced Mode enabled 26/07/2025 20:22:35 - (CN:40) Opening DB connection 26/07/2025 20:22:35 - (CN:40) Current VarAC DB version: 29 26/07/2025 20:22:35 - (CN:40) Updating login data to database. 26/07/2025 20:22:35 - (CN:40) Applications launcher disabled 26/07/2025 20:22:40 - (CN:40) Connecting VARA Main Modem Command interface... 26/07/2025 20:22:40 - (CN:40) Connecting VARA Main Modem data stream... 26/07/2025 20:22:40 - (CN:40) Connecting VARA Main Modem KISS Command interface... 26/07/2025 20:22:40 - (CN:40) Connected to VARA modem 26/07/2025 20:22:40 - (CN:40) Setting Bandwith to 500Hz 26/07/2025 20:22:41 - (CN:40) VarAC base directory: C:\Program Files\VarAC\ 26/07/2025 20:22:41 - (CN:40) VARA version: VARA HF v4.8.9 26/07/2025 20:22:41 - (CN:40) Checking for VarAC update. 26/07/2025 20:23:18 - (CN:40) Email Gateway disabled (Manually) 26/07/2025 20:23:29 - (CN:40) Email Gateway activated (Manually) 26/07/2025 20:23:51 - (CN:40) KISS BEACON received from 4Z1AC 26/07/2025 20:23:51 - (CN:20) KISS BEACON received from 4Z1AC 26/07/2025 20:23:51 - (CN:20) PSKReporter: Logged successfully (4Z1AC) 26/07/2025 20:23:51 - (CN:20) PSKReporter: Sending accumulated records 26/07/2025 20:23:51 - (CN:20) Logging Contact to DB: 4Z1AC 26/07/2025 20:23:51 - (CN:40) PSKReporter: Logged successfully (4Z1AC) 26/07/2025 20:23:51 - (CN:40) PSKReporter: Sending accumulated records 26/07/2025 20:23:51 - (CN:40) Logging Contact to DB: 4Z1AC

Unfortunately, it happened again, in v12.0.4 (the 20m instance's EMAIL GATE indicator turned ORANGE). Then I set PTT Lock ON in the QO-100 instance, and the 20m instance turned BLUE. I set PTT Lock OFF again, and the 20m instance remained BLUE. Strange. The log appears normal: 26/07/2025 18:47:57 - (CN:20) Email Gateway disabled (Manually) 26/07/2025 18:48:03 - (CN:20) Email Gateway activated (Manually)

I'm still sometimes getting a similar issue, in v12.0.4 (HF+QO-100). QO-100 instance is the email gateway node. EMAIL GATE turned orange in the HF instance. Note Not sure why, but Auto Log QSO was suddenly off. I used the LOG button - might be related. Log file 22/07/2025 22:35:25 - (CN:1) Opening COM port 22/07/2025 22:35:27 - (CN:1) Disconnecting SM3ULU 22/07/2025 22:35:30 - (CN:1) Disconnected from SM3ULU 22/07/2025 22:35:31 - (CN:1) Logging QSO to DB: SM3ULU 22/07/2025 22:35:31 - (CN:1) Logging QSO to ADIF and loggers: SM3ULU 22/07/2025 22:35:31 - (CN:1) QSO ADIF record was logged to Log4OM using UDP 22/07/2025 22:35:31 - (CN:1) Logging Contact to DB: SM3ULU 22/07/2025 22:35:34 - (CN:1) Connecting M7SJO 22/07/2025 22:35:51 - (CN:1) Connected to M7SJO 22/07/2025 22:36:19 - (CN:1) Report Received: 6 22/07/2025 22:36:59 - (CN:20) Error: unable to load QSO data: Value was either too large or too small for an Int32.    at System.Convert.ToInt32(Int64 value)    at System.Int64.System.IConvertible.ToInt32(IFormatProvider provider)    at System.Convert.ToInt32(Object value)    at VarAC.VarAC.get_qso_details(String guid)    at VarAC.Form15.dg_ch_adif_history_SelectionChanged(Object sender, EventArgs e) 22/07/2025 22:36:59 - (CN:20) Error: unable to load QSO data: Value was either too large or too small for an Int32.    at System.Convert.ToInt32(Int64 value)    at System.Int64.System.IConvertible.ToInt32(IFormatProvider provider)    at System.Convert.ToInt32(Object value)    at VarAC.VarAC.get_qso_details(String guid)    at VarAC.Form15.dg_ch_adif_history_SelectionChanged(Object sender, EventArgs e) 22/07/2025 22:37:15 - (CN:20) Error: unable to load QSO data: Value was either too large or too small for an Int32.    at System.Convert.ToInt32(Int64 value)    at System.Int64.System.IConvertible.ToInt32(IFormatProvider provider)    at System.Convert.ToInt32(Object value)    at VarAC.VarAC.get_qso_details(String guid)    at VarAC.Form15.dg_ch_adif_history_SelectionChanged(Object sender, EventArgs e) 22/07/2025 22:37:21 - (CN:1) 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) 22/07/2025 22:37:21 - (CN:20) 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)

No, actually, it left me at the top after scrolling all the way back!

Interesting! But I'm not sure what to do with this. Many of the stations on QO-100 can't auto-qsy! Therefore, until now, stations are making the QSO on the calling frequency. Except if they want to transfer a file, or stay a long time, then they QSY (usually manually) elsewhere. I don't remember seeing this issue until recently, after I upgraded to v12. Is this a new issue or an old issue?

This is still an issue (in July 2025), and now that there are more stations on QO-100 it is causing a lot of extra work fixing the log. Would it be possible to fix this in the next version pretty please?

I also notice issues with inconsistent timestamps in various functions of the software and GUI. IMHO the timestamp functionality/implementation should be reviewed / QAed. One example: I checked in to VarAC Wednesday. I composed the email, then started sending on one band, but the connection dropped. I then connected on a different band, and sent the email. 1. I think the date/time of the message should reflect when it is marked ready to send in the client! 1. There should be additional timestamps showing when it was relayed etc, 2. Since this is Ham Radio, timestamps should always be stored in UTC, but local time optionally displayed in the GUI.

Great idea! You know, since VarAC keeps a QSO log, maybe we could integrate awards and top operators of the week/month/year into the software, and on the web site! I.e. optionally report the statistics from each station and analyze them.

I experience this as well. Happened just now - in v12.0.0. It somehow hears my own beacon - but only sometimes. I did check, and there is only one VarAC instance on the band. Datastream 00:10:44 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 00:25:44 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 00:40:44 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 00:45:20 > INCOMING CONNECTION REQUEST. Still don't know who that is. 00:45:50 > NO LUCK. Maybe next time... 00:46:14 > INCOMING CONNECTION REQUEST. Still don't know who that is. 00:46:44 > NO LUCK. Maybe next time... 00:55:44 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 01:10:44 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 01:25:45 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 01:40:45 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 01:55:45 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 02:10:45 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 02:25:45 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 02:40:46 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 02:55:46 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 03:10:46 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 03:25:46 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 03:40:46 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 03:55:46 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 03:59:16 > INCOMING CONNECTION REQUEST. Still don't know who that is. 03:59:46 > NO LUCK. Maybe next time... 04:10:47 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 04:25:47 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 04:40:47 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 04:55:47 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 05:10:48 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 05:25:48 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 05:40:48 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 05:55:58 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 06:10:58 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 06:25:58 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 06:40:59 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 06:55:59 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 06:56:05 > NO LUCK. Maybe next time... 07:10:59 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 07:25:59 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 07:33:31 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 07:41:00 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 07:51:43 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 08:06:43 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 08:21:43 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 08:36:53 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 08:51:53 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 08:51:59 > NO LUCK. Maybe next time... 09:06:53 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 09:21:54 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 09:36:54 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 09:52:04 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 10:07:04 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 10:22:05 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 10:37:05 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 10:52:05 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 11:07:05 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 11:20:17 > INCOMING CONNECTION REQUEST. Still don't know who that is. 11:20:47 > NO LUCK. Maybe next time... 11:22:05 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 11:37:06 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 11:52:06 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 12:07:06 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 12:22:06 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 12:37:06 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 12:52:07 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 13:07:07 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 13:22:07 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 13:37:07 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 13:52:07 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 14:07:08 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 14:22:08 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 14:37:08 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 14:52:08 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 15:07:08 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 15:22:09 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 15:37:09 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 15:43:09 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 15:58:09 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 16:13:09 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 16:22:40 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 19:40:12 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 20:18:34 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 20:18:54 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 20:19:14 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 20:34:15 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE 20:34:21 > NO LUCK. Maybe next time... 20:49:05 > ADVANCED BEACON ON 3cm - 10.489.595.000> DE 4Z5PE Log ... 19/07/2025 20:34:15 - (CN:1) Sending beacon 19/07/2025 20:34:15 - (CN:1) KISS BEACON sent Note 1. I am operating VARA SAT with SDR Console in full duplex on QO-100. 2. It seems to occur also with VARA HF.

I still recommend you have the instances take turns automatically, so there is no need to designate a specific sender node. Or alternatively, split the email service to its own process/daemon/module. It doesn't really need to communicate directly with an active radio instance in order handle incoming and outgoing email! It just pushes and pulls email messages into/out of the mailqueues/mailboxes.