Am 08.12.2011 02:40, schrieb Grant:
>>>> yes because it is STARTTLS
>>>> 465 is smtp over ssl and NOT STARTTLS
>>>>
>>>> we provide both on smtp/imap/pop3 because all of them
>>>> having a dedicated "over ssl" port and STARTTLS over
>>>> the standard-port if configured
>>>>
>>>>    SMTP unencrypted / TLS: 587
>>>>    SMTP over SSL: 465
>>>>    POP3 unencrypted / TLS: 110
>>>>    POP3 over SSL: 995
>>>>    IMAP unencrypted / TLS: 143
>>>>    IMAP over SSL: 993
>>>
>>> Is IMAP over SSL on 993 deprecated in favor of using STARTTLS on 143?
>>
>> i do not know, but i see no reason to disable the dedicated ssl-ports
> 
> Are you saying I should continue using smtps port 465 even though it's
> deprecated?

your decision

>>> I just read that Squirrelmail doesn't support STARTTLS, so I must
>>> continue to use smtps 465 in order to use Squirrelmail?
>>
>> the main-question is why you need to encrypt sending messages from
>> a webmail which usually does not go over the WAN
> 
> If I set "Secure SMTP (TLS) : false" in squirrelmail, I get:
> 
> Authentication required
> 530 5.7.0 Must issue a STARTTLS command first
>
> If I change port 587 to 25 in squirrelmail I get:
> 
> Bad sequence of commands
> 503 5.5.1 Error: authentication not enabled

this sounds like a broken setup

smtp            inet  n       -       n       -      50       smtpd -o 
smtpd_client_connection_count_limit=15 -o
max_idle=1h -o max_use=500

submission      inet  n       -       n       -      50       smtpd -o 
smtpd_client_connection_count_limit=15 -o
smtpd_sasl_auth_enable=yes -o smtpd_delay_reject=yes -o 
smtpd_client_restrictions=permit_sasl_authenticated,reject
-o max_idle=1h -o max_use=500

smtps           inet  n       -       n       -      50       smtpd -o 
smtpd_client_connection_count_limit=15 -o
smtpd_sasl_auth_enable=yes -o smtpd_delay_reject=yes -o 
smtpd_client_restrictions=permit_sasl_authenticated,reject
-o smtpd_tls_wrappermode=yes -o max_idle=1h -o max_use=500





Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to