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/TCP4IZGASOJMYK6X437RECN5USJYQKVN/",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/",
    "message_id": "[email protected]",
    "message_id_hash": "TCP4IZGASOJMYK6X437RECN5USJYQKVN",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/4INR4TURFJT4LXMXH5LSRE7SZL6WEZUF/",
    "sender": {
        "address": "co7wt (a) frcuba.co.cu",
        "mailman_id": "e0c3935155ca4fb78cafec35cf64d7f2",
        "emails": "https://mailman.amsat.org/hyperkitty/api/sender/e0c3935155ca4fb78cafec35cf64d7f2/emails/"
    },
    "sender_name": "Pavel Milanes Costa",
    "subject": "Re: [amsat-bb] LightSail Data?",
    "date": "2015-05-28T12:41:35Z",
    "parent": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/4INR4TURFJT4LXMXH5LSRE7SZL6WEZUF/",
    "children": [
        "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/DCMQG7FXYWQ3EJCK3RW2E6B5UWXUAED2/"
    ],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "The packet modems relay on a CRC checksum of the packets to validate the \ndata received as a good packet.\n\nIn some situations, like yours when a modem is listening a long time, \nthe noise can \"forge\" a \"good\" packet. This is a statistically proved \nfact, the CRC is not as strong as we wish for this task.\n\nI'm not saying that this is a noise forged packet, but it's a possibility.\n\n73\n\nEl 27/05/15 a las 20:07, Kelley escibió:\n>\n> I left the rig and packet software running today while I was at work. I\n> was listening to the LightSail beacon on 437.435 MHz. I had one entry on\n> the screen when I got home:\n>\n> 1: Fm V-3 to 70-9 Via uH, , , -6 <RR P/F R5>[07:25:21]\n>\n> No idea what it means, not sure if it was LightSail or not. Posted as an\n> FYI. Curious to know what it might be.\n>\n",
    "attachments": []
}