Show an email

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

{
    "url": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/IOREHLR5SJKEEWHMYO5VVXNNMUTC3RQK/",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/",
    "message_id": "[email protected]",
    "message_id_hash": "IOREHLR5SJKEEWHMYO5VVXNNMUTC3RQK",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/RW72GIB33VN3LH3FJ7AWDEE34SQEM6UF/",
    "sender": {
        "address": "w2ev (a) yahoo.com",
        "mailman_id": null,
        "emails": null
    },
    "sender_name": "Ev Tupis",
    "subject": "Re: [amsat-bb] Outline: Initiation through Launch & Management",
    "date": "2019-08-13T11:12:49Z",
    "parent": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/D3TISRBE5JBZCTHHN4TIFCKV4MJEBOJ4/",
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": " Had Hans not replied, I'd have missed Daniel's informative post.  I have a feeling I may be missing e-mails from AMSAT-BB. :-/\nHappily, I have some additional reading to do.  Thank you, Daniel!  Also...thank you to Terry (ZL2BAC) for sending me a very interesting on-topic document, directly!\nI wasn't quite sure how to deal with informative, non-snarky responses but I figured it out. Lol.\n\nEv, W2EV\n\n    On Monday, August 12, 2019, 11:44:35 PM EDT, Hans BX2ABT via AMSAT-BB <[email protected]> wrote:  \n \n So what if the satellite was launched by Canada? It's AMSAT-NA, so \nCanada is included (I presume). If the USA has too many restrictions on \nlaunching requirements then go for a non-USA solutionm, I would say. \n(But what do I know? Just looking around the corner).\n\nHans\n\nBX2ABT\n\n\nOn 08/13/2019 06:02 AM, Daniel Kekez via AMSAT-BB wrote:\n> On 2019-08-12 18:20, Ev Tupis via AMSAT-BB wrote:\n>> Is there a general outline of the steps that are followed to get a satellite into orbit?  If so...point me?\n> Each launch provider will publish a Payload Planner's Guide that will\n> describe the environment on the rocket during all phases of launch,\n> which will dictate the minimum testing regime for the satellite. The\n> guide will also include the documentation that must be delivered as part\n> of that process.\n>\n> As an example, Spaceflight Services has a guide for their ride share\n> opportunities:\n>\n> https://spaceflight.com/wp-content/uploads/2019/02/Spaceflight-Mission-Planning-Guide-Rev-G.pdf\n>\n> One also needs to comply with government licensing requirements. In the\n> US that would be the FCC:\n>\n> https://www.fcc.gov/document/guidance-obtaining-licenses-small-satellites\n>\n> And I believe the FCC also requires an Orbital Debris Assessment Report:\n>     https://standards.nasa.gov/standard/nasa/nasa-std-871914\n> But perhaps someone who has gone through the American process can\n> explain it in more detail.\n>\n> Also, if the satellite has a camera, it must obtain a remote sensing\n> license from NOAA.\n>\n> 73,\n> -Daniel, VA3KKZ\n> _______________________________________________\n> Sent via [email protected]. AMSAT-NA makes this open forum available\n> to all interested persons worldwide without requiring membership. Opinions expressed\n> are solely those of the author, and do not reflect the official views of AMSAT-NA.\n> Not an AMSAT-NA member? Join now to support the amateur satellite program!\n> Subscription settings: https://www.amsat.org/mailman/listinfo/amsat-bb\n\n_______________________________________________\nSent via [email protected]. AMSAT-NA makes this open forum available\nto all interested persons worldwide without requiring membership. Opinions expressed\nare solely those of the author, and do not reflect the official views of AMSAT-NA.\nNot an AMSAT-NA member? Join now to support the amateur satellite program!\nSubscription settings: https://www.amsat.org/mailman/listinfo/amsat-bb\n  \n",
    "attachments": []
}