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/NU4MGECAS4G2YXF2MI2CREOFMNPZ66E3/",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/",
    "message_id": "[email protected]",
    "message_id_hash": "NU4MGECAS4G2YXF2MI2CREOFMNPZ66E3",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/NU4MGECAS4G2YXF2MI2CREOFMNPZ66E3/",
    "sender": {
        "address": "k6yk (a) juno.com",
        "mailman_id": "9dd495eb5a5b4400ad5e4ad998068d9f",
        "emails": "https://mailman.amsat.org/hyperkitty/api/sender/9dd495eb5a5b4400ad5e4ad998068d9f/emails/"
    },
    "sender_name": "John W Lee",
    "subject": "[amsat-bb]    SAT contacts and eQSL (And LOTW)",
    "date": "2008-02-11T03:22:21Z",
    "parent": null,
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "Hello Jay, \nI dread getting into this discussion because it will cause an \navalanche of e-mail! \n\nFirst of all,  E-QSL's  don't count for any meaningful awards. \nToo bad.  It would be nice if they did.\nI still upload my logs every month faithfully year after year. \n\nLOTW confirmations DO count for DXCC and WAS.\n\nI spent a lot of time figuring out what it took to get satellite \nQSO's uploaded that actually were correct. \n\nI don't know how many log programs actually export all the correct\nrequired info for satellite contacts.  My program does not, so what I've\nbeen doing is this:  Exporting the non-satellite contacts and satellite\ncontacts\nseparately.  This way I can massage the ADIF file to make the satellite \ncontacts correct for LOTW and E-QSL.\n\nSatellite contacts need to have some additional information: \n1. The  \"band\" or \"freq\"  should be the UPLINK frequency (your transmit).\n2. Then you need \"band_rx\"  <band_rx:4>70CM, for instance.\n3. Then you need \"sat_name\"  <sat_name:5>AO-51 for instance.\n4. Then you need \"prop_mode\"  <prop_mode:3>SAT  for instance\n\nAny contacts that match all the correct info will be confirmed as\nsatellite\nQSO's. \n\nThese changes in the ADIF  file are not hard to do unless you operate on\na lot \nof different satellites then you have to do them in bunches.   Recently\nall of my \nSat QSO's are on mode J \"V/U\"  so I just have to do a wholesale \"add in\"\nof the\n\"band_rx\" and \"prop_mode\" part on every QSO.\n\nWhen I log the QSO's in the computer I put the sat name  in the \"comment\"\nfield.\nSo when editing I do a wholesale change (search & replace)  \"comment\"  to\n\"sat_name\".\n\nNot a big job, and it makes things work.  I've got a few countries\nconfirmed on \nLOTW for satellite QSO's but I have a feeling there are a lot of folks\nthat uploaded\ntheir stuff without the required info, so the confirmations don't happen.\n\nAnd I get a ton of  \"70CM\" and \"2M\"  FM   E-QSL's which I know are not\nright.\n\nAlso, I went and exported all the AO-40 QSO's, fixed the file up, sent it\nin to LOTW \nand don't think I got a single confirmation on any of it.  Too bad again!\n\n\nDoes this help ? \n\n73,\nJohn, K6YK\n",
    "attachments": []
}