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/47C5NKY4COIO2HSRXQMAUWLJ2O3SCWI2/?format=api",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/?format=api",
    "message_id": "[email protected]",
    "message_id_hash": "47C5NKY4COIO2HSRXQMAUWLJ2O3SCWI2",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/HEO5I63GP6ZFA5OKECHJUHFEDXLHUAY7/?format=api",
    "sender": {
        "address": "vk3jed (a) gmail.com",
        "mailman_id": "e049fcabdd4648088cd7ce227ab7c655",
        "emails": "https://mailman.amsat.org/hyperkitty/api/sender/e049fcabdd4648088cd7ce227ab7c655/emails/?format=api"
    },
    "sender_name": "Tony Langdon",
    "subject": "[amsat-bb] Re: Email etiquette - was Re:  Re: Moon",
    "date": "2010-04-13T21:12:58Z",
    "parent": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/GXLDGOBKO2PPMO3NFV3AHK657QQV3R4F/?format=api",
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "At 04:50 AM 4/14/2010, 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\nDoesn't bother me either way, provided people trim unnecessary quotes \nfrom their emails.  I prefer things done in order, like this message, \nbut as long as it's possible to follow the conversation, I'm fine with it. :)\n\nIn order of increasing annoyance:\n\nProperly quoted messages with trimmed quotes.  May be more than one \npart of quoted text with new comments following.  - This is my \npreferred format.\n\nTop posting with quotes trimmed - Also a good option, and probably \nthe easiest for users of Outlook to manage.\n\nNo quoting at all - This can cause confusion, as there is no context.\n\nTop posting without trimming quotes - Now we're starting to waste \nbandwidth, especially on mobile devices.  However, this format is a \ngood one when forwarding emails, and is in common business usage, \nwhere it is often the most appropriate format, e.g. \"Can you please \nrespond to this customer's query...\".\n\nBottom posting without trimming quotes - This is HIGHLY annoying, \nespecially for mobile users.  People reading the email have to scroll \nthrough pages of quotes, to see anything new.  And it's several times \nas many screens on a mobile device to get through all that crud...\n\nImproperly quoted email - Emails where it is difficult to tell quoted \nmaterial from new material (usually because of careless formatting) \nare particularly difficult to follow.\n\nFully quoted email, no new content - Why repost an email without \ncommenting on it?  A total waste of bandwidth, and a waste of the \nreader's time.\n\nIn all cases, quoting of mailing list footers is particularly \nannoying, as this adds no useful value.\n\nThink of your readers.  Email rules are changing, IMHO, and compared \nto traditional \"Netiquette\", you'll notice these tips are very open \nand flexible. :)  We're certainly no longer reading email over a 300 \nbaud modem, but our screen sizes may be _much_ larger (i.e. just \nabout every desktop) or smaller (mobile devices) than the traditional \n40x24 or 80x24 text only formats that were dominant back then.  For \nsome of us, mobile bandwidth does cost serious money.\n\n73 de VK3JED / VK3IRL\nhttp://vkradio.com\n\n",
    "attachments": []
}