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/KANYTGOHKMA3TPETL2ZKSTOMDJMR6XSA/?format=api",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/?format=api",
    "message_id": "[email protected]",
    "message_id_hash": "KANYTGOHKMA3TPETL2ZKSTOMDJMR6XSA",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/IVB4NOD323B7SRWQGTA72ZAGMD6C6KPY/?format=api",
    "sender": {
        "address": "zilvinas (a) augma.lt",
        "mailman_id": null,
        "emails": null
    },
    "sender_name": "Zilvinas, AUGMA",
    "subject": "[amsat-bb] Re: Time for a repetion of considerate operating practice on\tFM satellites",
    "date": "2010-09-04T05:59:10Z",
    "parent": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/IVB4NOD323B7SRWQGTA72ZAGMD6C6KPY/?format=api",
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "Ib Christoffersen wrote:\n>  \n>\n> Make the QSO short when the satellite is busy. Valid QSO's just need to\n> exchange calls and signal report. That is it. You do not need locator or\n> operator name. If there is very little traffic OK go ahead and talk about\n> anything - but not when the satellite is busy.\n>\n>  \n>\n> Here in Europe we also have the habit of asking for the full lokator. I have\n> tried to avoid that, but I have failed in this respect. For a terrestrial\n> QSO or in a contest you need the full lokator - but not for a satellite QSO.\n>\n>\n>   \n\nThanks for tips Ib!\n\nI am beginner, but I always was scratching my head why people waste so \nprecious own/other pass time sending/asking  locator ? Sats are just a \nrepeaters! Inevitably we all use computers, internet - we can easy \nlookup for QRA/QTH/Name/etc easily.\n\n73! Zilvinas LY2SS\n",
    "attachments": []
}