Log4OM

Maritime mobile calls are generating DXCC alerts.
If there's no DXCC we should not get the alert. Perhaps if there's a MM option to allow this alert that would work for grid chasers.

2022-07-09 17:44:33.0693 INFO: [#=zBQA14NUM_z1vYr56DLu8E3Wzj3Oi] : Station W9MDB/MM is /MM - /AM -> DXCC NOT SET
2022-07-09 17:44:33.1251 INFO: [#=zyq1VIN21oGKVmiACag==] : [CLUSTER ALERT] Sending e-mail
2022-07-09 17:44:33.1261 INFO: [#=zjRPzHX94B$wH_FZj4b$AZ_I=] : Sending e-mail to [email protected]
2022-07-09 17:44:35.9108 INFO: [#=zjRPzHX94B$wH_FZj4b$AZ_I=] : Email sent
2022-07-09 17:44:35.9108 INFO: [#=zyq1VIN21oGKVmiACag==] : [CLUSTER ALERT] e-mail sent

FYI...Turns out this happens on any call that doesn't have a DXCC number.
Just had another bogus alert on TO8FTDM

This seems like a pretty easy fix to not send an alert when DXCC is invalid.
I tend to think the # of people chasing /MM grids is pretty small compared to the # of DXCC chasers getting bogus DXCC alerts.

Still doing this on 2.23.0.3
Surely this is an easy fix -- no county -- no alert. Don't need to be woken up in the middle of the night.

Subject Log4OM Cluster Alert notification
--------------------------------------------------
Log4OM message START

New cluster alert generated at 10/4/2022 6:39:06 PM UTC (10/4/2022 2:39:06 PM local)

Triggered rules:
[DXCC ALERT LOG4OM]

Callsign: YU2AX/MM
Country:
Band: 15m
Frequency: 21074.0
Emission type: DIGITAL
Identified mode: FT8

Here a list of available spot info:
Grid HK48