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/2NV4EQD7XBSIILRAEQEFJEAZSPORAJYS/",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/",
    "message_id": "010420072326.15981.459D8D140002A9A500003E6D2206824693969B9DC80D05@comcast.net",
    "message_id_hash": "2NV4EQD7XBSIILRAEQEFJEAZSPORAJYS",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/2NV4EQD7XBSIILRAEQEFJEAZSPORAJYS/",
    "sender": {
        "address": "kb8rtz (a) comcast.net",
        "mailman_id": null,
        "emails": null
    },
    "sender_name": "[email protected]",
    "subject": "[amsat-dc] Re: Impacts?  Missed Discussions?",
    "date": "2007-01-04T23:26:12Z",
    "parent": null,
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "You haven't missed anything in the VHF+ arena. The QRP folks sure went ballistic.\n\nPatrick...kb8rtz...\n\n-------------- Original message -------------- \nFrom: Pat Kilroy <[email protected]> \n\n> HAVE I MISSED ANY DISCUSSIONS or posts on the \n> \"other\" AMSAT mail list(s) regarding the impacts \n> to AMSAT (good or bad, imagined or real) with \n> respect to all the recent changes by the FCC to \n> the Part 97 rules and regs? \n> \n> At first thought, the expansion of the 80m phone \n> band and dropping Element 1 (Morse Code) of the ham \n> license testing requirements, for example, don't \n> appear to affect AMSAT and the amateur satellite \n> service a single bit. But how about after a second \n> thought? \n> \n> Might there be any indirect impacts lurking? \n> \n> Thanks for your thoughts. \n> \n> 73 de Pat N8PK \n> \n> \n> _______________________________________________ \n> Via the AMSAT-DC mailing list courtesy of AMSAT-NA \n> [email protected] \n> http://amsat.org/mailman/listinfo/amsat-dc \n",
    "attachments": []
}