Hi,

we have been using pound 2.0.3 as a front end for our webmail for the past several years.

The existing server was being retired so I created a new VM using RHEL 5.3 x64 and installed pound rpm 2.4.4

I copied over the old config file only to discover that some of the options I had used were no longer recognized.  To be honest it's been so long
since I've looked at this server that I don't recall the specifics of why I used certain options.

Anyway, my issue is that pound on the new server is not operating the same as pound on the old server.

Here is what is supposed to happen:

- user browses to https://mailserver.camsys.com
- login form appears, they enter their username and password, and click continue
- mail server processes login and webmail appears

What is happening now is when the user clicks the continue button, the URL is changing from HTTPS to HTTP, this causing a "no service" error.

Here is a bit of the OLD config:

User "pound"
Group "pound"
Daemon 1
LogLevel 1
Alive 30

ListenHTTPS
        Address 192.168.5.101
        Port 443
        xHTTP 0
        WebDAV 0
        Client 10
        Change30x 1
        Cert "/usr/local/etc/pound.pem"

        Service
                URL ".*"
                HeadRequire "Host:.*camwebmail.camsys.com.*"
                BackEnd
                        Address 192.152.136.3
                        Port 80
                End
        End

the NEW config is identical EXCEPT i had to comment out the WebDAV 0 and Change30x 1 options in order for pound to successfully parse the file.

I guess my question is, assuming these 2 commented out options are causing my current issues, what options have replaced them that offer the same
functionality?  

I googled this issue and found an old thread that I started in 2006 related to this exact issue.  The cause then was using hosts files and not DNS, but that is not the case this time,
though the thread did remind me of why I used the Change30x 1 option, in order to "fix" the response headers from my Lotus Domino server to make sure the URL was HTTPS

Thanks,

--jeff