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/6GH5VRWMFRVLA3RMVH4MDPSNLINYPUGQ/?format=api",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/?format=api",
    "message_id": "[email protected]",
    "message_id_hash": "6GH5VRWMFRVLA3RMVH4MDPSNLINYPUGQ",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/6GH5VRWMFRVLA3RMVH4MDPSNLINYPUGQ/?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: OT: Universal Text Messaging and Pagers (WAS Re: Re:dream)",
    "date": "2009-07-07T23:58:18Z",
    "parent": null,
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "At 04:05 AM 7/8/2009, [email protected] wrote:\n\n>So let's say I know your personal capcode - I send to you making a \n>call up now \"KF8II de KD8BXP pls call on 40meter 7.100 at 2200z\"\n>\n>I think that would be 100% legal. So it is all about content and not \n>about the techonolgy of it being a oneway device\n\nI'd agree with this logic.  It is establishing a QSO, albeit on a \ndifferent frequency.  Similarly, a pager could be used to send signal \nreports, when there's only a 1 way path.  For example, I can hear \nsomeone on HF, but they can't hear me, I could send a page saying \"UR \n5x1, can't reply, amp no go\" .  Now this is becoming a real time, \ncross band, cross mode QSO, and those ARE legal. :)\n\n73 de VK3JED / VK3IRL\nhttp://vkradio.com\n\n",
    "attachments": []
}