About Geoffrey Leach

There appears to be no way to edit a message once you go to 'preview'   If I post <code> with html content, the post is rejected for 'invalid' html.  ... View more

Problem: Connecting (only) to Amazon, (any) page hangs attempting to download (apparently) an image from images-na.ssl-images-amazon.com. Download succeeds for a dozen or so jpegs, then it hangs. Problem appears to be independent of browser (chrome, firefox) and OS (Linux Fedora 32 and Windows 7).. Sky is clear, view unobstructed. Connection to Huhges modem is hard-wire through Netgear R7000 modem.   Problem first noticed June 11.   I realize that round-trip times can very significantly, but this is unusual, as it happens only with amazon.com. Are thre any user-accessible facilities that might assist in diagnosing the problem? ... View more

I'm reliably informed that this wget works when run through another ISP. I might add that from my system, accessing other podcast providers works OK.   wget --no-check-certificate -vvv -O ml https://www.podtrac.com/pts/redirect.mp3/pdst.fm/e/chtbl.com/track/8G441/traffic.megaphone.fm/WWO7230198885.mp3 --2021-04-29 08:48:06-- https://www.podtrac.com/pts/redirect.mp3/pdst.fm/e/chtbl.com/track/8G441/traffic.megaphone.fm/WWO7230198885.mp3 Resolving www.podtrac.com (www.podtrac.com)... 54.200.97.37, 52.24.105.221, 44.231.197.162 Connecting to www.podtrac.com (www.podtrac.com)|54.200.97.37|:443... connected. HTTP request sent, awaiting response... 302 Found Location: https://pdst.fm/e/chtbl.com/track/8G441/traffic.megaphone.fm/WWO7230198885.mp3 [following] --2021-04-29 08:48:11-- https://pdst.fm/e/chtbl.com/track/8G441/traffic.megaphone.fm/WWO7230198885.mp3 Resolving pdst.fm (pdst.fm)... 216.239.36.21, 216.239.34.21, 216.239.32.21, ... Connecting to pdst.fm (pdst.fm)|216.239.36.21|:443... connected. HTTP request sent, awaiting response... 302 Found Location: https://chtbl.com/track/8G441/traffic.megaphone.fm/WWO7230198885.mp3 [following] --2021-04-29 08:48:15-- https://chtbl.com/track/8G441/traffic.megaphone.fm/WWO7230198885.mp3 Resolving chtbl.com (chtbl.com)... 13.249.48.69, 13.249.48.62, 13.249.48.37, ... Connecting to chtbl.com (chtbl.com)|13.249.48.69|:443... connected. GnuTLS: Error in the pull function. Unable to establish SSL connection. ... View more

My medical provider has an interface that mediates between provider and client. It is, as you might immagine, behind a firewall. When a provider sends a message to a client, the system sends a "You have mail" email to the client, using regular email protocols.   My issue is that much of the time the email that they are supposed to send does not appear in my HughesNet mailbox.   Wonderful opportunity for finger pointing?   In response to my request for a log, this is what I received:   You can let your email provider know that our email notifications are sent from the following email address: MYCHART.SUPPORT@UCDMC.UCDAVIS.EDU The SMTP response codes for the emails sent to your email address indicate that the messages are being successfully delivered from our system to their recipient email server. The most recent email message sent to you was on 10/22/20 at 5:25 pm Pacific time.   Is it possible to use this data to determine what might have happened? FWIW, I clear my mailbox hourly and delete messages once they are downloaded. The referenced email is not in my trash folder. ... View more

A piece of outgoing mail was (apparently) rejected by the hugshnet mail system. Short version:   This message was created automatically by the mail system (ecelerity). Received-SPF: softfail (smtp02.hughes.cmh.synacor.com: transitional domain hughes.net does not designate 184.53.48.217 as permitted sender)   FWIW, my assigned IP is  184.53.48.9   Long version: here are the headers   From: Mail Delivery System <postmaster@hughes.net> To: geoff@hughes.net Subject: Mail Delivery Failure Date: Tue, 21 Apr 2020 06:08:10 -0400 This message was created automatically by the mail system (ecelerity). A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: >>> oriana@almagourmet.com (while not connected): 554 5.4.7 [internal] exceeded max retries without delivery ------ This is a copy of the headers of the original message. ------ Return-Path: <geoff@hughes.net> X-Authed-Username: Z2VvZmZAaHVnaGVzLm5ldA== X_CMAE_Category: 0,0 Undefined,Undefined X-CNFS-Analysis: v=2.1 cv=Zb69TphA c=1 sm=0 tr=0 a=alMjyCJoxyUBoW4irxABtg==:117 a=alMjyCJoxyUBoW4irxABtg==:17 a=L9H7d07YOLsA:10 a=9cW_t1CCXrUA:10 a=s5jvgZ67dGcA:10 a=kj9zAlcOel0A:10 a=g-rBkFOlAAAA:8 a=inrySznMs_wvFKEwMCYA:9 a=N4bSDcBWTFA8dNBa:21 a=7gj18nmP-8DkfkB9:21 a=CjuIK1q_8ugA:10 a=-qui4eJqTRsA:10 a=yfmmBuS0vy3znAOsZFac:22 X-CM-Score: 0 X-Scanned-by: Cloudmark Authority Engine Authentication-Results: smtp02.hughes.cmh.synacor.com smtp.mail=geoff@hughes.net; spf=softfail; sender-id=softfail Authentication-Results: smtp02.hughes.cmh.synacor.com header.from=geoff@hughes.net; sender-id=softfail Authentication-Results: smtp02.hughes.cmh.synacor.com smtp.user=geoff@hughes.net; auth=pass (LOGIN) Received-SPF: softfail (smtp02.hughes.cmh.synacor.com: transitional domain hughes.net does not designate 184.53.48.217 as permitted sender) Received: from [184.53.48.217] ([184.53.48.217:31452] helo=puget.mtranch.com) by smtp.hughes.net (envelope-from <geoff@hughes.net>) (ecelerity 2.2.3.49 r(42060/42061)) with ESMTPSA (cipher=AES256-SHA) id F4/1A-21554-15F9B9E5; Sat, 18 Apr 2020 20:46:14 -0400 Date: Sat, 18 Apr 2020 17:46:01 -0700 From: Geoffrey Leach <geoff@hughes.net> To: "Oriana" <oriana@almagourmet.com> Subject: Re: Order Update Message-ID: <20200417191030.414d74b7@puget.mtranch.com> In-Reply-To: <02c401d614e7$fea9a560$fbfcf020$@almagourmet.com> References: <02c401d614e7$fea9a560$fbfcf020$@almagourmet.com> X-Mailer: Claws Mail 3.17.4 (GTK+ 2.24.32; x86_64-redhat-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit   ... View more

Telemedicine requires real-time video and audio interchange with a medicalprofessional. Its becomming more common, especially these days. My experience with on attempt at a telemedicine session suggests that satelite latency makes this impractical, at best.   Questions: is my diagnosis of the problem correct? If so, would a short-term (say 30 min) bandwith increase be practical. Might there be other solutions? ... View more