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/4ZQBHETY6MST3ERLDXVIB7JC2A5LI2MG/",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/",
    "message_id": "[email protected]",
    "message_id_hash": "4ZQBHETY6MST3ERLDXVIB7JC2A5LI2MG",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/4ZQBHETY6MST3ERLDXVIB7JC2A5LI2MG/",
    "sender": {
        "address": "n4ufo (a) yahoo.com",
        "mailman_id": null,
        "emails": null
    },
    "sender_name": "Kevin M",
    "subject": "[amsat-bb]  DM48 QSOs",
    "date": "2019-04-24T06:44:51Z",
    "parent": null,
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": " Bob, what did you correct? If you upload the EXACT SAME LOG, just sign it with a different location set within TQSL, then it should correct the details of all those already confirmed contacts. I remember making a 'location error' on a grid trip once (might have been county, not grid) and fixed it just as described. The only QSLs that might require some other type of 'fix' beyond that is if the person has already turned in the QSL for VUCC credit (as the incorrect grid) on an application. If you correct things quickly, the likelihood of that is low.\n\n\n\n\nTo everyone who contacted me while I was roving in Capital Reef NP last \nThursday, 4/18... I seem to have fouled up my upload to LoTW, all the \nentries are listed in grid DM58 instead of DM48. I tried to correct and \nupload to LoTW again, but it seems that most of our contacts have \nalready been confirmed on LoTW. I will be happy to send any and all of \nyou a QSL card confirming our contact, unless someone can tell me how to \ncorrect my mistake so you all can get a QSL out of LoTW.\n\nBob N6REK\n\n\n",
    "attachments": []
}