Https on Squirrelmail Apache2 Postfix Ubuntu

Hi Routinet,

Sorry for the late reply. I got cought up in multiple emergencies that needs to be taken care of.

Can you tell me if I mistakenly included any confidential info? I've looked at it ans so far I can tell it looked ok. Anyhow, here is the content of /etc/apache2/conf.d/squirrelmail.conf :


Alias /squirrelmail /usr/share/squirrelmail

<Directory /usr/share/squirrelmail>
  Options Indexes FollowSymLinks
  <IfModule mod_php4.c>
    php_flag register_globals off
  </IfModule>
  <IfModule mod_php5.c>
    php_flag register_globals off
  </IfModule>
  <IfModule mod_dir.c>
    DirectoryIndex index.php
  </IfModule>

  # access to configtest is limited by default to prevent information leak
  <Files configtest.php>
    order deny,allow
    deny from all
    allow from 127.0.0.1
  </Files>
</Directory>

# users will prefer a simple URL like http://webmail.example.com
#<VirtualHost 1.2.3.4>
#  DocumentRoot /usr/share/squirrelmail
#  ServerName webmail.example.com
#</VirtualHost>

# redirect to https when available (thanks omen@descolada.dartmouth.edu)
#
#  Note: There are multiple ways to do this, and which one is suitable for
#  your site's configuration depends. Consult the apache documentation if
#  you're unsure, as this example might not work everywhere.
#
#<IfModule mod_rewrite.c>
#  <IfModule mod_ssl.c>
#    <Location /squirrelmail>
#      RewriteEngine on
#      RewriteCond %{HTTPS} !^on$ [NC]
#      RewriteRule . https://%{HTTP_HOST}%{REQUEST_URI}  [L]
#    </Location>
#  </IfModule>
#</IfModule>

Well, that all looks good, but you're missing a couple of details.

The <Directory> container sets up some restrictions for the squirrelmail installation.  That's fine.  

The second part, the <VirtualHost> container, is the first thing you need to address.  Are you serving squirrelmail as a URL available from a parent site (www.mydomain.com/squirrelmail), or will it be its own independent site (such as webmail.mydomain.com)?  In the first case, you will need to make sure that the parent site is configured to serve SSL content.  In the latter case, you will need to uncomment the <VirtualHost> declaration, and add SSL directives to it.

The third part should probably be uncommented as well, if you want to enforce mandatory SSL with your squirrelmail installation.

Hello.

My setup uses a parent site www.mydomain.com/squirrelmail. However, this machine is the parent site (i.e, from the router, I direct port 80 to this machine.

So what should I do to achieve your recommendation:
" In the first case, you will need to make sure that the parent site is configured to serve SSL content."
Am I configured to serve ssl content already? I dont have /etc/httpd/conf.d/ssl.conf, but I'm pretty sure I've setup ssl. (according to http://workaround.org/articles/ispmail-etch/  anyways, unlessI misunderstood something).

On the third part:
"The third part should probably be uncommented as well, if you want to enforce mandatory SSL"
Yes, please. mandatory sounds good. (i.e redirecting http to https, correct?) How do I do this? just uncomment? No need to find /etc/httpd/conf.d/ssl.conf ? (All the guides has this file, so I'm somewhat worried why I don't have it).

Thanks Routinet.

You're right about my level of understanding. I kept telling myself that I need an IT personnel.

Anyhow, I think I need to do a bit of learning  before I can fully understand your answer and so ask better questions. Your answers has provided enough for me to know what information to look for though. Thanks.

HI Routinet,
I don't know if you can still get this message. I finally got the time to implement the above changes (deleting the comment marks on the third part: Ifmodule mod_rewrite, etc) but it doesnt seem to work. I'm still accessing via http and not redirected to https?

You'll need to post all of the relevant conf files.  What you have posted to date is just the squirrelmail configuration, and does not indicate how it interacts with the rest.

Routinet, what is the other relevant conf file?