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/SV7MHR3FLO2ZVLOJQWKEVCHWIGDUBPPL/?format=api",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/?format=api",
    "message_id": "7D00B788D5DA4A12AC4D8356406EA745@QUECREEK",
    "message_id_hash": "SV7MHR3FLO2ZVLOJQWKEVCHWIGDUBPPL",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/SV7MHR3FLO2ZVLOJQWKEVCHWIGDUBPPL/?format=api",
    "sender": {
        "address": "wb3jfs (a) cox.net",
        "mailman_id": "bdfc678d05af4f3f96c14d823fd3fbcf",
        "emails": "https://mailman.amsat.org/hyperkitty/api/sender/bdfc678d05af4f3f96c14d823fd3fbcf/emails/?format=api"
    },
    "sender_name": "Jeff Yanko",
    "subject": "[amsat-bb]  Sat QSOs and LoTW",
    "date": "2009-11-04T11:16:11Z",
    "parent": null,
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "Hi all!\n\nI just uploaded my satellite QSOs from early July to now to the LoTW.  A \ntotal of 158 with a match of 10, or 6.3%.  Not very good.  I understand that \nLoTW is good for DXCC and WAS, but not available to VUCC.  This could be why \nmany satellite ops opt not to partake in this program.  It's ashame that \nVUCC was never implemented into the LoTW from the get-go.  I've asked the \nARRL about this and never received what I would call a justifiable answer \nbut they did say they were working on offering LoTW to a non-ARRL award late \nthis year or early 2010.  Just my observation.\n\n\n73,\n\nJeff  WB3JFS\n\n \n\n\n",
    "attachments": []
}