New job

Gad. I almost got forcibly retired a month ago. Previous employer been having trouble all year about keeping me billable. Multiple hiccups caused me to be on overhead almost five months.

At my skill/experience level, that's expensive for them, so in October I went on unpaid LOA. That's a gamble by everyone that work is going to show up. My suspicion was not, so I didn't wait around much.


Now don't get me wrong, here...it's not that I *wanted* to get a job again. I'd have rather retired officially, but I can't quite afford that yet (recall that a move is occurring) until I sell the old house--once that's done I can retire when I feel like it.

New job is forcing a 25% pay cut on me, tho. That stings a bit. Again, once the old house is sold, that won't matter too much. But still...

That said--new job is properly interesting. Have a software AND hardware problem to solve. And multiple installations eventually, altho not too many. [Later: weird prime contractor goings on--this is dead.]

And its a really different tech area than I've done before, which means new learning and challenges.

[Update: it's a tiny business, maybe 10 employees. Luckily, a couple of them are fans of ethnic foods, as I am, so there's a small crew for lunch daily. That hasn't happened in >8 years. Yay!]

-----

While I was on LOA I started building the barn. Regrettably that's Plan C. Plan A was someone else builds a metal building. Plan B was someone else builds a wood building. Plan C was I built the wood building because I can't afford to pay anyone else; of course in the end that means I can say "I built it". It also means that if it falls down "I built that". So I've been getting a crash course in construction on this. Mistakes so far are minor, other than the weird need for after-the-fact anchor bolts into the concrete foundation. You really want to do that when its poured. Now I have to drill for them. If I had to do it over again, I'd go with cinder block walls, pay an expert to do that.

[Update: the walls went up in Nov. The roof trusses went up after xmas. The metal roofing went up a few days later. I am not the monkey I used to be for climbing on that stuff. Not quite done as of Jan 1, but not too much left. Eventually I'll put solar panels on it, probably 3kW.]

-----

Much later: turned out this job was really a bad idea. 11 months after I started it, and not quite six months after it ended, I *STILL* do not have a W2 for 2016. I am not sure if that equals stupid incompetence, criminal incompetence, or both, but it's damn sure incompetence. Some of the payroll taxes weren't even paid to the IRS. That's borderline criminal incompetence.

And there were never any paystubs I could fake/create a W2 from. So I have no info about withholding.

I may be having to sue them here shortly.

Odd trouble with Apple Mail

Various Mac users in the extended family. Have been for years (since the late 80s for me).

So I've a lot of experience with nearly every version of OS Apple has ever produced.

My mom bought a new Macbook in the summer. Her old machine was getting flaky, it was like 10 years old, so not a huge surprise.

Her old OS was 10.4, new OS is 10.11 (El Cap).

She's using Apple Mail. I have occasionally used that in the past, but only on my Powerbook laptop, and even then only on vacation, where email need was limited at best.

Mom's email flakes out regularly, refusing to send to the SMTP server. So I have gotten a lot of "tech support calls" from her about this, and I haven't really been able to solve it. Have spent time on the phone with her ISP, and with Apple, trying to figure this out.

IT SHOULD NOT TAKE AN ADVANCED DEGREE(TM) TO FIX THIS.

Except that apparently it does. Pay attention to get yours.

So here's what is going on (Apple guy didn't know this stuff, ISP guy hinted at it):

Apple Mail ("AM") auto-configures an account for you based on an email address you give it when you first start it up, and you can add more later that will also auto-configure. OK, that's friendly, you don't have to be an expert on setup to get going on your brand-new machine.

AM now knows how to handle additional mail flavors, so you can do IMAP as well as POP. These two things aren't the same however, so it's interesting that it auto-configures for you. SMTP has gotten fancier over the years with security settings, and that's where the problem starts.

The long-term problem is that it continues to try to auto-configure for you--any time there's a glitch between your machine and the server, it attempts to re-auto-configure the entire account. This is a thing that AM didn't used to do, so it took me a long time to figure it out.

Well, the odds of that working right are probably slim. Fortunately, it looks like you can turn this off, which is probably the right thing to do immediately. There's a check-box on your account settings about "auto-configure" that you really want un-checked.

The problem mom was experiencing is that the auto-configure was going from port 587/password/SSL to port 25/MD5/SSL, and the ISP just doesn't do that. And AM wouldn't let go of it most of the time. The ISP does not change it settings. Not ever. Yours doesn't either.

And this "re-auto-configure" would take place any time there was any kind of comm hiccup between AM and ISP/SMTP server. This was, I believe, the real problem. Mom's ISP is just not able to keep up with its workload, then there are comm-channel hiccups, if you try to send email during one of those hiccups it tries to reconfigure the comm scheme by choosing some other settings, that fails because the ISP only uses the one group of settings

It seems like sometimes it would recover ok (like the settings got changed back ?!), outgoing mail would finally transmit, and then later there'd be another hiccup, outgoing mail wouldn't go out, and this would last for hours or even days.

So what you need to do is turn off the auto-configure-settings on your email accounts. Once you have the right settings, don't let AM change them again.

A few weeks after that discovery I found the help web-page on the ISP's own site that explained this whole things with pictures and red circles over the naughty check-box.

---

What's also interesting here is that I still have an account with that same ISP, for a few more months. I don't use AM, I use SeaMonkey (altho not for much longer, as it's degraded, because it's a Mozilla product, (see other blog on that topic)). SeaMonkey is a whole different program, doesn't do this auto-configure at all. And I'm not using the same program settings anyway--I use the POP service, weaker security, etc., and virtually never have trouble at all--certainly nothing like what mom has had.

So I've convinced myself that it's this auto-configure that starts with what WAS once good settings, and gets stupid about them, and doesn't recover.

So turn that off. Bad dog.