The rule is that you log what you hear. If it does not match it means the other op likely did not upload correctly. His problem, not yours.
On Tue, 5 May 2020 13:13:59 -0400
"Mark Erbaugh" <mark.election@...> wrote:
I guess I should have been more specific. One station was N8GU/4 indicating that he was operating out of the call area. Another was OZ75MAY/73, which I think is related to a special or an operating event.
If I go back and remove the slashed info (and put it in the comment), will that mess up LoTW matches?
From: Mel Marcus
Sent: Tuesday, May 5, 2020 12:25 PM
Subject: Re: [N3FJPSoftwareUsers] eQSL Callsign Matching
The only reason a person would sign as an /AE was to show that he is allowed in the portion of the band. he took the extra test passed, but the fcc has not updated the database yet. aclog, eqsl, lotw could care less about it.
therefore logging his callsign without the /AE would be approprieate
-------- Original Message --------
Subject: [N3FJPSoftwareUsers] eQSL Callsign Matching
From: "Mark Erbaugh" <mark.election@...>
Date: Tue, May 05, 2020 10:43 am
I just started using eQSL with ACLog. I downloaded my inbox and noticed that a few calls were not matching and being flagged as confirmed by eQSL (with an E). In all cases, I think the problem was that I logged the contact with a /<extra> info, which is what the station was signing, but the record in the eQSL inbox didn't have the extra information. Is there a way to make the match ignore the extra or should I not enter the extra. FWIW, ACLog had no problem properly identifying the country, although it did not properly find the HamCall record.