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/JFIGYE7VOHNR2OZVBRTEJTSP76P4VGXM/?format=api",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/?format=api",
    "message_id": "[email protected]",
    "message_id_hash": "JFIGYE7VOHNR2OZVBRTEJTSP76P4VGXM",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/JFIGYE7VOHNR2OZVBRTEJTSP76P4VGXM/?format=api",
    "sender": {
        "address": "rarcher (a) tourstar.net",
        "mailman_id": "da7671fffe114083b6ba27beeb382a4b",
        "emails": "https://mailman.amsat.org/hyperkitty/api/sender/da7671fffe114083b6ba27beeb382a4b/emails/?format=api"
    },
    "sender_name": "Rowland Archer",
    "subject": "[amsat-bb]  AO-27 Event Timing",
    "date": "2010-02-07T19:05:28Z",
    "parent": null,
    "children": [
        "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/ELHDXBA5AEMW6PRY7QP2DJXOYM3GVO3Z/?format=api"
    ],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "About a month ago the events that turn AO-27 on and off seemed to be \ntimed so it would be on as it passed over North America.  More \nrecently, for the passes I check (more than 10 degrees here in NC), \nit seems like according to schedule on www.ao27.org, the \"ON\" time is \nwhen the bird has pretty much finished its pass.\n\nFor example, right now at 1858, the footprint of AO-27 neatly covers \nmuch of the US and Canada, yet according to the website the next \"ON\" \nevent is at 1906, one minute before I lose the satellite completely.\n\nIs this intentional or \"just the way it is?\" Does it slowly cycle the \nON time so it is ON for passes in different parts of the world?\n\n73,\nRowland K4XD\n\n",
    "attachments": []
}