Question: Server using Apache and Plesk 9.

I have set-up multiple domains each with its own IP for SSL. 
Each domain has its own SSL config file **/var/www/vhosts/mydomain/conf/vhost\_ssl.conf**

I have disabled SSLv2 in **/etc/httpd/conf.d/ssl.conf**
and checked it with 

`openssl s_client –ssl2 –connect localhost:443`
result is an error.. which is correct

However when i test the domain to see if SSLv2 is disabled

`openssl s_client –ssl2 –connect mydomain:443`
result is domain has SSLv2 support - not what i want

My question is... Do i have to add lines to /var/www/vhosts/mydomain/conf/vhost\_ssl.conf to disable SSLv2 support for that domain...?

Is yes, do i need to copy the full `<VirtualHost _default_:443>....</VirtualHost>` section form **/etc/httpd/conf.d/ssl.conf** and add it to **/var/www/vhosts/mydomain/conf/vhost\_ssl.conf** ?

Answer: 
I have a lot of understanding for your users. You are doing a fundamental error of system administration: You create a solution that is easy for the sysadmins, but forget the needs and requirements of the users. 200mb per user is simply insane, and it is a limitation that causes problems for them, as they have to bother with archives and backups. This is wasted time and wasted money. The cost of 1gb of storage compared to the time it takes to sort 1gb of emails is extremely bad on the cost/benefit scale. 

Why don't you provide your users with "unlimited" storage space? In practice, it won't grow very fast. It will take away the whole problem with the local archiving when the users no longer need to delete e-mails.

So, what you should be telling your users is "You don't need personal folders anymore. We will store all the e-mails for you, and take care of the backups."
It's really easy. Well it's easy to say and easy to understand. Might be difficult to do, however.

Simply put, you need to understand your users problems, and then you need to solve *their* problems, not the *IT Department's* problems. If they are using PST files then find out why and address that. If they are reluctant to change then find out why and address that.

I sympathise with the reasons why you can't just give people 'unlimited' space on the email server. But I sympathise more with people who are just trying to get their work done and have to cope with obstacles the IT department is (so it feels to them) placing in their way. 

You might think "but we don't place obstacles in their way". I'm sure you don't intend to, but consider this: No-one in their right mind would *want* to use a PST file. I mean really, do you get up on Friday mornings and think "It's been a rough week. I think I'll turn the week around by treating myself to a new PST file!". At least I *really* hope you don't. So if your users are doing this then either ALL of them are crazy or they have problems which the IT department are not addressing.

Their reluctance to use the mimecast feature could be a lack of understanding how it works, it could be that it hasn't been properly explained to them from their point of view (as IT people we typically get focussed on how cool some piece of tech is and not on how it makes things easier for our customers) or it might be a trust issue - if the IT department has been unhelpful in the past over email space and the users have created PSTs out of desperation themselves then they may see the new system as a 'grab' to take control of their data away from them and put it back under a regime that has not always been sympathetic to their needs.