^You're obviously a more committed than me when it comes to email servers.
Nowadays I'm more inclined to go with an inexpensive email setup through a reasonable hosting company like Dreamhost unless there are very unique or special requirements involved.
IMHO, for vanilla POP, IMAP and webmail it's a lot easier (and cheaper if you value your time at more than $3/hr. ) to farm the "tech part" out, only do the administration - and save your personal hardware and "little gray cells" for something far more interesting than email.
But maybe that's just me.
I've simply been burned too many times by crappy services.
WebHost4Life? Groan... Some of the worst, dishonest, lying, scum.
Layered Technologies? Some of the worst, most incompetent, retards.
I'm skittish about farming some things out. Email for $3? Nah... Too cheap. Scares me.
An email account costs around $100 a year to run if you're running any of the top software. Antivirus will run you $20 to $60. Antispam about the same. The account itself will cost $20 to $40 depending on the number of users you have. It adds up quickly. This is why I don't like to pay for "user" licenses. I like being able to add accounts at a whim.
When I see cheap stuff, it just scares me.
I'm running Windows 2008 R2.
Ah! that explains alot.
PHP is bad enough to get working properly. (Always a plethora of standard components in it that break it entirely on Windows.Biggest problem I've seen with PHP on Windows is most folks either use the installer package, or follow the (quickie way) instructions found online. Both are wrong.
Install only the parts you are going to use (much less attack surface), and put the script extension in the location MS intended...not on the root of the C: drive (Eliminates a ton of before & after permissions issues).
I did a quick bounce into the home lab - This is a clean and lean manual PHP install - IIRC these settings also worked on my current IIS7 (2k8) web server.
These are the Files & File Paths used for the MySQL db &
PHP Script support installation on IIS6 (Webster) <-Old now decommissioned server)
FOR PHP SUPPORT ONLY:
For PHP with MySQL Support ADD These Files:
C:\Windows\System32\libmysql.dll <-"Helper" File, Required for ANY of the Extensions to Work)
IF Using MS-SQL (Which Includes the MSDE Version) ADD These Files:
NOTE: These additional Files are required (in these locations) to load & run the PHP_cURL.DLL module.
At the moment I'm running the new PHP installation under FastCGI with the php-cgi.exe instead of the ISAPI DLL. On my other server I use the ISAPI. Both are the ZIP file and not the installer. FastCGI is supposed to give far better performance (20x?), so that's why I'm running with that.
I must confess though, I prefer to keep C:\PHP as my install location and configure paths instead. It makes for an easier upgrade, and I don't need to "remember" every path and file then. God knows my records are non-existent.
But I've had no real problems other than uncommenting some extensions like php_whatever.dll breaks PHP. They're so horribly documented that it just makes it a nightmare to figure out. A good number of extensions break. And I'm too busy to look into things further for anything but critical extensions, which all seem to work fine.
I only enable PHP for sites that use it though.
I use My Personal Proxy with SSL so I can surf without the ISP snooping on me, but it's a PITA and doesn't really work very well. It's also rather slow. That one is under the ISAPI, but the server is old too, and one of the reasons for the new one. I think it's mostly bad coding though that makes it slow.
My ASP.NET applications on the old server run nicely though.
Anyways, this is way off topic.
Still enjoyable though.
Any reasons why you like PHP in the Windows folder? It just seems somewhat dirty to me and hard to maintain. I've not really seen any practical upshot for it, so I'd love to hear more.