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/6VDHGQTBWKUMFVVEUVT2QCCBAABOULKP/?format=api",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/?format=api",
    "message_id": "[email protected]",
    "message_id_hash": "6VDHGQTBWKUMFVVEUVT2QCCBAABOULKP",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/ME5NCUIQUUPZ5LK7NTDAULVD2PWM3U5T/?format=api",
    "sender": {
        "address": "lucleblanc6 (a) videotron.ca",
        "mailman_id": "9e00802147284c40880480833e06c230",
        "emails": "https://mailman.amsat.org/hyperkitty/api/sender/9e00802147284c40880480833e06c230/emails/?format=api"
    },
    "sender_name": "Luc Leblanc",
    "subject": "[amsat-bb] Re: 1.2ghz helix",
    "date": "2008-10-29T08:02:09Z",
    "parent": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/ME5NCUIQUUPZ5LK7NTDAULVD2PWM3U5T/?format=api",
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "On 29 Oct 2008 at 2:58, [email protected] wrote:\n\n> I am almost finished with a 16 turn helix for 1.2ghz.  I am not sure of what type of matching I should use.\n> Some of designs I have  seen use a flat tab on the first 90 degrees of the helix.  What size should it be?  Is there a better way?  I > have a bird 43 with a 1.2 slug for tuning.\n> 73 Bob W7LRD\n> \nHere is a clever way to match an helix  http://helix.remco.tk/  For 1.268Ghz a 3\" tube od with caps seems to fit near the formulas \ndimension. The problem is the stub foil dimension on 1.268Ghz could be a pro rata of the S band will be good enough?\n\nExperts idea are welcome with figures for a L band model\n\n\n\n\n\"-\"\n\n\nLuc Leblanc VE2DWE\nSkype VE2DWE\nwww.qsl.net/ve2dwe\nWAC BASIC CW PHONE SATELLITE\n\n \n\n",
    "attachments": []
}