>Subject: Re: [Exim] "SMTP protocol violation: synchronization" error when
> using TLS with Outlook on a port other than 25?
>From: Scott Dexter <scott.dexter@???>
>To: Exim-Users <exim-users@???>
>Date: 01 Aug 2003 10:10:34 -0400
>
>I've had issues running the second instance of exim on the
>alternate port. I run the inital one port 25, no problems. When i
>run "exim -bd -oX 465 -tls-on-connect" It doesn't seem to attach to
>port 465 and instead seems (according to maillog) to be trying to
>attach to 25?
Well I haven't tried this, but I recall Matt Bernstein posting
details of how he did this back in February. Search the mail
archives and look for:
From: Matt Bernstein <mb@???>
To: exim-users@???
Subject: SSL/TLS recipe (was Re: [Exim] TLS on a port other than 25)
Message-ID: <Pine.LNX.4.53.0302161422370.786@???>
Date: Sun, 16 Feb 2003 14:34:19 +0000 (GMT)
>On Fri, 2003-08-01 at 04:19, Philip Hazel wrote:
>> On Thu, 31 Jul 2003, Ralf Hauser wrote:
>>
>> > SMTP protocol violation: synchronization error (next input sent too soon):
>> > rejected "<80>j^A^C^A" H=[10.2.1.1]
>>
>> There is already another thread already running on this mailing list on
>> this very topic.
>>
>> > Therefore my question: has anybody been successful at running a production
>> > exim with SMTP-TLS on a port other than 25 with Outlook users?
>>
>> You have to use the -tls-on-connect and -oX options to run a second Exim
>> daemon.
