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/GJVW4L4PZ565GLTZGLUSGU5T364YJHGB/",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/",
    "message_id": "[email protected]",
    "message_id_hash": "GJVW4L4PZ565GLTZGLUSGU5T364YJHGB",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/GJVW4L4PZ565GLTZGLUSGU5T364YJHGB/",
    "sender": {
        "address": "k.alexander (a) rogers.com",
        "mailman_id": null,
        "emails": null
    },
    "sender_name": "Ken Alexander",
    "subject": "[amsat-bb] MY struggles with AO-85",
    "date": "2016-07-02T00:22:50Z",
    "parent": null,
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "In several attempts I have yet to hear myself on the AO-85 downlink.  \nfinally, after playing with SatPC32 this evening I realized it tells me \npretty well exactly where I should be.  I ran through an upcoming pass \nto see what it tells me and the result is tabulated in the following \ntable.  First column is time (UTC), second column is the fine freq to 4 \ndecimals and the third column are frequencies I can actually enter in my \nTH-D72 with its 5 kHz frequency step.  435.170 at AOS confirms what many \nops have told me in the last few days.  What I forgot was how fast the \nfrequency changes as AO-85 passes through its maximum elevation; the \nmiddle 3 minutes will be busy!\n\nAnyway, I was pleased to \"discover\" this and hope the information will \ngive me what I need to finally make a QSO or two.  Now I just hope I \ndon't get rained out!\n\n73,\n\nKen Alexander\nVE3HLS\n\n",
    "attachments": []
}