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/QQUPC2CWIT4KBTPPT3WAVIFAEZ5BFMHB/",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/",
    "message_id": "CAJsuqdC4TR-ESbRGvpride7H3gd9r5xyo5WUfNd4aYm1yV8O0w@mail.gmail.com",
    "message_id_hash": "QQUPC2CWIT4KBTPPT3WAVIFAEZ5BFMHB",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/QQUPC2CWIT4KBTPPT3WAVIFAEZ5BFMHB/",
    "sender": {
        "address": "vk5qi (a) rfhead.net",
        "mailman_id": "23dad5aadd4c40f18b8b50ca734586c2",
        "emails": "https://mailman.amsat.org/hyperkitty/api/sender/23dad5aadd4c40f18b8b50ca734586c2/emails/"
    },
    "sender_name": "Mark Jessop",
    "subject": "[amsat-bb] CAS-6/TIANQIN-1 TT&C Frequency or Object Number?",
    "date": "2020-01-08T00:29:47Z",
    "parent": null,
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "Hi all,\n\n>From this article, it looks like the CAS-6 payload V/UHF antennas on\nTIANQIN-1 haven't yet been deployed:\nhttp://www.arrl.org/news/view/camsat-says-cas-6-activation-for-amateur-use-has-been-delayed\n\nI'm wondering if TIANQIN-1 is beaconing on any other frequency? Clearly the\ncontrollers are getting data from the sat somehow.\n\nI have identified a few objects from the same launch transmitting on the\n400-403 MHz TT&C band, though none of these have been named in the\ncatalogues (as seems to be typical for Chinese launches). In particular, I\nhave seen:\nObject 44884 - 401.548 MHz\nObject 44886 - 401.951 MHz (This is apparently a rocket body)\nObject 44887 - 401.951 MHz\nObject 44889 - 401.750 MHz\n\nI'm wondering if any of these are TIANQIN-1 .. if the operators of the sat\nhave an object number, it would be great if they could share it, so we can\nat least point our antennas in the right direction!\n\n73\nMark VK5QI\n",
    "attachments": []
}