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/PU3VMXXTRZFTESXYA4IG73NACILCLZVG/",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/",
    "message_id": "CH2PR13MB4412C86F5D1F35850C6058FF983E9@CH2PR13MB4412.namprd13.prod.outlook.com",
    "message_id_hash": "PU3VMXXTRZFTESXYA4IG73NACILCLZVG",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/PU3VMXXTRZFTESXYA4IG73NACILCLZVG/",
    "sender": {
        "address": "w1pa (a) hotmail.com",
        "mailman_id": "40f14f46c3444acf902c22b658e82117",
        "emails": "https://mailman.amsat.org/hyperkitty/api/sender/40f14f46c3444acf902c22b658e82117/emails/"
    },
    "sender_name": "Bill Acito",
    "subject": "[AMSAT-BB] Re: Rethinking high power on FM sats",
    "date": "2021-06-01T21:40:12Z",
    "parent": null,
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "All the QSO’s that I am aware of (including FT8 and EME, as examples) require an exchange of calls, one other piece of data, and _confirmation of reception_ to be valid.  I agree with the suggestion to reduce power, but the stomping on QSO’s in progress is bad operating, plain and simple.  Like a DX pile-up, the onus is on the rover to manage the pile-up and over-anxious callers.\n\n\nBill ACITO | W1PA\n\n\n\n",
    "attachments": [
        {
            "email": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/PU3VMXXTRZFTESXYA4IG73NACILCLZVG/",
            "counter": 2,
            "name": "attachment.html",
            "content_type": "text/html",
            "encoding": "windows-1252",
            "size": 1587,
            "download": "https://mailman.amsat.org/hyperkitty/list/[email protected]/message/PU3VMXXTRZFTESXYA4IG73NACILCLZVG/attachment/2/attachment.html"
        }
    ]
}