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/6WEBARFOR53UZB54UCHHZXJVM3NCFCAC/",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/",
    "message_id": "[email protected]",
    "message_id_hash": "6WEBARFOR53UZB54UCHHZXJVM3NCFCAC",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/6WEBARFOR53UZB54UCHHZXJVM3NCFCAC/",
    "sender": {
        "address": "info (a) dl9dak.de",
        "mailman_id": "44fc1b080273422c8f2a282ec6d05b85",
        "emails": "https://mailman.amsat.org/hyperkitty/api/sender/44fc1b080273422c8f2a282ec6d05b85/emails/"
    },
    "sender_name": "Peter Kaminski",
    "subject": "[amsat-bb] kepler data of AO-73 and Ham Radio Deluxe next pass info",
    "date": "2015-06-16T11:07:24Z",
    "parent": null,
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "Hello,\n\ntoday I received some telemetry frames of FUNcube-1 AO-73 but as I \nchecked the pass in Ham Radio Deluxe Sat Tracking I saw that the next \npass should be in abt. 10 min. later. So I manually reload the Kepler \ndata from www.amsat.org/amsat/ftp/keps/current/nasabare.txt but always \nthere is a big difference between the real pass of AO-73 and the passes \nshown in HRD. I use the latest update of HRD (updating a few days ago).\n\nSo do anyone has the same problem? May be something happend in the HRD \nupdate? The URL of the kepler data is OK because I can finde the file on \nthe amsat server via the link. Any idea? May be I should try another \nkepler data source?\n\nregards\nPeter\nDL9DAK | N9DAK\n\n-- \n\nDL9DAK | N9DAK\nPeter Kaminski\nVogt-Wells-Str. 5\n22529 Hamburg\nGermany\n\nphone:  +49 40 41477811\nmobile: +49 172 4053333\nskype:  peter.kaminski.hh\nemail:  [email protected]\nweb:    www.dl9dak.de\n\n",
    "attachments": []
}