7/26/2023 0 Comments Quotefix macI still haven't figured out the bugs with lbdb and ABQuery on Snow Leopard yet, but once I get that patched up, we'll be good to go. The code will make urlview compile correctly and run on Snow Leopard (10.6). Well, after a ton of searching, posting to the Mutt Mailing list and what not, Brenden Cully (The maintainer of the fink package for OSX) posted this patch to urlview.c. Unfortunately, urlview crashes if you download the source ( ) and compile it natively on Snow Leopard. and how to make it work with multiple Gmail accounts forwarded to each other - which was my major headache actually). (I'll post more later on how I overcame my objections to it. (That I didn't put there, or at least don't remember putting there.) Thanks Richard. ssh/authorized_keys It worked and life is fine now. the ONLY directory it was going to look in was /root/.ssh/authorized_keys Richard changed this to: AuthorizedKeysFile. After poking around a bit, Richard found the problem: AuthorizedKeysFile ~/.ssh/authorized_keys Because, when SSHD starts up, the sshd_config file was expanding "~/" to the home directory, and since sshd starts as root. I tested this out by moving my authorized_keys file to root's /.ssh directory and it worked right away. every time someone tried to connect to sshd on the SERVER's SSHD debug line, it was trying to access /root/.ssh/authorized_keys. We noticed one line in particular that was bothering us. We start daemons in debug mode, looking at RPM packages (this particular server was running Fedora 10), heck, I was even looking at bugs in SELINUX as the culprit. Richard connects up to my computer, and he has the same problem (can't connect via SSH key), so it's obviously a server problem. what am I overlooking? So I IM'ed a friend of mine, Richard Harman, who is the master of a bunch of things, one of the things is Linuxy, Unixy stuff - at this point I'm at my wits end, and trying to figure it out, I am racking my brain. So, here I am racking my brain, "why isn't this working", darn it. I had: PubkeyAuthentication yes I had the permissions right on all the files, on both the client and the server, yes, I checked this, and that. Seems like a normal thing for a guy with a bunch of Unix machines around the house to do right? Well, apparently it was more painful than I thought. Have fun! Me, I just want a replacement for QuoteFix (a Mail.app plugin that fixes the abomination of top posting).So, earlier today I was setting up some SSH keys to be able to connect back and forth between various machines in my network. If that’s a challenge that excites you, so be it. My recommendation: Figure out exactly what’s not working for you in Mail.app, and ask for help fixing that specific issue. But after some exploration of the options, I’ve got it mostly back to where I had it in Mojave (and which resembles Eudora’s old UI), with only a few minor complaints that are new with Big Sur. I hate the default UX for Mail in Big Sur, which I had to use when I first set up a new M1 MBP. It’s definitely important to experiment with and learn all about the various ways Mail can be customized, especially the built-in UX configuration. In other respects, it’s fine-to-very-good. It handles almost any incoming message format with ease, is generally pretty responsive, and has handled my accounts and email very well for … well, when did Eudora die again? In that time there’s only been brief periods where it was unreliable/crashy, and that was usually due to external factors. There are some UX issues, no doubt, but that was also true on Mojave (my prior version, I skipped Catalina). I don’t get the hate for Mail.app on Big Sur. And most of the others mentioned here, though usually for very brief periods that resulted in quick rejections. I’ve used Outlook for a couple of jobs (on Windows, shudder). I’m a sustaining contributor to MailMate, which I use for some specific secondary email accounts, and hope will evolve into something I want to use full time. I was so excited for Bluto (MailSmith), and was sad when it didn’t make it as a profitable product. I’ve tried a bunch of others along the way. I’ve been using email since the late 80s, and in that time, I’ve only used three email clients “seriously”.
0 Comments
Leave a Reply. |