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/DXZZOPKQHBNCCBZMAWAAMYTSWGDYL5BC/?format=api",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/?format=api",
    "message_id": "[email protected]",
    "message_id_hash": "DXZZOPKQHBNCCBZMAWAAMYTSWGDYL5BC",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/OTYTGCXZIN2XPHIPEAYAFQ632QSDABAZ/?format=api",
    "sender": {
        "address": "wb4gcs (a) amsat.org",
        "mailman_id": "87014499e012476c8198fad186f7f963",
        "emails": "https://mailman.amsat.org/hyperkitty/api/sender/87014499e012476c8198fad186f7f963/emails/?format=api"
    },
    "sender_name": "Jim Sanford",
    "subject": "[eagle] Re: Team Speak tomorrow night",
    "date": "2006-09-12T02:20:19Z",
    "parent": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/6R4L6O5G6XSJVYXCBPIXXAEWG52K7FPT/?format=api",
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "As I understand the proposal, the L/S package developers are welcome to \nuse SDX. \nJim\n\n\nMatt Ettus wrote:\n\n>\n>>             We offer that anyone willing can develop and submit for \n>> testing and qualification a stand-alone L/S transponder to fly in one \n>> of the TSFR slots, using fixed antennas.  It would be usable at/near \n>> Apogee, like the microwave packages on AO-13 and A)-40.  What do you \n>> think?  Les's discuss this.\n>>  \n>>\n> Bad idea.  We discussed having ONE SDX transponder and ONE digital \n> communications payload.  If for some reason it is decided that the DCP \n> is on neither S1 nor L (which itself would be a bad idea...), AND it \n> was decided that there was a desire for old-style transponders on L/S, \n> then it makes sense to build it as part of the SDX, and not have a \n> THIRD payload.\n>\n> Matt\n>\n",
    "attachments": []
}