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/TJRVQR5RM2257JJYMLK76V5CBTCWEQUD/",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/",
    "message_id": "[email protected]",
    "message_id_hash": "TJRVQR5RM2257JJYMLK76V5CBTCWEQUD",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/TJ4GSBOKPVADYXCVXWDS4BHMT46XLVG6/",
    "sender": {
        "address": "k5mlt (a) yahoo.com",
        "mailman_id": "c434a4edf1ce442783384353f7f33b65",
        "emails": "https://mailman.amsat.org/hyperkitty/api/sender/c434a4edf1ce442783384353f7f33b65/emails/"
    },
    "sender_name": "Marvin Tamez",
    "subject": "[amsat-bb] Re: LOTW - improperly coded satellite contacts?",
    "date": "2011-02-21T19:30:48Z",
    "parent": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/TJ4GSBOKPVADYXCVXWDS4BHMT46XLVG6/",
    "children": [
        "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/7IKWNO7N535POFVWZFOGIWERFPCPFCMM/"
    ],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "Patrick, I mentioned to Bill earlier, off group, that three of \nmy confirmed QSL's are blank in the \"VUCC\" column. What could have caused that? \nLeaving out Propagation=SAT, maybe? Also on the 10th of this month I started \nusing an ELK-L5 and it has made a noticable difference! Hearing at much lower \nelevations and making QSO's at and below 10*.  Thanks for all your help and \nadvice. \n\n\n73,\nMarvin\nK5MLT\n\n\n\n\n________________________________\nFrom: Bill Dzurilla <[email protected]>\nTo: [email protected]\nSent: Mon, February 21, 2011 11:19:29 AM\nSubject: [amsat-bb] Re: LOTW - improperly coded satellite contacts?\n\nThanks, Patrick,, I have already sent an email to LOTW.  If the other station \nfailed to include Propagation Mode or Satellite Name, there should be no match \nat all.  There is no basis for me to be credited with a 144mhz or 432 mhz grid.\n\nI spent a lot of time going through my log before uploading it, as LOTW demands \nperfection.  The slightest error (e.g., writing vo-52 instead of VO-52, AO51 \ninstead of AO-51) and the entry is rejected.\n\n73, Bill NZ5N\n> \n> Most likely, the other station didn't include one or both\n> of the fields\n> used to mark a QSO as a satellite QSO (Propagation Mode,\n> Satellite\n> Name).  I've seen this on a handful of QSOs I've\n> uploaded in the past\n> few weeks.\n> \n> > Anyone know how this is handled?\n> \n> Assuming your log has all the necessary fields for a\n> satellite QSO (all\n> of the QSLs I've gotten from you are showing as satellite\n> QSOs, so I\n> don't think your logs are missing anything), there is only\n> one way to fix\n> this - the other station has to upload the QSO record(s)\n> again, this time\n> making sure those additional ADIF fields are in their\n> log.  As long as the\n> other QSO details like date, time, your call, etc. are the\n> same, the new\n> upload replaces what was originally uploaded.\n> \n> If the other station's log has the satellite-related\n> fields, then an e-mail to\n> lotw-help @ arrl.org is necessary.  There could be\n> errors in how ARRL's\n> database queries run to match up QSO records and make\n> QSLs.  ARRL\n> will not fix problems with other stations' log uploads, and\n> everything has\n> to be in there correctly in order to use the resulting QSLs\n> toward awards.\n\n\n\n      \n\n_______________________________________________\nSent via [email protected]. Opinions expressed are those of the author.\nNot an AMSAT-NA member? Join now to support the amateur satellite program!\nSubscription settings: http://amsat.org/mailman/listinfo/amsat-bb\n\n\n\n      \n",
    "attachments": []
}