![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
lwoodIMPORTANT! 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.
