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/E5NEN5M665SP2QPDKIAPBRN3UR63WGXZ/",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/",
    "message_id": "[email protected]",
    "message_id_hash": "E5NEN5M665SP2QPDKIAPBRN3UR63WGXZ",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/SKIOQMZV7Q2MKTO7265BX7X7CS2P3JSG/",
    "sender": {
        "address": "greencl (a) mindspring.com",
        "mailman_id": "5421c5ff9a12494f8f7bd304db4ac696",
        "emails": "https://mailman.amsat.org/hyperkitty/api/sender/5421c5ff9a12494f8f7bd304db4ac696/emails/"
    },
    "sender_name": "Chuck Green",
    "subject": "[eagle] Re: YAHOO!!!! IT WORKS!!!!",
    "date": "2007-09-18T03:54:31Z",
    "parent": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/YQEUE5EKL3LZFM2C6YDNBHOVOAH6AJUU/",
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "Hi Jim,\n\nChuck's note stated that the user determines mode.  It can be set before \ndelivery but the user can also do it themselves as long as they know it \nneeds to be done.  The address needs to be specified by the *system \nadministrator*.  Again, it can be set before delivery but can also be \ndone by the user if they know it needs to be done.\n\nChuck\n\nJim Sanford wrote:\n> Bdale:\n> I don't disagree with anything you say.\n>\n> I had in mind something along the lines of installation and/or \n> configuration instructions.  Based on Chuck's note, it appears that \n> the user needs to specify address and mode before delivery.\n>\n> Thanks & 73,\n> Jim\n> [email protected]\n>\n>\n> Bdale Garbee wrote:\n>> On Sun, 2007-09-16 at 20:27 -0400, Jim Sanford wrote:\n>>   \n>>> Guys:\n>>> There's a lesson here:   DOCUMENTATION\n>>>     \n>>\n>> The only additional documentation I can think of that might help in this\n>> sort of case would be something like a CAN bus troubleshooting\n>> flowchart.  Having something like that wouldn't help avoid this kind of\n>> problem, but it might reduce the time to resolution.\n>>\n>> It does sound like the software Juan is using could use better error\n>> reporting in the case where there's apparently no module responding at\n>> the address selected.\n>>\n>> Pretty typical in projects like this for us to get a lot of mileage out\n>> of software and process documentation that's just barely adequate to the\n>> task and lacking in \"frills\" like good user interfaces and/or error\n>> reporting.  That doesn't make it right, but I don't think there are any\n>> magic fixes, either.\n>>   \n>> Bdale\n>>\n>>\n>>   \n> ------------------------------------------------------------------------\n>\n> _______________________________________________\n> Via the Eagle mailing list courtesy of AMSAT-NA\n> [email protected]\n> http://amsat.org/mailman/listinfo/eagle\n>   \n",
    "attachments": []
}