Re: [PLUG] email issues
I put my charter IP address into http://mxtoolbox.com/SuperTool.aspx and received info that my IP address was blacklisted ... on the Spamhaus ZEN blacklist. I have no idea what that means. I assure you no one in this household is doing bad stuff on the internet. Charter support told me to contact my router manufacturer (Why, I wonder?). The quote I got from Charter was "There is no way to assign this issue as it does not involve accessibility of services. And would not be able to further escalate the issue." I see it as involving accessibility of services ... my charter email does not work, but I have had no success explaining that. Have I lost Charter as my cable provider? Does anyone have advice on what I can do? -mark -Original Message- From: PLUG On Behalf Of Ben Koenig Sent: Tuesday, January 2, 2024 1:02 PM To: Portland Linux/Unix Group Subject: Re: [PLUG] email issues On Tuesday, January 2nd, 2024 at 12:10 PM, markcasi...@comcast.net wrote: > I am unable to send charter ==> comcast > > But I can send > charter ==> IEEE, which is auto forwarded ==> comcast. > That makes it look like comcast is having an issue specifically with charter. I would be curious to know if you can receive mail from other charter accounts. Is there anyone else you know on that service who can send you a test? What's also odd is that you are not having issues with forwarded emails or the PLUG mailing list. PLUG sends emails on behalf of the sender which can cause some email services to silently reject the message. I have a similar issue on this proton account when other proton users post to PLUG. It is possible that comcast is refusing to accept that the issue is on their end because something they expect to see is missing from your charter message headers. The trick is getting past their T1 support team and getting someone who will actually diagnose the issue. Failing that, your only other option is to lawyer up. -Ben
Re: [PLUG] Pacific Telephone ...
On Thu, Jan 4, 2024, 18:48 Keith Lofstrom wrote: > [...] > > I wonder if Ainsworth paid royalties to Bell ... > > I watched a fun talk at 37c3 about keeping rotary dial phones functional in a modern world: https://media.ccc.de/v/37c3-11716-analog_rotary_phones_get_a_second_life_with_raspberry_pi The speaker suggested that someone else altogether invented the telephone, which might be well known, but if I ever knew it I had forgotten it. It is in the first part of the talk. The rest is fun too. I opened an issue on his GitHub requesting that he "TAKE MY MONEY", which he closed after a few days as resolved, which is not quite true, since he hasn't taken my money yet. Lol.
Re: [PLUG] Pacific Telephone ...
On Wed, Jan 03, 2024 at 10:53:21PM -0800, Russell Senior wrote: > Pacific Telephone and Telegraph Company --(1961)--> Pacific NW Bell > --(1988)--> US West --(2000)--> Qwest --(2011)--> CenturyLink (which ... Thanks, Russell. This Wikipedia article: https://en.wikipedia.org/wiki/Pacific_Bell#Northwest_acquisitions says: "Acquisitions over the years extended Pacific Telephone's territory into Oregon, Washington, and northern Idaho" It would be interesting to learn about the Oregon companies that Pacific Telephone and Telegraph acquired. According to the Oregon History Project: "Pioneer steamboat captain George Ainsworth brought the first telephone to Oregon in 1878, just two years after Alexander Graham Bell patented the new technology. The first telephone conversation in the state took place in Portland between Ainsworth and his wife on a line that connected his office with his home." I wonder if Ainsworth paid royalties to Bell ... This paywalled Jstor article: https://www.jstor.org/stable/20611147 ... points to a December 1938 Oregon Historical Quarterly article, which I don't have time to read. Perhaps not relevant to PLUG and Linux, except that I imagine the geeks who cobbled up Portland's first telephone systems were a lot like the geeks who cobbled up Portland's first hobby computer networks a century later (without involving steamboats). Perhaps Portland geeks will cobble up the first telepathy networks a few decades from now, though I fear that future spam will be canned meat composed of our brain cells. - Perhaps I have more important things to think about, like configuring SVG-image math equations in my own experimental mediawiki instances. Wikipedia uses a mathoid server, but I'm aiming for standalone content that I can also deploy on net-disconnected laptops. Keith -- Keith Lofstrom kei...@keithl.com
Re: [PLUG] fdisk not recognizing external SATA HDD
"PRO TIP: Connect JUST the USB adapter - no drive - and check dmesg. It should not disconnect (just show 'media removed') and the USB adapter MUST be listed in 'lsusb'. For example, for my 3.0 USB adapter." I didn't see this mentioned or perhaps you already now, but the best way to see log mssgs realtime is the command: tail -f /var/log/messages Here's the command output when I disconnect and reconnect my usb speaker. Link] on usb-:00:1d.0-1.2/input0 Jan 4 16:46:34 mc-bunsen kernel: [16035.930728] usb 3-1.2: USB disconnect, device number 7 Jan 4 16:46:38 mc-bunsen kernel: [16039.479790] usb 3-1.2: new full-speed USB device number 8 using ehci-pci Jan 4 16:46:38 mc-bunsen kernel: [16039.594705] usb 3-1.2: New USB device found, idVendor=05a7, idProduct=40fe, bcdDevice= 1.00 Jan 4 16:46:38 mc-bunsen kernel: [16039.594714] usb 3-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Jan 4 16:46:38 mc-bunsen kernel: [16039.594717] usb 3-1.2: Product: Bose Micro SoundLink Jan 4 16:46:38 mc-bunsen kernel: [16039.594721] usb 3-1.2: Manufacturer: Bose Corporation Jan 4 16:46:38 mc-bunsen kernel: [16039.594723] usb 3-1.2: SerialNumber: Q1222049006784949K80080 Jan 4 16:46:38 mc-bunsen kernel: [16039.618227] input: Bose Corporation Bose Micro SoundLink Consumer Control as /devices/pci:00/:00:1d.0/usb3/3-1/3-1.2/3-1.2:1.0/0003:05A7:40FE.000C/input/input51 Jan 4 16:46:38 mc-bunsen kernel: [16039.676337] hid-generic 0003:05A7:40FE.000C: input,hiddev2,hidraw5: USB HID v1.11 Device [Bose Corporation Bose Micro SoundLink] on usb-:00:1d.0-1.2/input0 Also, check to see if the drive shows up in your bios prior to OS bootup. For example, when I want to boot off a usb thumb drive, it has to bee seen and mounted by the BIOS during initial hardware boot-up. HTH
Re: [PLUG] NON-ANNOUNCEMENT ANNOUNCEMENT: PLUG vs UnPLUG this month?
In case Michael is not able to secure his plans in time, let's meet at the Lucky Lab Brew Pub in Southeast like we did a couple months back. 7pm tonight Lucky Labrador Brew Pub 915 SE Hawthorne Blvd, Portland, OR 97214 On 1/2/24 14:15, Russell Senior wrote: Michael and I were talking about what was going to happen this month. Last month, I had threatened to give a talk about my ancient tape recovery adventure, and I was considering what it would take to pull it together when it dawned on me that I probably won't be in town that day, as I am committed to going to Seattle on January 4, our nominal meeting night. We have Michael and the venue is available, but we (afaik) have no speaker, and I am sadly not available to organize an UnPLUG. In other news, there are some hopeful murmurs about getting back into the PSU Engineering Building to use as a meeting venue, but so far they are just murmurs and further murmuring is on hold for the next couple weeks. I'll pipe up if there is more progress on that front.
Re: [PLUG] fdisk not recognizing external SATA HDD
On Thu, 4 Jan 2024, King Beowulf wrote: As Russell mentioned, your USB adapter is disconnecting, that is why /dev/sdg is AWOL. Are you sure you are plugging into a the correct port? Bad USB adapter? Ed, The disconnect was intentional. When fdisk -l did not display /dev/sdg/ after several attempts I gave up for the day. PRO TIP: Connect *JUST* the USB adapter - no drive - and check dmesg. It should not disconnect (just show 'media removed') and the USB adapter *MUST* be listed in 'lsusb'. For example, for my 3.0 USB adapter Will do this. Thanks, Rich
Re: [PLUG] fdisk not recognizing external SATA HDD
On Wed, 3 Jan 2024, Russell Senior wrote: The last message seems to say that the USB device disconnected a couple minutes after it was plugged in. Russell, Yes, that's when I shut it down. The dmesg log was from my earlier attempt; will re-do today. The sd in sdg stands for scsi disk. Prior to nvme, in Linux, storage tends to be treated as scsi disks because regardless of connection technology (USB, SATA, SAS, etc) the underlying commands sent to devices were scsi commands. Thanks for clarifying. Rich
