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/WOFKYUFFB4QFWXVS3PDWZHSPGSHNNNSZ/",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/",
    "message_id": "[email protected]",
    "message_id_hash": "WOFKYUFFB4QFWXVS3PDWZHSPGSHNNNSZ",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/WOFKYUFFB4QFWXVS3PDWZHSPGSHNNNSZ/",
    "sender": {
        "address": "k9qho6762 (a) sbcglobal.net",
        "mailman_id": null,
        "emails": null
    },
    "sender_name": "WILLIAMS MICHAEL",
    "subject": "[amsat-bb] Re: amsat-bb] AO-73 sometimes hard to access",
    "date": "2013-11-26T19:52:24Z",
    "parent": null,
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "Make your computer clock is synchronized with WWV exactly.\n \nI've noticed the time sync problem on VO-52 (LEO) and especially doing downlink telemetry from MASAT-1 (LEO). The satellite is moving very fast so if your computer clock is off, your antennas will not be at the correct position. Since FO-29 and AO-7 are higher, they moving slower across the sky and are more forgiving with this time issue.\n \nCheck regularly for updated Keps as they are changing for AO-73. AO7 and FO-29 have been around a while so their Keps are pretty stable. AO-73's Keps are still unsettled and so the resulting Doppler problems. LEOs seems to need their Keps updated more regularly then FO-29 and AO7. Again, I found this out when doing  telemetry down loading on MASAT-1. \n \nAnd again, AO-73's circuits maybe not quite stable yet.\n \nGL, have fun,\n \nMike, K9QHO\n",
    "attachments": []
}