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/DZNA52HCNA6EY7EQ3PSXTJ2BN6RRMUKK/",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/",
    "message_id": "[email protected]",
    "message_id_hash": "DZNA52HCNA6EY7EQ3PSXTJ2BN6RRMUKK",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/DZNA52HCNA6EY7EQ3PSXTJ2BN6RRMUKK/",
    "sender": {
        "address": "n4ufo (a) yahoo.com",
        "mailman_id": null,
        "emails": null
    },
    "sender_name": "Kevin M",
    "subject": "[amsat-bb]  Can QSO's be manually input to LOTW?",
    "date": "2017-05-05T17:10:44Z",
    "parent": null,
    "children": [
        "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/QXJ2KAMLD77NWNGLMLWJKUSURVJ4HNZM/"
    ],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "I might share a trick that I use for satellite logging using TQSL. Instead of creating a new file each time you can click on:\n\nFile > Edit Existing ADIF File... > then open a previously created file.\n\nWhat file? Well instead of just using a single file for ALL satellite contacts, I have a file for each bird. That way, after a pass, I merely open the file for the corresponding satellite, then I click the >>| button that takes me to the end of the file. I click ADD QSO and then I enter the callsign, change the time and date and save. By having one file for each satellite, when I add a new QSO, I don't have to re-enter the bands, prop mode, satellite, etc.\n\nIt may not be as easy for everyone, but for me it makes logging after a pass, extremely simple. Just a note, this method is for home logging only... for rover ops, I have to keep separate files for each location. But those details for another time. also, I archive my files at the end of every year to keep size down.\n\n\n73, Kevin N4UFO\n",
    "attachments": []
}