GET

Email Detail

Show an email

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

{
    "url": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/EM5I57VEIA4HWM6FCTJI2IP2GNX6OIDV/?format=api",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/?format=api",
    "message_id": "[email protected]",
    "message_id_hash": "EM5I57VEIA4HWM6FCTJI2IP2GNX6OIDV",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/EM5I57VEIA4HWM6FCTJI2IP2GNX6OIDV/?format=api",
    "sender": {
        "address": "bstrick (a) N5BRG.COM",
        "mailman_id": "953542c988dd4c549175bb02a8a6a1ed",
        "emails": "https://mailman.amsat.org/hyperkitty/api/sender/953542c988dd4c549175bb02a8a6a1ed/emails/?format=api"
    },
    "sender_name": "Bob Stricklin",
    "subject": "[pacsat-dev] Re: Writing to the PacSatx git repository",
    "date": "2023-03-01T15:37:34Z",
    "parent": null,
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "Thanks to all for feedback…\r\n\r\nI can use any of the systems and methods you described Jonathan. My preferred method is fro the command line on Linux but if I get that working I can use MAC too. Windows would be my last choice.\r\n\r\nI have used SSH keys. Let me look into that idea. That would be a good solution if it works.\r\n\r\nNever had any trouble with cloning a repository. The issue is writing and deleting and creating on a repository. I have done all this on my own repository. Burns, since you created PacSatx you are the owner and I would not expect you to have a problem.\r\n\r\nBob\r\n\r\nOn Mar 1, 2023, at 8:28 AM, Burns Fisher (AMSAT) via pacsat-dev <[email protected]<mailto:[email protected]>> wrote:\r\n\r\nI've never had to use a token to clone a repo.  I just did this yesterday with the loader repo that Heimir created.   I just looked in \"Code\" for the URL to clone.  So for pacsatx, it should be\r\n\r\ngit clone https://github.com/AMSAT-NA/PacSatx.git<https://url.emailprotection.link/?buEq4eyNl9NRYRhKUfm4VcEU7nPYElH0fMOcgLdfQqKd4-_qp1P6J2hyvx5HYIn46psONW2RmErQVVoec7it1zA~~>\r\n\r\nChecking something in is a different ball of wax.  However, by \"normal\" personal access token, created in my own account about the time that github stopped allowing the normal password for checkins, seems to work fine.  There is also the public key method, but I think you have to mess around with your local git to make that work.  Or something.  It works for the repos in my own area, but not for the AMSAT-NA repos.\r\n\r\n73,\r\n\r\nBurns Fisher, WB1FJ\r\nAMSAT(R) Engineering -- Flight Software\r\n\r\n\r\nOn Wed, Mar 1, 2023 at 8:43 AM Jonathan Brandenburg via pacsat-dev <[email protected]<mailto:[email protected]>> wrote:\r\n\r\nI am happy to have a look at it. Can you remind me of your environment, please?\r\n\r\nAre you Windows, Mac or Linux?\r\n\r\nAre you using command line, web interface, or a Git client (like TortoiseGit)?\r\n\r\nIs your personal access token one of the fine-grained tokens? (There are a little tricky to use interactively but it can be configured. They must be given access to each individual API call as they are designed for automatic scripts.) Or is this a \"classic\" personal access token? (I know those are discouraged because of the ability for \"lateral movement\" between repositories in an organization.) Or, are you using 2FA? (I believe 2FA is the preferred mechanism for interactive human access).\r\n\r\nThank you!\r\n\r\nJonathan\r\n\r\nOn 2/28/23 20:51, Bob Stricklin via pacsat-dev wrote:\r\nAll,\r\n\r\nI continue to have an issue writing to the PacSatx repository.   Jonathan has adjusted permissions to give me write access. Apparently there is more to it in this case. My use of git has mostly been with a repository I setup or one a company had. In this case it seems several here have owner rights in this repository.\r\n\r\nI have tried with one of my personal access Tokens, but I have seen this from GIT:\r\n\r\nEach token can only access resources owned by a single user or organization. Each token can only access specific repositories. Each token is granted specific permissions, which offer more control than the scopes granted to personal access tokens (classic). Each token must have an expiration date.\r\nCreating a personal access token - GitHub Docs<https://url.emailprotection.link/?b_LuMRoC5h8bQTN2ySNoV2j7SSzxIuvawl9AvqwQ5NiNcheXSPi5ad6lpoiLYS_7EoHdBqPgBqcBmrYGl9TCEOmzdOAGdOHrSj2rNJ0c43m52tUxFfreAFoQbgnnVKr0NY_y4tvYfiUTGlwNJwByMR7VOuwk3vHavT_VU_8vym90CWHaOtBQOf-0YUBHAWCq6rg_JedoP4R20NrmbReQio3MTJtMWVNs79RXJFXtuy_nMd0Z1Xw5ctyR45u44LHTy>\r\n\r\nI have also read it may be possible to access a GIT if you have a project Token and create access with that using:\r\n\r\n\r\ngit clone \"https://my-project:<https://url.emailprotection.link/?bUGyKvxiy3XARL1hpyUkkd27ECbOJxe-qS3Nqu-kpkT9_xhPy1QwQzVbMF8kinUGtVMexFXmYjFDiYMXY9oCCCw~~>[email protected]/my-group/my-project.git\"\r\n\r\nWould anyone that knows the process on how to do this please help with the steps or send me the needed Token so i can gain access?\r\n\r\n\r\nThanks,\r\n\r\nBob\r\n\r\n\r\n\r\n\r\n-----------------------------------------------------------\r\n\r\npacsat-dev mailing list -- [email protected]<mailto:[email protected]>\r\nView archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/[email protected]<https://url.emailprotection.link/?buUg7YY4HZLXKo6ZKNudC8bRTBdOsBlAV5C9rq-aqxOQfa9Eqh8kfGK8xAPNkaYeV4y3Z5HVIEvNBaAimp_ZfFMwcw8QT0XZxGj2iXsHa3mcBRxu810JiHLaLtHS4Ej_7>\r\nTo unsubscribe send an email to [email protected]<mailto:[email protected]>\r\nManage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org<https://url.emailprotection.link/?bO71JCUf8Kb7txAlIoAarNqcIdQhyb8VQQIN4j0Gik24jnwI-Byk6ZVn92BYiD7Bxz61XZBoNoJE1TKqdfKnwFw~~>\r\n\r\n\r\n--\r\nJonathan Brandenburg\r\nRadio Amateur Satellite Corporation\r\n1-214-213-1066\r\n\r\n-----------------------------------------------------------\r\n\r\npacsat-dev mailing list -- [email protected]<mailto:[email protected]>\r\nView archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/[email protected]<https://url.emailprotection.link/?buUg7YY4HZLXKo6ZKNudC8bRTBdOsBlAV5C9rq-aqxOQfa9Eqh8kfGK8xAPNkaYeV4y3Z5HVIEvNBaAimp_ZfFMwcw8QT0XZxGj2iXsHa3mcBRxu810JiHLaLtHS4Ej_7>\r\nTo unsubscribe send an email to [email protected]<mailto:[email protected]>\r\nManage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org<https://url.emailprotection.link/?bO71JCUf8Kb7txAlIoAarNqcIdQhyb8VQQIN4j0Gik24jnwI-Byk6ZVn92BYiD7Bxz61XZBoNoJE1TKqdfKnwFw~~>\r\n\r\n-----------------------------------------------------------\r\n\r\npacsat-dev mailing list -- [email protected]<mailto:[email protected]>\r\nView archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/[email protected]\r\nTo unsubscribe send an email to [email protected]<mailto:[email protected]>\r\nManage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org\r\n\r\n\n\n",
    "attachments": [
        {
            "email": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/EM5I57VEIA4HWM6FCTJI2IP2GNX6OIDV/?format=api",
            "counter": 2,
            "name": "attachment.html",
            "content_type": "text/html",
            "encoding": "utf-8",
            "size": 12544,
            "download": "https://mailman.amsat.org/hyperkitty/list/[email protected]/message/EM5I57VEIA4HWM6FCTJI2IP2GNX6OIDV/attachment/2/attachment.html"
        }
    ]
}