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/XN2ZGO3EZ6Y7NGV3UNCXILCT6YKK7YPA/?format=api",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/?format=api",
    "message_id": "[email protected]",
    "message_id_hash": "XN2ZGO3EZ6Y7NGV3UNCXILCT6YKK7YPA",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/XN2ZGO3EZ6Y7NGV3UNCXILCT6YKK7YPA/?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]  WD9EWK and LOTW - coming soon",
    "date": "2011-01-17T17:39:33Z",
    "parent": null,
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "Hi!\n\nWith the news last week that ARRL's Logbook of the World now supports \nthe VUCC award, I have started the work to get my satellite QSOs \nuploaded to LOTW.  As I previously mentioned, the ability to associate \nup to 4 grids with a station location will make my work so much easier.  \nGrid-boundary QSOs won't require any extra work to upload.  QSOs from \nother boundaries will still require a little extra work to properly \nrepresent them in LOTW, but that is a small number I can manage.  I \njust renewed the LOTW certificates for all of my calls, and they \ndropped into my e-mail in-box this morning.  Once I load the renewed \ncertificates into the TQSLCert program, I will take my spreadsheet log \nand start making ADIF files for all of my calls and locations I have \nworked from. \n\nI have received QSL cards over the years where my callsigns have /P after \nthem, and a couple where the XE2 comes after my US call and not before it \nas is it listed on my Mexican ham permits for QSOs when I was in Mexico.  \nSince I operate portable almost all the time, I do not identify on the air\nas \"portable\" or \"/P\".  If you have logged QSOs with WD9EWK (or my other \ncalls) with a \"/P\" in LOTW, you will need to correct those entries in \norder to have QSLs in LOTW with me.  \n\nBased on e-mail exchanges with ARRL when I set up my LOTW account in \n2008, there are 5 key elements that have to match in any two LOTW QSO \nrecords to make a QSL.  The call sign is one of those key elements. \nThe others are date, time, band, and mode.  \n\nI will soon upload satellite QSOs to LOTW for these calls:\n\nWD9EWK     (two QSOs from 2000, one from 2003, and a bunch since 2005)\nVA7EWK     (used on my July 2010 trip to Canada)\nCJ7EWK     (used on my November 2008 trip to Vancouver - CJ was a \n            one of the special prefixes available at that time to \n            Canadian hams)\nXE2/WD9EWK (for my 3 trips to Mexico since February 2009)\n\nI have also operated with other call signs in January 2007 (W7W) and \nMay 2008 (K7RDG).  Since I do not hold those calls, I am not able to\nupload anything to LOTW for those satellite QSOs.  \n\nQSOs made from other boundary lines - county, state/province, or \nnational - will require uploading two QSO records to LOTW by *both*\nstations to confirm the contact from both sides of that line.  Each \nof my QSO records for these contacts will be from a station location \non each side of the boundary line.  I have worked satellites from \nthese non-grid boundary lines:\n\nApache/Navajo county line in Arizona (August 2009)\n\nIndiana/Ohio state line (several times since 2006)\nArizona/New Mexico state line (October 2009)\nIllinois/Wisconsin state line (October 2010)\n\nCanada/USA international border (July 2010)\n\nSince the QSO records for the county-line and state-line QSOs would \nhave the same 5 key elements matching, I will vary the QSO time for \nQSOs from one side of the county or state line by one minute (i.e., \nQSO at 2300 UTC from Indiana and 2301 UTC from Ohio).  Otherwise, \nthe second QSO record with the same 5 key elements will overwrite \nthe first QSO record in LOTW with those elements.  The Canada/USA \nborder QSOs won't have that problem, since the calls in the two QSO \nrecords won't match (VA7EWK for one QSO record from Canada, and \nWD9EWK for the other QSO record from the USA).  \n\nI still need to make my initial satellite VUCC application, but want\nto get my satellite activity into LOTW so others may be able to use\nQSOs with me toward future award applications.  I've waited for VUCC\nto be supported in LOTW since I first set up my LOTW account almost 3 \nyears ago, and it is great that it has finally happened.  \n\n73!\n\n\n\n\n\nPatrick WD9EWK/VA7EWK\nhttp://www.wd9ewk.net/\n\n\n",
    "attachments": []
}