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/GGOCNCKT6SG6U6XRI6MQBWLVXABTE35K/",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/",
    "message_id": "[email protected]",
    "message_id_hash": "GGOCNCKT6SG6U6XRI6MQBWLVXABTE35K",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/GGOCNCKT6SG6U6XRI6MQBWLVXABTE35K/",
    "sender": {
        "address": "kk7p (a) wavecable.com",
        "mailman_id": "ecaeda8313f54fe6b33b16a345e6ba3a",
        "emails": "https://mailman.amsat.org/hyperkitty/api/sender/ecaeda8313f54fe6b33b16a345e6ba3a/emails/"
    },
    "sender_name": "Lyle Johnson",
    "subject": "[eagle]  SDX, MRAM and Radiation",
    "date": "2007-01-04T21:42:36Z",
    "parent": null,
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "Hello!\n\nI have heard anecdotal assertions that MRAM (see < \nURL:http://www.freescale.com/mram >) is inherently SEU immune from \nradiation, or at least very tolerant.\n\nDoes anyone have any knowledge of this?\n\nI ask because the Freescale part is pretty tempting, even if its standby \ncurrent drain is a little high.  Thinking in terms of SDX here...\n\n73,\n\nLyle KK7P\n\n",
    "attachments": []
}