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/6MGOGA47NF4M6FKX5D3I6QTZIUEGIB7D/",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/",
    "message_id": "[email protected]",
    "message_id_hash": "6MGOGA47NF4M6FKX5D3I6QTZIUEGIB7D",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/6MGOGA47NF4M6FKX5D3I6QTZIUEGIB7D/",
    "sender": {
        "address": "summit496 (a) live.com",
        "mailman_id": null,
        "emails": null
    },
    "sender_name": "Kevin Deane",
    "subject": "[amsat-bb] Email via ISS/APRS",
    "date": "2012-01-06T01:56:42Z",
    "parent": null,
    "children": [
        "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/7XN64IMDP726DUBLJTSA5MNKZGZLD54D/"
    ],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "\nOk so I think that this all fine and dandy and even more so if it keeps people from logging into the BBS and ruining the pass for everyone else. I dont think that an email sent via ISS would be considered a Qso but still pretty neat. In between the beacons there are Two Way Communications made on the ISS Digi.\n \nWhat I do not understand is the Beaconing. What is the point? So that while you are at work, or sleeping, your callsign shows up on arris.net? In doing so you Beaconers not only clog up the passes but have basicly killed NO-44.\n \nIf you are going to use the ISS or a satellite you should be there at your station and not be like the very annoying automated menu you get when trying to get through to a human being on the phone.\n \nBy the way Unproto CQ via WIDE2-2 or RS0ISS-4  then k or CONVERSE  :EMAIL    :[email protected] Type mess here works great there is no need for the Beacon...\n \nJust my opinion.\n\nKevin\nKF7MYK\n\n \t\t \t   \t\t  ",
    "attachments": []
}