Show an email

GET /hyperkitty/api/list/[email protected]/email/G7DFBJO3WP336FYBVY3BA4NKHRIWC5G3/
HTTP 200 OK
Allow: GET, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "url": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/G7DFBJO3WP336FYBVY3BA4NKHRIWC5G3/",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/",
    "message_id": "000901c6f29e$df894e30$f5e8230a@notepad8",
    "message_id_hash": "G7DFBJO3WP336FYBVY3BA4NKHRIWC5G3",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/ABM4LAMZ3D6GN4O4IS4BLBR7RGGTGY6H/",
    "sender": {
        "address": "eagle (a) howardlong.com",
        "mailman_id": "a9c59876bf364a4fb3565b10d9755577",
        "emails": "https://mailman.amsat.org/hyperkitty/api/sender/a9c59876bf364a4fb3565b10d9755577/emails/"
    },
    "sender_name": "Howard Long",
    "subject": "[eagle] Re: S1 downlink coordination and interference mitigation",
    "date": "2006-10-18T10:19:15Z",
    "parent": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/5JAOOMK5YHLKED33CRV2KXO65IMZYUXZ/",
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "Hi Grant\n\n> The linear transponder on ESEO will also be \n> 'as close to 2400 as possible'.  Given that \n> the orbits of ESEO and Eagle are planned to \n> be fairly similar (low inclination GTOs AFAIK) \n> I would assume that the downlinks won't overlap, \n> as there will be times when both satellites \n> will cover the same footprint?\n\nI am sure that this will be taken into account, including the possibility of\nDoppler overlap expecially if one is approaching and the other receding.\nPerhaps a few more kHz too for crystal instability.\n\nI originally raised this point of using the WiFi guard band really because\nit's a way of mitigating at least somewhat against interference, so that if\nanyone had any further comments I thought raising it here was as good as\nany. As I understand it, Eagle frequencies are definitely not set in stone,\nand paperwork needs to be formally submitted from AMSAT-NA/Eagle for IARU\ncoordination. As the Eagle proposals are now ratified by the BoD, it was\nuseful for Graham Shirville to be able to put it in the mix for other known\nS1 requirements, including ESEO and P3E, prior to a formal request.\n\n73 Howard, G6LVB\n\n",
    "attachments": []
}