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/BFFIAA6JTHMKZ6V2PUWJOEJNW5HMR4JQ/",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/",
    "message_id": "[email protected]",
    "message_id_hash": "BFFIAA6JTHMKZ6V2PUWJOEJNW5HMR4JQ",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/GQN66W4DHOQJYEXDIZCCLWG3525EQ6AV/",
    "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] Re: Where we're heading for bands and services",
    "date": "2006-09-25T04:36:20Z",
    "parent": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/MFPRYKZBBGA36BE2HTNVU5NVU2N4PL7O/",
    "children": [
        "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/EGY7WVKAYQ6ERWGT6WGOGJGOYUJ6E5AN/"
    ],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "\n> If we don't \"promise\" a performance level, then we must face the problem that \n> Franklin pointed out with AO-40 -- a set of realistic user requirements was \n> never presented, so everyone was just flying blind.\n\nI think we need to promise a field strength (flux density, whatever the \npolitically correct term is these days :-) on the ground for a given \nuplink power by the user, or its equivalent.  We can't control the \nuser's noise environment, but we sure better be able to predict our \ndownlink and publish it and meet it.  And don't forget to add 6 to 8 dB \nof loss just because, since I seem to recall we've nearly always been 6 \nto 8 dB shy of our expectatins in the past...\n\n73,\n\nLyle KK7P\n\n",
    "attachments": []
}