SereBlue

To have SSL on a site, I'd need a dedicated IP number for that domain. I understand (correct me if I'm wrong) that if I have more than one domain for which I want SSL, I have to have a dedicated IP number for each domain. Do I also need a dedicated IP number for each subdomain that has SSL? For instance, given that I want to serve the following from my hawkhost account: https://project1.mydevelopmentdomain.tld https://project2.mydevelopmentdomain.tld https://www.myproductiondomain.tld https://myproductiondomain.tld How many dedicated IP numbers would I need? And does the answer change depending on whether I have separate certs for project1 and project2, or have a wildcard cert for everything on mydevelopmentdomain.tld? (A note about my architecture: as the above suggests, I have a domain under which I do development work in subdomains. This allows me to test that I have things running correctly on the server, expose projects to beta testers or clients, etc, as an intermediary step before deploying to the actual domains. SSL is precisely one of the things I would be wanting to test; this came up when I realized that running under SSL would affect some logic of how I was handling the REFERER, and I'd better test before deploying to see if there were any other gotchas. I am trying to figure out how much things cost so I can make informed decisions as to how much SSL I want to roll out.)

Hi, Anonymike. Sure. Under "Membership Management", there's an option "Mass subscription". The form has buttons to select whether you send an invite email or add them silently.

It means to copy what's inside. A single "*" means "everything". A "*.*" means everything with a name of the form "something-dot-somethingelse". So when it says to copy "root/includes/*.*" into "includes/*.*", it means to move every file from "root/includes" that has a name like "fred.php" or "header.c" or "a.supercalifragilisticexpialidocious" into "includes/" (presumably on your target system.) That "*" is called a "wildcard", and this usage is called "globbing". See http://en.wikipedia.org/wiki/Glob_%28programming%29 for an intro.

I feel likewise about my addon domains, so I set up an .htaccess file for each of my addons so that when visitors go to zzz.net they get zzz.net, but when they go to zzz.yyy.com, they get a 404 Page Not Found error on yyy.com. I'm not an htaccess guru of any sort, and this doesn't work perfectly, but what I have is: RewriteEngine on RewriteCond %{HTTP_HOST} yyy [NC] RewriteRule ^(.*)$ http://yyy.com/404.html [L,R=404] (Those three lines go in the .htaccess file in the docroot of the addon domain.) When the string "yyy" (case insensitive) is found in the host specified in the request, it coughs up a 404. When that string isn't found, it serves pages normally. This is working fine for my docroot, but I think it's not doing the right thing for subdirectories, and I've yet to figure out why.

In the sticky post, you asked what customers missed from other vendors. I'm using another vendor to get (among other things) subaddressing aka plus addressing. Here's a description: http://zemalf.com/1418/email-sub-addressing/ Here's the relevant RCF: http://tools.ietf.org/html/rfc5233 Exim supports it. I gather Cpanel added supporting this to their to-do list. See this discussion: http://forums.cpanel.net/f145/case-16578-get-serious-about-getting-subaddress-plus-addressing-support-exim-100893-p2.html which also concludes with a recent hack to turn on the necessary exim configuration, and a cogent explanation of why it's different/better than just making an endless supply of valiases. While this feature might not quite yet be ready for prime time in a CPanel environment, it is a very awesome feature which I commend to you.