Show an email

GET /hyperkitty/api/list/[email protected]/email/YWYW5YX76HF5HCGMEU3LHNIYOLBPWTAD/?format=api
HTTP 200 OK
Allow: GET, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "url": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/YWYW5YX76HF5HCGMEU3LHNIYOLBPWTAD/?format=api",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/?format=api",
    "message_id": "CAN6TEUcdbmMRXReUMmyGG4uAqBUKjr5SM28wN7h-vwJbwdoiJA@mail.gmail.com",
    "message_id_hash": "YWYW5YX76HF5HCGMEU3LHNIYOLBPWTAD",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/AX7OESAP6SJPKUTDXESI46SCJW74NM54/?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": "Re: [amsat-bb] North and South Pole Gridsquares",
    "date": "2016-07-25T18:23:51Z",
    "parent": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/KGYIDLRHF32PCHH4YO33XNIZXXKJXKL6/?format=api",
    "children": [
        "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/HZJZ75ZETISSCD6UFKGDXK6KAVWCIWJF/?format=api"
    ],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "Peter,\n\nThe VUCC rules are silent on the maximum number of grid locators\nthat can be given with a single contact. Reading over the latest\ncopy of the VUCC rules I could find, in a November 2014 PDF at:\n\nhttp://www.arrl.org/files/file/DXCC/VHF%20UHF%20Rules20141pdf.pdf\n\nsection 4(e) refers to stations that claim to operate from more than\none grid locator simultaneously. There are two examples cited,\nthe boundary between two grid locators or a four-grid intersection,\nbut the VUCC rules do not state these are the only examples of\noperating from more than one grid locator simultaneously.\n\nVUCC rule 4(f) explains how to document operating from more than\none location, again giving examples of the two most-common ways\nthis would happen (two or four grids). The GPS would need to have\na display with 90 degrees North or South to establish a location\nat either pole. Otherwise, the operator would have to provide\nARRL with other documentation that is sufficient to show the\nstation was at the North or South Pole. Documentation other than\nGPS might require a change in the VUCC rules, in that case.\n\nLogbook of the World, on the other hand, would be trickier. LOTW\nis configured to accept up to 4 grid locators for an individual\nstation location. An operator could attempt to define a series of\nstation locations, covering 4 grids at a time, that will cover all\nof the grids at either pole. Multiple QSOs are currently required\nin LOTW for those operating at a US county or state boundary,\na Canadian provincial boundary, or any international boundary.\nLOTW only allows for 1 DXCC entity, one US county and state, or one\nCanadian province per station location. I know this from my 2010\noperation at the Peace Arch on the Canada/USA border between\nSeattle and Vancouver, operating from a few US state lines, and\na few county lines over the past few years.\n\nThen again, using a QSL card that lists all of the grids covered at\nthe North or South Pole may be easier than trying to make all of\nthe station locations and QSOs to satisfy LOTW. Add in some\nphotos of a GPS receiver on the QSL card, to help anyone who sees\nthe QSL card know where the station was located. :-)\n\n73!\n\n\n\n\nPatrick WD9EWK/VA7EWK\nhttp://www.wd9ewk.net/\nTwitter: @WD9EWK\n\n\n\n\nOn Mon, Jul 25, 2016 at 5:48 PM, Peter Laws <[email protected]> wrote:\n\n>\n> As fun as that would be, VUCC rules only allow for contacts from\n> within a single grid, from the line between two grids, or from the\n> corner of 4 grids.\n>\n> You could always petition the ARRL to change the rules, though.\n>\n>\n",
    "attachments": []
}