Email Detail
Show an email
GET /hyperkitty/api/list/[email protected]/email/QN5RLO4J3LLYJAUBJA6NVLZQEL2RFWNG/?format=api
{ "url": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/QN5RLO4J3LLYJAUBJA6NVLZQEL2RFWNG/?format=api", "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/?format=api", "message_id": "[email protected]", "message_id_hash": "QN5RLO4J3LLYJAUBJA6NVLZQEL2RFWNG", "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/QN5RLO4J3LLYJAUBJA6NVLZQEL2RFWNG/?format=api", "sender": { "address": "7ndel3fr (a) gmail.com", "mailman_id": null, "emails": null }, "sender_name": "Calvin McDonald", "subject": "[AMSAT-BB] TQSL Support for IO-117", "date": "2022-12-10T04:49:23Z", "parent": null, "children": [ "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/P4FTTWABKLQDPG7KIKGIU2E3JF6BWVE7/?format=api" ], "votes": { "likes": 0, "dislikes": 0, "status": "neutral" }, "content": "I'm getting a bit antsy waiting for the ARRL to update TQSL to support \r\nGreenCube(IO-117), I'm backed up over 100 QSO's now. Digging around a \r\nlittle tonight I see the satellite definitions are stored in TQSL's \r\nconfig.xml file. It would appear that adding a line in this file for \r\nIO-117 is all that would be needed to enable logging QSOs for this \r\nbird. My gut is telling me that doing so is over-simplifying what is \r\nneeded to support IO-117, but thought I'd ask. Can a person just update \r\nthe config.xml file? Why is the ARRL so slow at making this seeming \r\nsimple update?\r\n\r\nN7AY\r\n\n\n", "attachments": [ { "email": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/QN5RLO4J3LLYJAUBJA6NVLZQEL2RFWNG/?format=api", "counter": 2, "name": "attachment.html", "content_type": "text/html", "encoding": "utf-8", "size": 853, "download": "https://mailman.amsat.org/hyperkitty/list/[email protected]/message/QN5RLO4J3LLYJAUBJA6NVLZQEL2RFWNG/attachment/2/attachment.html" } ] }