I do not publish my "personal" e-mail addresses because I already receive too much spam generated by "list harvesting" in the past. So reply here.A properly configured group on groups.io will allow "replay to sender" No option to reply to sender on your io either I wanted to reply off list but it seems you do not want your email Preferences/ADIF modes/Custom ADIF mode mappings Now the contacts log as FT4 in LoTW and when downloaded after a verify in LoTW the contact verifies in HRD log. I have also added an entry of MFSK>FT4 in TQSL/file/Display or Modify In HRD log Modes I have the FT4 entry as FT4 MFSK Well I think I have found a setup that works. *IF* *LOTW IS FULLY ADIF COMPLIANT* and reports those submodes the same way it reports FT4. I haven't tested, but without ADIF compliance HRD will not properly "verify" any mode that is actually a "sub-mode" in ADIF standard - that includes JT65A/B/C, JT9A/B/C/D/E/F/G, CHIP64/128, etc. The only solution is for HRD to *get off its ass* and become ADIF compliant rather than continue to cause problems for its users. With your mapping, any MFSK mode except MFSK8, or MFSK16 will also be uploaded as FT4. That only works as long as you do not log *any other MFSK MODE* in HRD (MFSK4, MFSK11, MFSK22, MFSK31, MFSK32, MFSK64, MFSK128, MFSK64L, MFSK128L). To: Re: Downloaded FT4 QSOs not Verified. Boy am I glad I did not get caught up with that, especially since you have to pay. It seems coders at HRD are not listening or more likely do not care. No option to reply to sender on your io either so reply here. I wanted to reply off list but it seems you do not want your email known, not even in QRZ. HRD has defined/added many new modes since FT4" on export would have required almost no effort whenĭefining the new mode. With an ADIFĬomplaint structure, adding the rules "accept FT4 -OR. If the current owners of HRD cared, they could have certainlyĪdded ADIF compliance at any time in that time. Structure was introduced to ADIF in version 3.0.4 adopted six yearsĪgo. It seems coders at HRD are not listening or more likely do not care.I can't say, but as AA6YQ points out, the Vectors for false "reply to:" addresses used by spam mailers. Some of those (now abandoned) accounts have also been used as Receive too much spam generated by "list harvesting" in the past. I do not publish my "personal" e-mail addresses because I already I know that because the groups I "own" are configured that way. Or "reply to all" (which includes the sender's e-mail). No option to reply to sender on your io either so reply here.A properly configured group on groups.io will allow "replay to sender" > In HRD log Modes I have the FT4 entry as FT4 MFSK > I have also added an entry of MFSK>FT4 in TQSL/file/Display or Modify > Preferences/ADIF modes/Custom ADIF mode mappings Now the contacts log as FT4 in LoTW and when downloaded after a verify in LoTW the contact verifies in HRD log. Joe, W4TV On 11:56 PM, Garry Herden wrote: > Well I think I have found a setup that works. Outlook Laptop Gil W0MN Hierro Candente Batir de Repente 44.08226N 92.51265 W en34rb -Original Message- From: On Behalf Of Joe Subich, W4TV Sent: Tuesday, Aug08:03 To: Subject: Re: Downloaded FT4 QSOs not Verified.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |