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/YJTEEU4XK4RVA3FKJUB7X2OKOXHXDHF4/?format=api",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/?format=api",
    "message_id": "[email protected]",
    "message_id_hash": "YJTEEU4XK4RVA3FKJUB7X2OKOXHXDHF4",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/YJTEEU4XK4RVA3FKJUB7X2OKOXHXDHF4/?format=api",
    "sender": {
        "address": "amsat-bb (a) wd9ewk.net",
        "mailman_id": "21664df01bef4757931b7cdb42a9e768",
        "emails": "https://mailman.amsat.org/hyperkitty/api/sender/21664df01bef4757931b7cdb42a9e768/emails/?format=api"
    },
    "sender_name": "Patrick STODDARD (WD9EWK/VA7EWK)",
    "subject": "[amsat-bb]  Now that LOTW has caught up with my uploads...",
    "date": "2011-01-27T15:56:07Z",
    "parent": null,
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "Hi!\n\nIt looks like LOTW took about 5 minutes or so after I shut down \nlast night to get the rest of my uploads processed.  The numbers\nnow stand at 9911 QSO records, with 1332 QSLs (13.4% confirmation \nrate).  I also had to adjust the ruleset for my VUCC \"account\" based\non activity in and around Phoenix, since it was picking up at least\na couple of QSOs I know would be outside the 200km limit in the VUCC \nrules.  I'm now at 87 grids confirmed for my Phoenix-area activity, \nbased on LOTW QSLs.  Not enough for a VUCC application solely on LOTW\nQSLs, but not bad considering VUCC just became an option through LOTW.  \n\nI spent almost as much time last night getting the last 2100 QSOs\nuploaded as I did the other evening working on the larger part of\nmy log, since I had more station locations to define.  I made 60\nuploads in total last night.  Some of those locations only had a \nhandful of QSOs, and a couple had exactly one QSO.  I had to redo\na couple of uploads, since I fat-fingered the grids for a couple \nof the station locations (locations at 4-grid intersections - ones\nthat really need to be done carefully). I also found that I had to \nupload some QSO records again, so I could have a station's call with \n\"/P\" after it.  I expect this will probably be the main reason I won't \nsee some QSLs; not having the appropriate indicator added to a \nstation's call.  This is not a big deal, as I can make a new QSO \nrecord and quickly go through the process to upload the additional \nrecord.  If you think there should be QSLs with any of my calls that \nyou are not seeing, please e-mail me directly so we can take a look at\nspecific instances. \n\nOnce SO-67 is supported by LOTW, I can upload those QSOs.  Then my \ncomplete satellite log will be there.  I will upload my future satellite \nactivity to LOTW periodically, and hope to go through my logs to get 6m \nactivity and possibly other contest logs I have in electronic form up \nthere.  And, soon, save enough pesos to make my initial satellite VUCC \napplication, plus a lunch for my friendly card checker as he goes through \nall of those cards.  :-) \n\n73!\n\n\n\n\n\nPatrick WD9EWK/VA7EWK\nhttp://www.wd9ewk.net/\n\n\n",
    "attachments": []
}