Are you using VirtualHost definitions in apache? If so, see
http://httpd.apache.org/docs/2.2/mod/mod_rewrite.html#vhosts
Will you post the mod_rewrite commands you were using that failed to do
what you wanted? I might be able to see whatever the problem is.
--
-Eric 'shubes'
madmac wrote:
I could not get any redirects to work on my qmail server:
So I forced ssl, by that I mean I modified the http.conf to listen on
80, and 443
Made a defailt index.html for http, saying " nothing here: you must go
to https://servername.com/webmail
Then sent a server wide email to the fact.
I will be later forcing pop3s and imapds, but need baby stems for the users
As there is only One admin ( me ) I always go to
https://servername.com/qcontrol , just force of habit.
For those that rememeber some of my previous emails, I created a new VM
Image unsing Centos 5.4 ISO, I made it ( Hopefully ) ultra secure.
Link to it from Jake`s site ,http://iso.qmailtoaster.com/
or if the link is still down, download direct from my server
http://techyguru.com
If there is a working solution to get the correct redirect working, I
will add it to the VM Image and re-upload.
Thanks All
madmac
----- Original Message -----
*From:* Scott Hughes <mailto:[email protected]>
*To:* [email protected]
<mailto:[email protected]>
*Sent:* Friday, May 28, 2010 10:18 PM
*Subject:* Re: [qmailtoaster] Re: Webmail SSL
CJ,
Yes, those two directives are doing what I need them to do. Thanks!
Scott
On May 28, 2010, at 11:12 PM, Maxwell Smart <[email protected]
<mailto:[email protected]>> wrote:
Scott,
It sounds like you handle multiple domains, but only in a mail
environment. In my case I have used the QMTISO as a base to my
webservers. It has been an excellent base.
You can put those in the httpd.conf file or as Eric suggested in a
.conf file in your conf.d folder.
/Also, I can still get to the webmail by using the standard
'www.SERVERNAME.net/webmail <http://www.SERVERNAME.net/webmail>'.
In this case, it does go to the SSL page via the SSLREQUIRESSL and
the 403 https://mail.SERVERNAME.net/ directives.
/
My personal preference would be to remove these aliases once you
get the https sorted. Is it doing what you want (expect) now?
@Eric. I'll check out that link and see if it applies to my
situation.
CJ
On 05/28/2010 07:02 PM, Scott Hughes wrote:
CJ,
I don't use virtual hosts on this server. While this QMT server
does handle several domains, I have everyone pointed to the main
domain name to access their mail (webmail and mail clients). In
addition to keeping all the settings the same, I can get away
with only needing one SSL certificate instead of one for each domain.
Where in httpd.conf would be the best place to put these
directives with the setup I have?
Scott
On 5/28/10 8:51 PM, Maxwell Smart wrote:
When you include SSLRequireSSL and it's not an SSL connection it
will give an error 403, using the ErrorDocument 403
https://mail.servername.net include it will then redirect the
page to the https page.
On 05/28/2010 06:26 PM, Scott Hughes wrote:
CJ,
I'm not getting any 403 errors. Would this still apply? I'm
just looking to make it so that when one of my users goes to
"mail.SERVERNAME.net <http://mail.SERVERNAME.net>' they get the
SSL pages.
Thanks,
Scott
On 5/28/10 6:50 PM, Maxwell Smart wrote:
Add these two lines to the virtual server.
SSLRequireSSL
ErrorDocument 403 https://mail.servername.net
There is a way to do a simple redirect, but I haven't played
with it and can't seem to get it to work as desired. I am
told it has to do with timeout. You set the META to timeout
and redirect to the SSL site. It can be seamless too. I
know the above works and I am sure there is not much to be
gained using the latter configuration.
On 05/28/2010 04:27 PM, Scott Hughes wrote:
CJ / Eric,
How does one set up a redirect so that people automatically
go to the secure area? My SSL setup is working, but only if I
go directly there (https://mail.SERVERNAME.net). If I just
do 'mail.SERVERNAME.net, it goes to the non-secure page.
My setup is as follows:
I have a symlink in my /var/www/html directory called
'webmail' (the symlink points to the Squirrelmail directory).
In my http.conf file, in the document_root section, I have it
setup to go to /var/www/html/webmail.
I do this so that my users can type in mail.SERVERNAME.net
<http://mail.SERVERNAME.net> and get to webmail.
Is there a more proper way to do this and still give them the
ease of access?
Thanks,
Scott
On 5/28/10 10:49 AM, Maxwell Smart wrote:
I have set up the Rewrite as suggested, but it does not redirect from
http to https is only says forbidden. I can create a 403 redirect, but
would rather set it up as a simple redirect. How is this done?
While this will work for one domain or if the user knows that the master
domain is the one he is receiving the certificate for. Has anyone set
it up either using ssl or gnutls to have each virtual domain using it's
on certificate? I use the QMT ISO as a webserver and would like to be
able to offer certs for individual clients thus being able to correctly
authenticate either their https://www.myserver.com or
https://mail.myserver.com correctly.
CJ
On 05/27/2010 11:28 AM, Eric Shubert wrote:
Scott Hughes wrote:
Does anyone happen to know if there is a wiki entry for securing
SquirrelMail using SSL? I'm looking but I'm not finding it.
Thanks,
Scott
http://wiki.qmailtoaster.com/index.php/Certificate briefly mentions
that you can use the cert for apache. That page could really use some
rework.
Note, the mod-ssl package must be installed for apache.
Once you have a certificate installed for apache, the
squirrelmail.conf file can be modified to look like this:
<IfModule mod_alias.c>
Alias /webmail /usr/share/squirrelmail
</IfModule>
RewriteEngine on
RewriteCond %{SERVER_PORT} !^443$
RewriteRule ^(.*/webmail.*)$ https://%{SERVER_NAME}$1 [L,R]
<Directory /usr/share/squirrelmail>
Options None
Order allow,deny
allow from all
SSLRequireSSL
</Directory>
I see you've started a SM page on the wiki. Great.
Thanks for your work on this.
--
Cecil Yother, Jr. "cj"
cj's
2318 Clement Ave
Alameda, CA 94501
tel 510.865.2787
http://yother.com
---------------------------------------------------------------------------------
Qmailtoaster is sponsored by Vickers Consulting Group
(www.vickersconsulting.com <http://www.vickersconsulting.com>)
Vickers Consulting Group offers Qmailtoaster support and
installations. If you need professional help with your setup,
contact them today!
---------------------------------------------------------------------------------
Please visit qmailtoaster.com <http://qmailtoaster.com> for
the latest news, updates, and packages. To unsubscribe,
e-mail: [email protected]
<mailto:[email protected]> For
additional commands, e-mail:
[email protected]
<mailto:[email protected]>
--
Cecil Yother, Jr. "cj"
cj's
2318 Clement Ave
Alameda, CA 94501
tel 510.865.2787 | fax 510.864.7300
http://yother.com
--
Cecil Yother, Jr. "cj"
cj's
2318 Clement Ave
Alameda, CA 94501
tel 510.865.2787
http://yother.com
---------------------------------------------------------------------------------
Qmailtoaster is sponsored by Vickers Consulting Group
(www.vickersconsulting.com <http://www.vickersconsulting.com>)
Vickers Consulting Group offers Qmailtoaster support and
installations. If you need professional help with your setup,
contact them today!
---------------------------------------------------------------------------------
Please visit qmailtoaster.com <http://qmailtoaster.com> for the
latest news, updates, and packages. To unsubscribe, e-mail:
[email protected]
<mailto:[email protected]> For
additional commands, e-mail:
[email protected]
<mailto:[email protected]>
---------------------------------------------------------------------------------
Qmailtoaster is sponsored by Vickers Consulting Group
(www.vickersconsulting.com)
Vickers Consulting Group offers Qmailtoaster support and installations.
If you need professional help with your setup, contact them today!
---------------------------------------------------------------------------------
Please visit qmailtoaster.com for the latest news, updates, and packages.
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
