On Wed, Nov 20, 2013 at 1:13 PM, li...@rhsoft.net wrote:
> Am 20.11.2013 13:55, schrieb bitozoid:
>> On Tue, Nov 19, 2013 at 1:32 PM, Brian Evans wrote:
>>> The smtp client process does not have support for the deprecated smtps
>>> protocol (465) you are trying to use.
>>
>> I have another instan
Am 20.11.2013 13:55, schrieb bitozoid:
> On Tue, Nov 19, 2013 at 1:32 PM, Brian Evans wrote:
>> The smtp client process does not have support for the deprecated smtps
>> protocol (465) you are trying to use.
>
> I have another instance of postfix working against other smarthost
> (Exchange in thi
On Tue, Nov 19, 2013 at 1:32 PM, Brian Evans wrote:
> The smtp client process does not have support for the deprecated smtps
> protocol (465) you are trying to use.
I have another instance of postfix working against other smarthost
(Exchange in this case) via port 465, and it seems not to be a pr
On Nov 19, 2013, at 5:50, bitozoid wrote:
>
> I'm getting a TLS timeout (4.4.2) when connecting to the smarthost
> (port 465).
Port 465 is a legacy port and was only ever used by Outlook, as I recall. It is
generally not supported by other MUAs, and I seriously doubt any MUA tha
On 11/19/2013 7:50 AM, bitozoid wrote:
I'm getting a TLS timeout (4.4.2) when connecting to the smarthost
(port 465). If I try with no TLS (port 25) it connects and sends
emails.
I can successfully connect with 'openssl s_client ...' and this way it
says there is a 300 seconds t
I'm getting a TLS timeout (4.4.2) when connecting to the smarthost
(port 465). If I try with no TLS (port 25) it connects and sends
emails.
I can successfully connect with 'openssl s_client ...' and this way it
says there is a 300 seconds timeout (same as in the log below).
My po
