Saturday & Sunday (trip report)

By Saturday afternoon I’d had enough of the heavy rain and idiot drivers; I just missed contributing to a multi-car pileup on I-40 near Wallace. (Do not tailgate in heavy rain showers.)

I arrived in Wilmington, checked in to the hotel, and went looking for food. I pigged out – at Smithfield’s BBQ. Real eastern NC bbq is the one food I can’t readily reproduce in Jersey, thus the quick feast. After that it was time to explore the downtown a bit, take a few photos, and off to the theater.

I was in Wilmington to see “1776”, with lifelong friend Robin Dale Robertson in a substantial role – he played Mr. Thomson, clerk to the Continental Congress. Kudos for him for finding a role which allowed him to read his lines – every time!

The play was staged in the Ballroom/City Council Chamber space at Thalian Hall. Thalian Hall, built in 1858, has always combined the theatre with the city government of Wilmington. The staging allowed for a “House” seating area of two rows of seats on either side of the main floor (I was seated second row center on the far side); and a cabaret-style “Senate” area in the center – mixing actors and audience together. My rough count is there were 150 seats for the audience – thus a small show.

The staging made the action more interesting; the cast was generally excellent although a few actors were singing way too loud for the space. 1776 is a long show; it ran four hours and a bit on Broadway (I saw it in 1972 near the end of its run); this show clocked in close to five hours as some time was used at the start for a charitable fundraiser pitch… and more time used at intermission to take souvenir photos (or perhaps they were alibis!).

Sunday morning found a break in the clouds, and it was off to Salter Path (actually Pine Knoll Shores) for the Road Scholar Program. Since I had most of the day free before registration (4pm at Trinity Center) I decided to do a bit more photography, and check out the areas. It’s been three years since I was down here, and yes – there have been some significant changes.

I turned off in Jacksonville to take NC-24 up to the beach, and along the way stopped by the Cedar Point Wildlife Trail (part of Croatan National Forest) to see how the hurricane had affected the area. The damage is noticeable – a lot less trees in many areas, and most of the snags are gone. With the snags (dead trees still standing) gone, the ospreys have retreated to areas well back in the preserve.

But with a medium telephoto lens, and by carefully listening to calls, I was able to find a juvenile pair. I contemplated getting the big (500mm) lens out but it was starting to spit rain again, and that lens is not weather resistant. So I stayed with just the one photo of the pair:

Of course, as soon as I left it cleared up a bit, so I swung north on NC-58 to see about getting good photos of the oldest church in the vicinity – the 1815 Hadnot Creek Primitive Baptist church. When I got there, after a few perimeter shots and a ‘hope-it-works’ shot through the window, a car pulled in behind me. The woman (a neighbor) decided I was just a photographer, and tipped me to the cemeteries hidden behind the church.

After this, it was off to Trinity Center for a weak of Road Scholar. Photos from that tour, along with a review, will be in a forthcoming post.

First trip of 2019

So it was time to travel. Part of the rationale for leaving the college classroom was to allow for more flexibility in travel plans – thus time to test that out. I decided to give Road Scholar a whirl.

Road Scholar is the marketing name for Elderhostel, which organizes tours for older people to various locales, and around varied themes. My parents went on 27 such adventures over a ten-year span, and quite enjoyed most of them… back in the late 80s and early 90s. Nowadays the organization is vastly larger and attempts to appeal to a broader audience (hence the name change). I decided on a tour “Historic Homes and Gardens of NC’s Crystal Coast” – in that I knew it was in driving distance, I was familiar with the area, and it was relatively inexpensive. Continue reading First trip of 2019

Blowing in the wind

As mentioned before, in January my parents switched over to Optimum for TV/Internet/Phone. It’s been quite the journey thus far.

First there was the substantial delay in getting a phone number ported over. Then in late February the TV began to pixelate like mad – and after a flurry of calls and resets and two different service visits, the drop line (from pole to house) was replaced – and it seemed all was well.

Yesterday saw high winds (25 mph sustained, gusting to 50) for several hours, and service became unreliable, before ceasing entirely around 10pm. Checking Optimum’s [useless] website via cell service showed “all is well” in the system. This morning, under clear skies and a near-calm situation, service has returned.

In class I used to joke with a name of “Optimum Offline” – I’m beginning to realize my business experience with the company bears little resemblance to the travails of the residential consumer.

 

Updating the platform

Recent visitors should note the removal of advertising – I have upgraded to a paid account here. This site is now accessible via several methods:

  • custom domain: avoiceinthewoods.com
  • redirect: blog.woodall.com
  • direct: woodallrvcc.wordpress.com

This will be my first ever domain with “domain privacy” enabled – I’ll see if that actually does anything to slow the spammers.

More posts coming soon.

Phone number Phollies

After six years on FiOS, the parents decided it was time to move on – rates up, customer service non-responsive (it’s difficult for older people to deal with fast-talking jargon-spilling agents on the phone).

So they moved to the other choice, Optimum.

Optimum isn’t.

Oh, the Internet is fast, and the TV works ok. But there’s a little problem of moving a phone line. Or really, just a phone number. And on that simple issue, Optimum can’t manage. So far, it’s taken eight phone calls (over three hours aggregate on hold)… and we’re still not there.

The latest (as of 1/7/2019) is that 1) we need another phone line(?); 2) that will add $15 to the monthly charges; 3) they need to install a second modem(???), and 4) they scheduled the appointment without bothering to tell us about it (found out via a call in to them).

So… as of now, we’re waiting. I’ll update this when there’s a resolution.

A proper email client

After a month of testing, I’ve found a proper email client. It meets my requirements – runs on Android phone, works with a blended IMAP/POP server, connects only when necessary to poll mail, has reasonable controls.

The winner is: K-9 email. Free, open-source, supports all that I need, free, can auto-thread received mail, easy to operate, and well-documented for advanced features.

Reading the fine print

Upon contemplation, blaming a time zone issue for the mail server problem just doesn’t seem right. Email works just fine across all the various time zones; why should it fail over something so simple?

When I “solved” the problem it was by updating the time zone, and bringing the server into proper sync with the client. But why would this be needed? As I made the change, I noticed something else unusual – there was a persistent connection to my mail server’s IMAP port, from the Amazon cloud. That struck me as odd, and potentially undesirable. So I closed the connection, and waited… and it reestablished itself within seconds. I put this down to being the tech-support diagnostic from the email client vendor, and then went about the business of kicking them off the server (write email to them, remove the extra account created for them, changing master passwords). As always, when I’ve opened a diagnostics port for outsiders, when it’s finished I go back and reset any master passwords which might have been [inadvertently] exposed – in this case, the password to my primary email – access to which had been the impetus for the whole exercise.

Changing the password on that email requires updating not just the mobile client on the phone, but also the mobile clients on the notebook computers, and the POP3 client on the administrative computer.  It’s an easy routine; pull up the client, stop the automatic message pull (which will fail as the password has changed), then make the change, do another message pull to validate, and we’re done.

Not so, this time. Instead, upon updating the password in the POP3 client, I get a “server closed connection” message. What? Did I type the password wrong? Let’s go try that again… get the same error… but that’s the wrong error for a password change. So it’s off to the mail server console to see what’s happened now – and the primary email account is now on ‘auto-ban’ status, meaning too many attempts were made with the wrong password in too short a time frame. I remove the account from auto-ban, do the POP3 pull from the client (works fine), then check the phone app.

It’s complaining it can’t connect. And that’s when it hits me – that persistent cloud connection was from the phone app. But why would it care? I’ve told the phone app to poll the server every 15 minutes… let’s fire up wireshark and do some packet analysis, see what’s happening. And sure enough, it’s the phone app, probing the mail server every 60 seconds for new email. Say what? And then I notice the section on the app menu, about privacy, and look in there. “Erase your data from our servers” – ahem. What data are you storing? Selecting Yes to “Erase data” tells me I may no longer use this app, and when I persist, it deletes the account from the app – resetting it back to the beginning.

Let’s go examine that app again… I should have been a bit more aware (read the fine print!) as to what was going on; how did a no-ads-install-for-free app have a dedicated tech-support team, without a visible source of revenue? Well, if you’re not paying, you’re the product, not the customer. In this case, the company providing the app is indeed reading the mail and making marketing trend analysis data available – to third-party [paying] clients. That’s how the app makes money.

I’d complain about deceptive advertising but… GMail is essentially the same. So Edison Email comes off the phone, and it’s time to find a better client.

Time and the ancient email server

For the past few days I’ve been chasing a rather pernicious problem – email clients weren’t interacting properly with the server. Since I haven’t changed the server software in, oh, five or six years, my first thought was – there’s something crazy going on with the clients.

As of this writing (November 2018) I run my own primary email server. It’s been a stable platform for years, requiring only very intermittent maintenance. However, it’s an older product, running on a non-supported platform. I run in a blended mode; the server is nominally IMAP4 but when I’m in the office I’m retrieving messages using the older POP3 protocol – which then removes the messages off the server. I’m used to this routine (23 years and counting) and it limits message exposure to only a few hours under most circumstances.

The symptom was – the phone email client showed unread messages on the server, but gave me no way to access them. Over the period of a few days I narrowed it down to a specific sequence – leave a few messages on the server, off to bed, wake up in morning, check mail and find the unread and inaccessible new mail… which then caused me to do a POP3 run and retrieve stuff. But this wouldn’t do for the long run. I experienced the same phenomenon on Edison Email (Android) and on GMail (browser and Android client).

The Edison Software app has excellent tech support – and during the various steps they went through (including establishing a test account on my server) – I finally recognized the problem. My server had already executed the reset to standard time – two weeks early. Once I reset the server back to daylight time, things are back to working normally. Then it was time to track down the timezone file and fix that, so this won’t be a problem (at least for the next several months).