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/XDHDZZWAJPY57G5KULVIFYULXDJLNTRC/?format=api",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/?format=api",
    "message_id": "[email protected]",
    "message_id_hash": "XDHDZZWAJPY57G5KULVIFYULXDJLNTRC",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/HEO5I63GP6ZFA5OKECHJUHFEDXLHUAY7/?format=api",
    "sender": {
        "address": "w5ggw (a) cox.net",
        "mailman_id": null,
        "emails": null
    },
    "sender_name": "Gregg Wonderly",
    "subject": "[amsat-bb] Re: Email etiquette - was Re:  Re: Moon",
    "date": "2010-04-13T21:42:06Z",
    "parent": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/PUQGROJAYWZPXGDGCLZTDCCUWTR4KYXS/?format=api",
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "\n\nGordon JC Pearce wrote:\n> On Tue, 2010-04-13 at 14:50 -0400, Tom Azlin N4ZPT wrote:\n>> Guess times change. Top posting is the standard on some reflectors. \n>> Especially with folks reading using small screens.\n>>\n> \n> Top posting makes no sense, and on small screens makes it damn near\n> impossible to follow what's going on.\n\nGordon, I think it depends on what you are replying to, and the content you \ninclude.  Sometimes, I have something related, but not point-by-point to say \nabout a post.  Including some context, and top-posting is a smart thing to do in \nthat case, because it lets people read your reply, and if they care about the \nsubject, they can scroll down to see the details that you are replying too.  If \nthey don't care, then no more scrolling is necessary to look for your reply \nverses the content you quoted and posted response to.\n\nGregg Wonderly\nW5GGW\n",
    "attachments": []
}