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/CMSZP4CROPNCHG53SCMURSMTYB2SCOSC/",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/",
    "message_id": "[email protected]",
    "message_id_hash": "CMSZP4CROPNCHG53SCMURSMTYB2SCOSC",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/CMSZP4CROPNCHG53SCMURSMTYB2SCOSC/",
    "sender": {
        "address": "JamesDuffey (a) comcast.net",
        "mailman_id": "16d2718d7d4a47dca8f564d867aacfe2",
        "emails": "https://mailman.amsat.org/hyperkitty/api/sender/16d2718d7d4a47dca8f564d867aacfe2/emails/"
    },
    "sender_name": "James Duffey",
    "subject": "[amsat-bb]    RX only satellite?",
    "date": "2007-02-07T02:34:00Z",
    "parent": null,
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "\nIt would be interesting to look at the NCDXCC HF beacons from space to \nget an idea of ionospheric absorption.  These have predictable times \nand variable predictable power levels, so path losses can be easily \ncalculated.\n\nMonitoring the 10M frequency at 28.200 might provide useful information \nfor future Mode A applications. With beacons all around the world, \nbroadcasting every 3 minutes at known power levels, a 28.2 MHz receiver \ncould provide a wealth of information. The beacons ID themselves, so \ndata analysis should be easy; all that would be required is some sort \nof time tagging. I suspect that the satellite would never be out of \nrange of a beacon.\n\nHow much data storage is available?  I need to calculate how much data \nyou would need to  obtain.\n\nIt would be interesting to launch these satellites at various points in \nthe solar cycle. - Duffey KK6MC/5\n\n\n",
    "attachments": []
}