![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
lorien update -- updated and bumped throughout the day
IMPORTANT! AFFECTS ALL MY USERS!
11 Jan 06 1807 PST:
Had to wrassle OpenSSL to the ground in order to generate keys that said mail.snugharbor.com instead of lorien.snugharbor.com. All e-mail users should enable encryption, but not encrypted authentication, with their POP and/or IMAP services, and should be using mail.snugharbor.com as their incoming and outgoing mail servers, regardless of what domain they use to get their mail. If you need help reconfiguring your mail client, reply here or e-mail me.
11 Jan 06, 1618 PST:
New SMTP authorization via SASL and/or TLS is in place. This means you can configure your mail reader to use authentication and/or encryption to send mail, and it will send things out -- this augments the pop-before-smtp that we were using before that sent passwords in the clear. Did I mention that was bad? 'cos it is.
11 Jan 06, 1330 PST:
Name service is back -- when it wasn't up, mail receipt would have been a bit peculiar, and not worked at all for the mailing lists.
Consequently -- mailing lists are back! Yay!
Next target: web services, including web pages, photo galleries, and webmail.
For those of you who ssh and ftp (if you don't know what they are, you don't care), they're up. The ssh keys have changed, of course, so calm your worried little clients down if they spaz.
11 Jan 06, 1140 PST:
Part of the gyrations that we've gone through means that we now accept... drumroll... Secure IMAP and POP! This means your password need no longer be sent in the clear across the net, that your e-mail will have a harder time being intercepted in transport by nogoodniks, and general privacy prevails. Indeed, non-encrypted IMAP is throwing odd errors and doesn't work; please consider reconfiguring your mail client appropriately if you would like to take advantage of encryption in your e-mail while I work on the plain stuff some more (which you shouldn't use).
As for outgoing e-mail, pop-before-smtp authentication "should" be working as of this update. Please advise if you use me for your outgoing mail server and it used to work, but now is not.
11 Jan 06, 1132 PST:
We are now receiving mail! You may or may not be able to pick it up yet, but it's hitting mailboxes, which means no more mail will be lost--some, from reports, was. Next is to debug POP and IMAP handling.
11 Jan 06, 0251 PST:
Okay, after a lot of fussing about partition sizes, I got lorien to boot with a new OS. After some well-deserved sleep, I get to install apache and postfix... MY WAY. That's tomorrow's Fun and Excitement.
User data came through fine, but it's still unavailable.
As for e-mail, it's supposed to be being queued up on my backup MX host, but this may not have been done successfully. I'm just as screwed as any of the rest of you, and just as pissed about it not working perfectly...
My deepest apologies for all the inconvenience my error has caused. A drink on me, when next we meet!
-- Lorrie, currently playing Sibelius to her Linux server in hopes to awaken its folksoul or summat.
11 Jan 06 1807 PST:
Had to wrassle OpenSSL to the ground in order to generate keys that said mail.snugharbor.com instead of lorien.snugharbor.com. All e-mail users should enable encryption, but not encrypted authentication, with their POP and/or IMAP services, and should be using mail.snugharbor.com as their incoming and outgoing mail servers, regardless of what domain they use to get their mail. If you need help reconfiguring your mail client, reply here or e-mail me.
11 Jan 06, 1618 PST:
New SMTP authorization via SASL and/or TLS is in place. This means you can configure your mail reader to use authentication and/or encryption to send mail, and it will send things out -- this augments the pop-before-smtp that we were using before that sent passwords in the clear. Did I mention that was bad? 'cos it is.
11 Jan 06, 1330 PST:
Name service is back -- when it wasn't up, mail receipt would have been a bit peculiar, and not worked at all for the mailing lists.
Consequently -- mailing lists are back! Yay!
Next target: web services, including web pages, photo galleries, and webmail.
For those of you who ssh and ftp (if you don't know what they are, you don't care), they're up. The ssh keys have changed, of course, so calm your worried little clients down if they spaz.
11 Jan 06, 1140 PST:
Part of the gyrations that we've gone through means that we now accept... drumroll... Secure IMAP and POP! This means your password need no longer be sent in the clear across the net, that your e-mail will have a harder time being intercepted in transport by nogoodniks, and general privacy prevails. Indeed, non-encrypted IMAP is throwing odd errors and doesn't work; please consider reconfiguring your mail client appropriately if you would like to take advantage of encryption in your e-mail while I work on the plain stuff some more (which you shouldn't use).
As for outgoing e-mail, pop-before-smtp authentication "should" be working as of this update. Please advise if you use me for your outgoing mail server and it used to work, but now is not.
11 Jan 06, 1132 PST:
We are now receiving mail! You may or may not be able to pick it up yet, but it's hitting mailboxes, which means no more mail will be lost--some, from reports, was. Next is to debug POP and IMAP handling.
11 Jan 06, 0251 PST:
Okay, after a lot of fussing about partition sizes, I got lorien to boot with a new OS. After some well-deserved sleep, I get to install apache and postfix... MY WAY. That's tomorrow's Fun and Excitement.
User data came through fine, but it's still unavailable.
As for e-mail, it's supposed to be being queued up on my backup MX host, but this may not have been done successfully. I'm just as screwed as any of the rest of you, and just as pissed about it not working perfectly...
My deepest apologies for all the inconvenience my error has caused. A drink on me, when next we meet!
-- Lorrie, currently playing Sibelius to her Linux server in hopes to awaken its folksoul or summat.
no subject
no subject
-- Lorrie
no subject
I can log in now, but still in TF. Do I need to reinstall that, or will it be recovered?
no subject
-- Lorrie
no subject
Which reminds me, call me and tell me where you want lunch from today and I'll conference you in and pay for it. :)
no subject
Lunch? Wha?
-- Lorrie
no subject
no subject
-- Lorrie
no subject
Looking forward to more updates, like "SquirrelMail is working again"... I actually had to do WORK today during the Teleconference of Extreme Boredom.
no subject
-- Lorrie
Just FYI
Take care.
M
Re: Just FYI
Sorry about that. The problem is that it all has to be done yesterday, so I have to work out an order.
-- Lorrie
no subject
Check checking, not meaning to be pushy!
no subject
Again jumping on the bandwagon of "not about to look a gift-horse in the mouth, just wanting to know what's up".
If I'd realized webmail would be down for long, I would have temporarily moved a couple of lists to my gmail account, for a couple things that are time sensitive.
The rest can wait as long as I can pick it up this month, as long as the messages aren't still being lost.
--Ember--
no subject
-- Lorrie
no subject
-- Lorrie
no subject
I'm getting password-incorrect errors on my FTP and email for my 3 domains (sockiipress, spacial-anomaly, johnglover.info) still...should I just assume they're down still, or is it something I need to change on my end? (I have no idea how to enable encryption on Mac's Mail program...) I use Transmit for ftp.
no subject
Under the Mail menu, select Preferences. In the window that appears, select "Accounts" (the white @ on a blue background).
Click the e-mail account you want to twiddle from the choices at the left.
Just right of center, there are three buttons: Account Information, Special Mailboxes, and Advanced.
Click on "Account Information" and change your Incoming Mail Server to mail.snugharbor.com.
Now click on "Advanced". Just below center on this window, you'll see Port: (which should be 110 at the moment) a checkbox saying "Use SSL", and a dropdown of various authentication methods.
Check the "Use SSL" box. The 110 should automagically change to a 995. If you are using IMAP instead of POP, the port values will be different but will still change when you check that box. Authentication: should be Password, if it isn't already.
That should fix it -- if not, let me know!
-- Lorrie
no subject
no subject
-- Lorrie
eudora help
I get this error message - Cert Chain not trusted, Try adding this cert to your cert database for SSL to succeed. Cert Error: Unknown and unprovuded root cert Cert bad:
What do I need to change or tick off?
thank you!
Re: eudora help
-- Lorrie
Re: eudora help
now to debate upgrading.