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/6X7QX35VCEEK64763VBBNZVPJKD6WNY4/",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/",
    "message_id": "CDC3C9712D9940AC9B6DB3958B002682@WA4SCA",
    "message_id_hash": "6X7QX35VCEEK64763VBBNZVPJKD6WNY4",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/6X7QX35VCEEK64763VBBNZVPJKD6WNY4/",
    "sender": {
        "address": "APBIDDLE (a) UNITED.NET",
        "mailman_id": null,
        "emails": null
    },
    "sender_name": "Alan P. Biddle",
    "subject": "[amsat-bb] Re: [aprssig] RK3KKPK? (CONNECTED Igates?)",
    "date": "2012-01-29T23:44:56Z",
    "parent": null,
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "Got this from the IGate manager.  Thanks to all who provided the pieces and\nclues needed so track this down.\n\n73s,\n\nAlan\nWA4SCA\n\n==============================\n\nSubject: Re: I-Gate\n\nI see what happened. RK3KPK is a BBGATE user who frequently \ntelnets or netroms\ninto BBGATE. He's a curious follow who stumbled across the gateways \nRF port servicing the APRS packets on 144.390. That port has not, \nyet, been restricted. So, when\nrk3kpk checked the heard list on the port, he thought there were lots \nof keyboard\nstations available for contact. Ergo, he attempted to initiate a \nconnection in hopes\nof chatting with a 'local' laptop or tnc. There's nothing clandestine \nabout his activity.\nIf anything, it's my bad for leaving that RF accessible to the \ngeneral ham community. As it turns out, I believe he as been the only \nuser who actually tried going out on\nthat port to connect with INDIO or any other station listed on the \nAPRS port heard list.\n\nGood catch guys.\n73, Jack \n\n\n",
    "attachments": []
}