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/N3UKHGPB3TPSQ2LKBX5JC2JBSW7I52GD/",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/",
    "message_id": "[email protected]",
    "message_id_hash": "N3UKHGPB3TPSQ2LKBX5JC2JBSW7I52GD",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/N3UKHGPB3TPSQ2LKBX5JC2JBSW7I52GD/",
    "sender": {
        "address": "emily (a) planetemily.com",
        "mailman_id": null,
        "emails": null
    },
    "sender_name": "Emily Clarke",
    "subject": "[eagle]  Skin Issues",
    "date": "2007-03-02T22:05:06Z",
    "parent": null,
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "\nDuring the last upgrade the special EaglePedia skin for non-Eagle \nteam members was no longer needed.  However it appeared that at least \none team member had that skin in their preferences and this made it \nimpossible for them to log on.  There is no way for me to tell if \nthis is affecting other members, but the situation has been partially \ncleared up. If you did have this skin as a preference the system will \nnow switch you over to the \"Classic\" skin and you can change your \nskin preferences there.  Here are the steps to do that:\n\n1) Log on to EaglePedia with your user name and password\n2) Go into Preferences (link is in the upper right)\n3) Select \"Skins\"\n4) Select \"Monobook\"\n5) Save\n\nThis will make sure you have the same skin (and same user expereince) \nas is intended.\n\n73,\n\nEmily\n\n\n\n---------------------------------\nN1DID formerly W0EEC - CM87tm\n\nSupport Project OSCAR - http://www.projectoscar.net\n\n",
    "attachments": []
}