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/YHT6M7WUTPZUS6CJ7JH3GPD63CNRGR3N/",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/",
    "message_id": "[email protected]",
    "message_id_hash": "YHT6M7WUTPZUS6CJ7JH3GPD63CNRGR3N",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/YHT6M7WUTPZUS6CJ7JH3GPD63CNRGR3N/",
    "sender": {
        "address": "hans.bx2abt (a) msa.hinet.net",
        "mailman_id": null,
        "emails": null
    },
    "sender_name": "Hans BX2ABT",
    "subject": "[amsat-bb] non-doppler correction on linear sats",
    "date": "2019-05-09T08:07:37Z",
    "parent": null,
    "children": [
        "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/74VJI6XU2O2UA64X464RH7O2W5C74ZS2/"
    ],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "How to deal with signals (CW/SSB) where the other party doesn't seem to \ndo doppler correction? I use an Airspy/IC820H combo to receive (2m) and \ntransmit (70cm) and both are controlled by Gpredict so that uplink and \ndownlink on linear sats stay in tune. However, I hear many stations that \napparently don't do this and their signals \"walk\" up very fast, right \nout of my passband. Difficult to get their call, let alone have a QSO. \nSo what should be my strategy to deal with this?\n\n73 de Hans\n\nBX2ABT\n\n",
    "attachments": []
}