Duh! That was it, Thank you.

On 6/21/2011 9:45 AM, Charles Keaton wrote:
> Peter,
>
> My setup works with https://www.domainname.com:7443/surgeweb as does 
> yours. (Your secure URL sent off-list.)
>
>
>
> Charles Keaton
> Director of Technology
> Lockney (TX) Independent School District
> PO Box 428 -- 406 W. Willow
> Lockney, TX 79241
> 806-652-4943 (Direct Office)
> 806-652-4943 (Fax)
> 806-632-3862 (cell)
>
>
>
>
> On Tuesday 06/21/2011 at 11:27, Peter Dyke  wrote:
>> [SurgeMail Version 5.3c-12, Built Apr 8 2011 05:49:48, Platform 
>> Linux_64 (Surgeweb Enabled)]
>>
>> Am I having a senior moment?
>>
>> I am trying to transition our users gradually from an http to an 
>> https login for Surgeweb.
>>
>> I currently have g_webmail_port set to 80, and g_webmail_secure_port 
>> at 7443.
>>
>> If they land on port 80, I have a link that takes them to 
>> http://mail.domain.com/surgeweb which of course works just fine. But 
>> what would be the equivalent link to take them to the secure login 
>> page for Surgeweb? http://mail.domain.com:7443 goes back to the same 
>> as the port 80 page, just with an https connection, and so no new 
>> route to the secure Surgeweb. Neither 
>> https://mail.domain.com/surgeweb nor 
>> https://mail.domain.com/surgeweb:7443 connect at all.
>>
>> I don't want to force Surgeweb to require an https connection just 
>> yet for all connections, there needs to be some education first.
>>
>> So my question is, what would be the URL, equivalent to 
>> http://mail.domain.com/surgeweb, that would enable an https page for 
>> login?
>>
>>
>>
>
>
>
>
>