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/HDT32ZNWVOGFLPZ4OBPWCAVGFLDPFGPD/",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/",
    "message_id": "[email protected]",
    "message_id_hash": "HDT32ZNWVOGFLPZ4OBPWCAVGFLDPFGPD",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/HDT32ZNWVOGFLPZ4OBPWCAVGFLDPFGPD/",
    "sender": {
        "address": "wa113y3s (a) yahoo.com",
        "mailman_id": null,
        "emails": null
    },
    "sender_name": "Jeremy Bomkamp",
    "subject": "[amsat-bb] Re: ISS",
    "date": "2011-06-17T00:13:24Z",
    "parent": null,
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "No problem Kevin.  I dont rely on HRD sat tracker much but after seeing your \nmessage on the board I did some investigating to see what the problem actually \nwas.  My HRD sat tracking was lagging like yours for the ISS, I closed it and \ntried running as administrator and uploading keps and nothing changed.  By \nchance I changed my keps on satpc32 from celestrak to amsat and the ISS was \npredicted to be the same position as HRD.  That is how I came across the remedy \nfor HRD, but when I eliminated the amsat site for keps downloads, all it showed \nwas the moon no matter what sat I selected, so I shut down sat tracker and \nrestarted and everything worked like it should.  And before Alan asks again, my \ncallsign is AB9RU, and thanks again Alan for your satpc32 doppler file, and \nKevin good luck hunting packet QSO's on the ISS digi\n",
    "attachments": []
}