Email Detail

HTTP 200 OK
Allow: GET, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "url": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/ZGMIXTBBR26PG7AS522HOP33MH3SS4CB/?format=api",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/?format=api",
    "message_id": "635077970F51427287155B28FA569741@kb2m4PC",
    "message_id_hash": "ZGMIXTBBR26PG7AS522HOP33MH3SS4CB",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/UDYXJNOC2IPB4XTXU62W5BYT2YFZAXEV/?format=api",
    "sender": {
        "address": "kb2m (a) comcast.net",
        "mailman_id": "4f01ae6749a54d178a501e4efec2da0b",
        "emails": "https://mailman.amsat.org/hyperkitty/api/sender/4f01ae6749a54d178a501e4efec2da0b/emails/?format=api"
    },
    "sender_name": "Jeff",
    "subject": "Re: [amsat-bb] CY9C satellite update August 26",
    "date": "2016-08-26T15:17:39Z",
    "parent": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/YXFHHYDFK2W4HZQAKYKFRIFSHZWNKVX4/?format=api",
    "children": [
        "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/BVCRACR6GWANAIIMWKVDVCNMHOKNEEYY/?format=api"
    ],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "The Sat contacts might need to be re-entered depending on the logging \nsoftware used. My NJ radio club SJDXA  was the QSL manager for among others \nK1N. The log entries for Navassa weren't properly put in the log till after \nthe DXPedition was over. I offered to enter them , but N2OO took care of it, \nall 27 of them. So it might be awhile before they show up in club log....\n\n73 Jeff kb2m\n\n-----Original Message----- \nFrom: Patrick STODDARD (WD9EWK/VA7EWK)\nSent: Friday, August 26, 2016 10:33 AM\nTo: [email protected]\nSubject: Re: [amsat-bb] CY9C satellite update August 26\n\nHi Mark!\n\nI was searching for call signs of satellite operators who have\nworked CY9C, going back to the first two stations that worked\nthem (2E0SQL, KB1PVH) as reported via Twitter. I don't see those\ncalls in the log. For some satellite operators, I only saw HF QSOs\nlisted in the log (i.e., N8HM shows up for 30m CW). I did not expect\nanything for my call, since as of now (1430 UTC) the log was only\nupdated through 1447 UTC yesterday, and I worked them on AO-7\nat 2106 UTC yesterday.\n\nI'm not worrying about the log search. Seems like satellite QSOs\ndon't show up in these log searches, at least not right away, since\nthe log records need to have the additional fields inserted to\nindicate a satellite QSO. As Clayton said, if you still need a\nCY9C in your satellite log, it's time to start looking at any passes\nthat cover both you and them. Don't just rely on seeing AMSAT-BB\nposts or Twitter to plan your passes.\n\n73!\n\n\n\n\n\nPatrick WD9EWK/VA7EWK\nhttp://www.wd9ewk.net/\nTwitter: @WD9EWK\n\n\n\n\nOn Fri, Aug 26, 2016 at 2:23 PM, Mark Johns via AMSAT-BB <[email protected]\n> wrote:\n\n> Clayton,\n>\n> Do you know if satellite QSOs are reflected in the 2m ClubLog results? If\n> so, it's easy to see if your station is in the log and know that those\n> \"insurance\" contacts are unnecessary. (As of yesterday, my satellite QSO\n> was not shown in ClubLog. But I know it takes awhile, especially if \n> weather\n> has everything shut down.)\n>\n> --\n> Mark D. Johns, KØMDJ\n> Decorah, Iowa USA  EN43\n\n",
    "attachments": []
}