locked DXCC Alert on bad callsign
Laurie -- could we get a last-ditch QRZ or HamQTH query before a User Alert is sent out to ensure the callsign is valid in QRZ if those options are checked?
Seems reasonable to put a check in there IMHO.
Seems the false decodes in WSJT-X can cause improper callsigns to pass through.
And DXPeditions are using ClubLog so maybe add ClubLog queries too -- but just for the User Alert?
So if none of the enabled services returns as valid callsign the alert is just dropped.