Comment 2 for bug 592420

Thanks s34n for the Reply and reminder that I post this.

After some very extensive testing I found that the Qwest supplied Actiontec PK5000 DSL modem was the culprit to the issue that I was having. There is according to Actiontec a "Glitch" in their Software. So what I originally did to configure Port Forwarding on the PK5000 was under the Advanced Port Forwarding Section of the Web Interface of the Modem. I had set ports 25, 110, 143, 443, 585, 993, 995 to forward to my mail server, and ports 22, 80 to forward to web server, with ports 53, 953 forwarded to dns server. So all of the sudden that configuration stopped working and 443 was being forwarded by the DSL modem to the web server which didn't have https running, nor open for traffic.

How I fixed this issue was as follows:
I not only used the Advanced Port Forwarding section but also under Application Forwarding Section I created 3 custom rules one for dns servers with 53, 953 being forwarded, one for web server with 22, 80 being forwarded, and one for mail server with 25, 110, 143, 443, 585, 993, 995 being forwarded. Once I had both rules under Advanced Port Forwarding, and Application Forwarding it started allowing traffic to my Mail Server via HTTPS and I no longer get that SSL error.

I have since replaced the Actiontec Pk5000 with the D-Link DSL-2540b and have been very happy so far with the replacement. The D-Link was just as easy to set-up as the Actiontec, and didn't require having settings in multiple locations just to get a Single service to work.

So I apologize for posting as a bug with Ubuntu when it was really a bug for Actiontec.