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/HXOOGW4YTIDHDT2OPUDHNDR75PHLZKYB/",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/",
    "message_id": "000301c7c334$495b3ba0$6432a8c0@LAPTOP9",
    "message_id_hash": "HXOOGW4YTIDHDT2OPUDHNDR75PHLZKYB",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/RQX4DLDIYY3MVVVNFRFO357N5UXLTUIQ/",
    "sender": {
        "address": "eagle (a) howardlong.com",
        "mailman_id": "a9c59876bf364a4fb3565b10d9755577",
        "emails": "https://mailman.amsat.org/hyperkitty/api/sender/a9c59876bf364a4fb3565b10d9755577/emails/"
    },
    "sender_name": "Howard Long",
    "subject": "[eagle] Re: CAN-Do-Too!   ??????????",
    "date": "2007-07-10T20:52:52Z",
    "parent": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/TTAXE4IAMYG3DK62OKWNABJJAHU5UYFR/",
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "Hi Chuck \n\n> The naming of one \"EB\" is a legacy from P3D where the engineering beacon \n> was so pervasive throughout the satellite that it was decided to actually \n> name one of the user pins as such.  Part of this is also driven by P3E/P5A\n\n> perceived requirements.  P3E has used some of the user pins to input \n> structure thermistor signals to modules that do not otherwise use all \n> of their analog input pins on the 40 pin connector.\n\nOn P3E, the EB signal goes to the P3E U/V transponder from the IHU3. In the\nU/V transponder, it hits a DSP GPIO pin via a voltage level adjustment and\nisolation circuit. The DSP uses this to generate the BPSK beacon.\n\n73, Howard G6LVB\n\n",
    "attachments": []
}