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/3FNQBEFLSEJILOA2QG4OSLPA56BPFYCN/",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/",
    "message_id": "[email protected]",
    "message_id_hash": "3FNQBEFLSEJILOA2QG4OSLPA56BPFYCN",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/3FNQBEFLSEJILOA2QG4OSLPA56BPFYCN/",
    "sender": {
        "address": "rhyolite (a) nettally.com",
        "mailman_id": null,
        "emails": null
    },
    "sender_name": "RFI-EMI-GUY",
    "subject": "[amsat-bb]  LogSat Y2k???",
    "date": "2009-06-04T04:30:53Z",
    "parent": null,
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "Anyone still using LogSat out there?\n\nI have version 5.2.61 with the Y2K patches installed. I am running WINXP \nOS. This has been a very good program for me over the years. I like how \nit works.\n\nI just got through updating the KEPS etc so that I could print out some \nsatellite predictions. All worked well until I fine tuned the time to \nGMT using the time setting utility in the program that queues up the \nsystem clock.  (This utility has only two digits for the year.). I \nprinted out about 10 pages of work and then turned on my browser and \nfound the Yahoo security certificate had expired. In checking the system \nclock under windows the year was 3909!\n\nHas anyone encountered this bug?\n\nAlso the DST box has to be checked to get correct GMT -  Strange??\n\n-- \nJoe Leikhim K4SAT\n\"The RFI-EMI-GUY\"©\n\n\"Use only Genuine Interocitor Parts\" Tom Servo  ;-P\n\n\n\n",
    "attachments": []
}