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/MLFEGZA2EDWDVJTSOBNSY2GI3FV45MJ5/?format=api",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/?format=api",
    "message_id": "[email protected]",
    "message_id_hash": "MLFEGZA2EDWDVJTSOBNSY2GI3FV45MJ5",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/MLFEGZA2EDWDVJTSOBNSY2GI3FV45MJ5/?format=api",
    "sender": {
        "address": "billdz.geo (a) yahoo.com",
        "mailman_id": "cf72c3fefd9647e5b0216b2b0300c538",
        "emails": "https://mailman.amsat.org/hyperkitty/api/sender/cf72c3fefd9647e5b0216b2b0300c538/emails/?format=api"
    },
    "sender_name": "Bill Dzurilla",
    "subject": "[amsat-bb]  LOTW - improperly coded satellite contacts?",
    "date": "2011-02-21T14:36:43Z",
    "parent": null,
    "children": [
        "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/NQYTK5QGDK7QHWLS5FHV6DDTL4WBNBON/?format=api"
    ],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "Hi,\n\nI just upload several hundred sat contacts to LOTW.  Many matches were returned, BUT many of them were credited for \"VUCC 144 mhz\" or \"VUCC 432 mhz\" and NOT for \"VUCC Satellite\", which is how they should be credited.\n\nDoes this mean that the person on the other side of the QSO did not properly encode the log entry as a satellite QSO?  Or is there some glitch in the LOTW program?  I would have guessed that, if I encoded the QSO as Satellite and the guy on the other side did not, it would not show as a match at all.\n\nAnyone know how this is handled?\n\n73, Bill NZ5N\n\n\n      \n",
    "attachments": []
}