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/V2N4UU3TFRFZBYGW6JRKIN3ILI3RFD5S/?format=api",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/?format=api",
    "message_id": "[email protected]",
    "message_id_hash": "V2N4UU3TFRFZBYGW6JRKIN3ILI3RFD5S",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/V2N4UU3TFRFZBYGW6JRKIN3ILI3RFD5S/?format=api",
    "sender": {
        "address": "brad.wf7t (a) gmail.com",
        "mailman_id": "30aea8cbc9994a4fb1c24af05c2b99ac",
        "emails": "https://mailman.amsat.org/hyperkitty/api/sender/30aea8cbc9994a4fb1c24af05c2b99ac/emails/?format=api"
    },
    "sender_name": "Brad WF7T",
    "subject": "[amsat-bb] Fwd: Polluted time server causing issues with digital\tmodes",
    "date": "2018-04-01T05:37:26Z",
    "parent": null,
    "children": [
        "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/5RWX6BREK2UHXTLY7DSHZKQM5YMXNAOS/?format=api"
    ],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "I am forwarding this for anyone interested. I think my discovery is correct \nand invite additional review/scrutiny. \n\n73 Brad WF7T\n\nOn Sunday, April 1, 2018 at 12:21:36 AM UTC-5, Brad WF7T wrote:\n>\n> *I have discovered a polluted time server that is wreaking havoc with \n> time-synced digital modes, and worse. For everyone using round-robin style \n> time synchronization like Dimension 4, please remove the following time \n> server: rackety.udel.edu <http://rackety.udel.edu>.* It is consistently \n> sending time sync corrections that are between 10 and 41 seconds different \n> than every other SNTP server in the world. This will cause your PC clocks \n> to skip this amount and stay that way until another time sync occurs, e.g. \n> 5 to 15 minutes later, causing another massive time correction by another \n> accurate time NTP server. Please pass this information along to all \n> digital-active hams.\n>\n> While this amount of time is not of any consequence for RTTY, PSK and the \n> like, this behavior is detrimental to WSJT and QRSS modes. Terrestrial WSJT \n> modes like FT8, WSPR, Meteor scatter MSK144, and EME modes fail to decode \n> and will cause out of sequence transmissions.\n>\n> I also noticed a number of out-of-sequence FT8 tranmissions on 40M this \n> afternoon (BTW, open early to EU), which clued me into the situation. This \n> messed up time server could have been a contributor.\n>\n> *Remove or disable the following server: rackety.udel.edu \n> <http://rackety.udel.edu>.* Apparently it has been getting increasingly \n> worse since 3/8/2018 or so. I only discovered this tonight while I was \n> decoding WSPR on 474.2KHz (630M) and saw a huge time jump and lack of \n> decodes of some fairly strong signals. \n>\n> And yes, this is also an InfoSec problem. Time bases are important for \n> MANY Information Security purposes, but beyond the scope of this discussion.\n>\n> Excerpts of my Dimension4 time-base logs below. Please contact me with \n> questions/comments.\n>\n> 73 Brad WF7T\n> Nashville, TN\n>\n> --- \n>\n> ... First noted occurrence in my time-base logs\n>\n> 2018-03-07 10:36:44.461 -7.962988e+000 rackety.udel.edu SNTP <-- 7 second \n> correction\n> 2018-03-07 10:39:52.480 7.980464e+000 clock-1.cs.cmu.edu SNTP <-- fixed \n> on next round-robin sync\n>\n> ... Persists for a second day, appearing to get worse\n>\n> 2018-03-08 09:17:25.217 -1.015543e+001 rackety.udel.edu SNTP <-- 10 \n> second correction\n> 2018-03-08 09:20:35.240 9.963055e+000 clock-1.cs.cmu.edu SNTP <-- Fixed \n> on next round-robin sync\n>\n> ... Jump ahead a week; yup, getting worse\n>\n> 2018-03-15 05:34:10.880 -1.761963e+001 rackety.udel.edu SNTP <--  17 \n> second correction\n> 2018-03-15 05:37:29.176 1.812267e+001 ntp.cais.rnp.br         SNTP <-- \n> Fixed on next round-robin sync\n>\n> ... Skipping ahead to tonight; SNAFU\n>\n> 2018-03-31 23:29:34.849 -4.165045e+001 rackety.udel.edu SNTP <-- 41.6 \n> second correction!\n> 2018-03-31 23:33:35.421 4.192192e+001 ntp2.kansas.net SNTP <-- fixed on \n> next round-robin sync\n>\n>\n",
    "attachments": []
}