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/S7PBWHHVUCY5JTRFAC2EGMM67A5ZFHJN/",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/",
    "message_id": "[email protected]",
    "message_id_hash": "S7PBWHHVUCY5JTRFAC2EGMM67A5ZFHJN",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/S7PBWHHVUCY5JTRFAC2EGMM67A5ZFHJN/",
    "sender": {
        "address": "kd6pag (a) amsat.org",
        "mailman_id": null,
        "emails": null
    },
    "sender_name": "John Mock KD6PAG",
    "subject": "[amsat-bb] Re: QSL card exchange",
    "date": "2008-03-29T03:32:26Z",
    "parent": null,
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "I've had very good luck with US and Canadian QSL cards.  My experience with\nMexico is too limited to draw that much of conclusion (but lately i've been\ngetting a fair number of them).  In fact, i get ALOT of cards that i don't \nask for; people seem to like to send me cards even when i check 'TNX' on \nmy card when i know that i don't need their grid and/or state.  \n\nI'm not so good at QSLing promptly, as i record each pass i operate and then\ncarefully transcribe them [when time permits].  But everyone gets a card\nfrom me the first time i work them in (or from) a new grid.  I find that\neasier than trying to keep track of who needs which cards.  So if you don't\nhear me on the air for awhile, that's probably because i have gotten too far\nbehind in QSLing.\n\nHere's what i do that works well for me.  I print my own cards from the QSO\ndata on 4x6\" card stock and accurately trim to post card size.  (Alot of \nfolks don't want your card sticking out of an otherwise neat stack of cards.)\nSince i'm frequently roving, i include both my operating location, six-\ncharacter grid square and GPS co-ordinates.  There are a couple of graphics\nand some lettering is colored.  Perhaps most importantly, i add a personal\ncomment to each card, even if it's just the other station's grid square and\nbest wishes.\n\nIn addition, as well as the usual 'Thx' and 'Pls QSL', there is also a box\nmarked 'LoTW' which is checked whenever the QSO data has been already been \nuploaded to ARRL at the time the card was printed.  Also, for QSLs on grid\nsquare boundaries, i often include a picture taken from QSO location, which\ncould be compared to satellite images (such as Google maps) or topographic\nmaps to help verify that i was operating from two [or more(!)] grid squares\nat once.  (I probably should include the county and power level [available\non LoTW] but that would require a re-design of my cards.)\n\nThe other thing i do when i want a card back is to include a self-addressed\nenvelope and 'loose' postage.  This way, the receiver can use the postage\nand still have the choice of using my envelope or their own.  For Canada,\ni order Canadian stamps on-line.  (I don't have a good source of Mexican\npostage, but i make an effort by including the corresponding US postage\nwith the notation \"for your next USA SASE\".  Stamp trades are welcome.)  \nAt the moment, US amateurs get an extra 1 cent stamp to they can respond\nconveniently even after our postal rates go up [again].\n\nBasically, i go through a fair amount of work to produce and mail the cards \n(much of which was a once-only task [programming]).  People seem to respond\nto that effort.  Compared to what i've heard from most HF'ers, i am quite\npleased with (and also proud of) efforts that satellite operators make to \nQSL.\n\t\t         -- KD6PAG  (Networking Old-Timer, Satellite QRPer)\n",
    "attachments": []
}