The last few days.. err.. may be it's a week now.. I've been setting up my live server on the internet. You may or may not know that I own spiritshigh.com and I run braveandthebold.com but I've recently picked up softwarewithstyle.com for the with:Style product me and my team mates are making.

In short, spiritshigh.com, hosted by betterbox.net at the moment (thanks guys) will no longer be hosting it. I'll host it on my own server. The same server will host softwarewithstyle.com (braveandthebold.com is its own thing.. I just make sure it keeps working for them).

The biggest problem I've had has been POP3 actually. Netscape has the most shitful secure connection support ever. I've struggle to find good secure pop software for the server too. I'm currently using qpopper, which fails any time somebody tries to connect using TLS. So I've given up on that for now. Oh and netscape cannot do APOP. The Bat! does APOP just nicely.

And to top it all off, port 110 isn't allowed through the firewall just yet. And even if it were, APOP wouldn't work for netscape. I'm not sure MacOSX mail does it either.. and I doubt Opera would. Steve's dropping Opera mail any way. Rowan wasn't that impressed with The Bat! oh well, can't win them all.

So this leaves me with a big problem. I don't want plain text passwords going to the server (although, that's what everbody else does) as most linux pop3 software sources said passwords from the PAM database - thus! a person sniffing the plain text password suddenly has shell access.. solution? Well, I may just have to set up disabled accounts just for mail and have shell accounts as something completely different. Something sort of like michaell as the shell, michaell_mail as the mail and michael.lucas-smith as an alias for michaell_mail. At least that will also help reduce spam.