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/N2EBP4RE4PY7GRTVGB2ET3BW3VBUSOOO/",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/",
    "message_id": "[email protected]",
    "message_id_hash": "N2EBP4RE4PY7GRTVGB2ET3BW3VBUSOOO",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/N2EBP4RE4PY7GRTVGB2ET3BW3VBUSOOO/",
    "sender": {
        "address": "wb4gcs (a) amsat.org",
        "mailman_id": "87014499e012476c8198fad186f7f963",
        "emails": "https://mailman.amsat.org/hyperkitty/api/sender/87014499e012476c8198fad186f7f963/emails/"
    },
    "sender_name": "Jim Sanford",
    "subject": "[eagle]  Service class names",
    "date": "2006-10-18T00:59:23Z",
    "parent": null,
    "children": [
        "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/CNYQD5NSY5LHMCEFOHJDWXGMMUWIG7QB/"
    ],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "Team:\nA few days ago, I made a proposal for naming Eagle's communications \nservices and solicited comments.  I received many good comments.\n\nI really think it important that we have unambiguous service class \nnames.  Based on all the comments, I propose:\n    U/V \"linear\"\n    L/S  \"linear\"\n    Text messaging\n    Low Rate ACP\n    High Rate ACP\n\nWhile I'd prever something less ambiguous than \"linear\", our customers \nseem to understand that \"linear\" means SSB/CW/PSK31/SSTv . . . . etx.\n\nAny strong objections to this?\n\nIf not, I'll get the announcement on AMSAT.org changed.  It's time to \nget precise.\n\nThanks & 73,\nJim\[email protected]\n\n",
    "attachments": []
}