Show an email

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

{
    "url": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/EJFEULND2XR5XE3CQ2UA2FJVCSUP7UDH/",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/",
    "message_id": "00a601c6e327$1cc1f220$0101992c@FRONTDESK",
    "message_id_hash": "EJFEULND2XR5XE3CQ2UA2FJVCSUP7UDH",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/EJFEULND2XR5XE3CQ2UA2FJVCSUP7UDH/",
    "sender": {
        "address": "lu7abf (a) amsat.org.ar",
        "mailman_id": null,
        "emails": null
    },
    "sender_name": "lu7abf",
    "subject": "[amsat-bb]  YES !! RS-15 is alive !",
    "date": "2006-09-28T17:54:12Z",
    "parent": null,
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "Hello Domenico, et all aboard BB\n\nThanks for test and try. Perhaps there is some timer or condition that place/unplace operational the RS-15 transponder, or variable attitude hence antenna position.\n\nWhat I noticed, is that on-off period of beacon is variable, sometimes the cycle is about 1 second on, 7 sec off, under that situation I was not receiving the transponder. The time where I succeed getting back my uplink was when beacon was 10 seconds on and 2 seconds off. Perhaps it varies according to pannels solar exposure.\n\nWhen transponder operating, my CW replicates the same woeing that the beacon has, it means has some fming. \n\nAlso it is possible that command station still has control over RS-15, and can set on or off transponder, or some external event is doing alike effect. That's reason I copied to control station email stated on RS-15 page.\n\nSo, I will keep trying and perhaps we could infere some pattern about transponder operation.\n\n73, lu7abf, Pedro\[email protected]\nwww.amsat.org.ar\n",
    "attachments": []
}