I tried the following:
g_ssl_require = !127.0.0.1/8
g_ssl_require_login = !11.22.33.0/24,!127.0.0.1/8,*
(where 11.22.33.0/24 is my subnet)
Also tried:
g_ssl_require = <empty>
g_ssl_require_login = !11.22.33.0/24,!127.0.0.1/8,*
And:
g_ssl_require = <empty>
g_ssl_require_login = !127.0.0.1/8,*
I still get the same error message when I try to send mail from SurgeWeb:
Send failed
500 SSL required for ip (127.0.0.1) when authenticating
The only way I can send a message from SurgeWeb is to leave g_ssl_require_login blank, which allows authentication in the clear over the public Internet - something I do not want to permit.
I want to require SSL authentication for connections outside my subnet but allow non-SSL connections within my subnet. I also want to be able to use SurgeWeb. This appears to be impossible.
What am I missing?
Thanks,
John
--
John Wilkes
HIDDEN@lkes.com
On Nov 10, 2011, at 7:17 AM, Paul M. Beck wrote:
> Try adding to "!127.0.0.1" g_ssl_require
>
>
> Paul
>
>
>
>
> On Nov 9, 2011, at 11:25 PM, John Wilkes wrote:
>
>> Normally I use the Mac email client and have no problems sending, but the SurgeWeb interface gives me an error:
>>
>> Send failed
>> 500 SSL required for ip (127.0.0.1) when authenticating
>>
>> I have g_ssl_require_login = !xxx.yyy.zzz.0/24,*
>> (where xxx.yyy.zzz.0/24 is my subnet, i.e. do not require ssl login from my subnet)
>>
>> What setting(s) will allow users to send email from the SurgeWeb interface?
>>
>> Thanks,
>> John
>>
>> --
>> John Wilkes
>>HIDDEN@ilkes.com
>>
>
>
|
