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/VR2MEUSKYCZ334DHW7CTUDAJ2FBTVMIB/",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/",
    "message_id": "20081029034421.SNWX24054.cdptpa-omta04.mail.rr.com@Dave.san.rr.com",
    "message_id_hash": "VR2MEUSKYCZ334DHW7CTUDAJ2FBTVMIB",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/VR2MEUSKYCZ334DHW7CTUDAJ2FBTVMIB/",
    "sender": {
        "address": "dguimon1 (a) san.rr.com",
        "mailman_id": null,
        "emails": null
    },
    "sender_name": "Dave Guimont",
    "subject": "[amsat-bb] Re: 1.2ghz helix",
    "date": "2008-10-29T03:44:17Z",
    "parent": null,
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "\n>I am almost finished with a 16 turn helix for 1.2ghz.  I am not sure \n>of what type of matching I should use.  Some of designs I have  seen \n>use a flat tab on the first 90 degrees of the helix.  What size \n>should it be?  Is there a better way?  I have a bird 43 with a 1.2 \n>slug for tuning.\n>73 Bob W7LRD\n\nHi Bob,\n\nVery simple to use the flat tap, and just bend it for minimum swr..\nWe've been using it for years....\n\n\n\n\n\n\n            73, Dave, WB6LLO\n                [email protected]\n\n                    Disagree: I learn....\n\n               Pulling for P3E... \n\n",
    "attachments": []
}