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/2L6Z7XDY4PIXTXFNQYSAAXW3VHRZMQQ5/",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/",
    "message_id": "26961521.5337.1488749120637@mswamui-thinleaf.atl.sa.earthlink.net",
    "message_id_hash": "2L6Z7XDY4PIXTXFNQYSAAXW3VHRZMQQ5",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/2L6Z7XDY4PIXTXFNQYSAAXW3VHRZMQQ5/",
    "sender": {
        "address": "twdeckard (a) earthlink.net",
        "mailman_id": "7ce245bfe53e49ee99247feaa165c0b9",
        "emails": "https://mailman.amsat.org/hyperkitty/api/sender/7ce245bfe53e49ee99247feaa165c0b9/emails/"
    },
    "sender_name": "Todd Deckard",
    "subject": "[amsat-bb] Any communication thru CAS-2T/Fengtai-1",
    "date": "2017-03-05T21:25:20Z",
    "parent": null,
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "After the delight of BY70-1, I was wondering if any practical two-way communication was possible with CAS-2T?  \n\nAny clever schemes to work around the downlink issues?  Anybody up to pound out some MCW? ... could just mash it out with the push to talk switch -- my morse is so bad that the ARRL officially recognizes \"that gibberish must be coming from Todd\" as a valid QSO. \n\nTodd\n",
    "attachments": []
}