Show an email

GET /hyperkitty/api/list/[email protected]/email/6BWNGETXB2GGHAAWVOCQY4AQ7GGXAI2M/
HTTP 200 OK
Allow: GET, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "url": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/6BWNGETXB2GGHAAWVOCQY4AQ7GGXAI2M/",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/",
    "message_id": "[email protected]",
    "message_id_hash": "6BWNGETXB2GGHAAWVOCQY4AQ7GGXAI2M",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/6BWNGETXB2GGHAAWVOCQY4AQ7GGXAI2M/",
    "sender": {
        "address": "n4zq (a) netzero.net",
        "mailman_id": null,
        "emails": null
    },
    "sender_name": "Keith N4ZQ",
    "subject": "[amsat-bb] Re: FO-29 Heard Sat Apr 21 2007 10:30 UTC",
    "date": "2007-04-21T14:57:08Z",
    "parent": null,
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "Disregard my earlier post that FO-29 was heard this morning. After\nreading the many other post about it not being heard at all, it got me\nto thinking. A dangerous thing. So I reset my PC clock back to 10:25\nUTC and fired up SatPC32, which I used for Doppler correction, and\nUA9OV CW Type to generate a CW CQ Beacon. \n\nLow and behold I heard myself again, but this time FO-29 was located\nover the South Pole. Seems I have a weak, self generated, birdie that\noccurs at or near one of FO-29 down link frequencies.\n\nMy error !!  Sorry if I got any hopes up and NOW I really pray FO-29 is\n  fixable...\n\nKeith N4ZQ\n\n\n\n-- \"Keith N4ZQ\" <[email protected]> wrote:\nBriefly, and I emphasize briefly, heard my own CW CQ on the 16 degree\npass of FO-29 this morning. The signal only showed up about midway into\nthe pass and lasted less than a minute. The satellite was barely in\nsunlight heading to eclipse. Signal was weak but sounded normal, no\nFMing noted.\n\nCan only hope it's recoverable.\n\nKeith N4ZQ\nEL88 Florida \n\n\n\n\n \n\n\n",
    "attachments": []
}