Gary Dale wrote on 03/24/2015 04:49:
> The problem seems to have been the location of the protocol = smtps line. I
> had
> it originally in
> /etc/exim4/conf.d/transport/30_exim4-config_remote_smtp_smarthost. Moving it
> to
> /etc/exim4/exim4.conf.template seems to have done the trick.
>
Didn'
On 17/03/15 10:38 AM, Gary Dale wrote:
On 17/03/15 01:30 AM, David Wright wrote:
Quoting Gary Dale (garyd...@torfree.net):
On 16/03/15 12:37 PM, Brian wrote:
On Mon 16 Mar 2015 at 10:46:25 -0500, David Wright wrote:
Quoting James (bjloc...@lockie.ca):
You can't telnet to an ssl port.
Use:
On 17/03/15 01:30 AM, David Wright wrote:
Quoting Gary Dale (garyd...@torfree.net):
On 16/03/15 12:37 PM, Brian wrote:
On Mon 16 Mar 2015 at 10:46:25 -0500, David Wright wrote:
Quoting James (bjloc...@lockie.ca):
You can't telnet to an ssl port.
Use:
openssl s_client -connect [IP]:smtps
I'
On Tue 17 Mar 2015 at 00:30:38 -0500, David Wright wrote:
> Quoting Gary Dale (garyd...@torfree.net):
> > OK, following the doc at http://www.debianhelp.co.uk/mail.htm, I
> > could enter:
> > HELO
>
> I always use EHLO but have no idea if it makes a difference.
EHLO allows the client to discove
On Sat, Mar 14, 2015 at 08:48:37PM -0500, David Wright wrote:
> Is it worth telnetting the port to check that it supports what you
> think it does. For example, from several years ago:
Check out "swaks". It is a debug SMTP client which can do more sophisticated
things than you can via telnet.
--
Quoting Gary Dale (garyd...@torfree.net):
> On 16/03/15 12:37 PM, Brian wrote:
> >On Mon 16 Mar 2015 at 10:46:25 -0500, David Wright wrote:
> >
> >>Quoting James (bjloc...@lockie.ca):
> >>
> >>>You can't telnet to an ssl port.
> >>>Use:
> >>>openssl s_client -connect [IP]:smtps
> >>I'm sorry if I m
On 16/03/15 12:37 PM, Brian wrote:
On Mon 16 Mar 2015 at 10:46:25 -0500, David Wright wrote:
Quoting James (bjloc...@lockie.ca):
You can't telnet to an ssl port.
Use:
openssl s_client -connect [IP]:smtps
I'm sorry if I muddied the waters by suggesting using telnet.
I find it a useful tool to
On Mon 16 Mar 2015 at 10:46:25 -0500, David Wright wrote:
> Quoting James (bjloc...@lockie.ca):
>
> > You can't telnet to an ssl port.
> > Use:
> > openssl s_client -connect [IP]:smtps
>
> I'm sorry if I muddied the waters by suggesting using telnet.
> I find it a useful tool to quickly test whe
Quoting James (bjloc...@lockie.ca):
> You can't telnet to an ssl port.
> Use:
> openssl s_client -connect [IP]:smtps
I'm sorry if I muddied the waters by suggesting using telnet.
I find it a useful tool to quickly test whether I can reach a port,
whether anything is listening, and whether the res
On 03/15/2015 08:04 AM, Gary Dale wrote:
On 15/03/15 05:32 AM, Jörg-Volker Peetz wrote:
Gary Dale wrote on 03/15/2015 04:26:
I can telnet to both 26 and 465. I get three 220 lines when I
connect to port
26, including the ESMTP line, but not when I use port 465. When I
connect to
port 465,
Forgot to mention that I'm using jessie with exim4 version 4.84-8.
--
Regards,
jvp.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/me46qp$6ek$1...@ger.gmane.org
On 15/03/15 05:32 AM, Jörg-Volker Peetz wrote:
Gary Dale wrote on 03/15/2015 04:26:
I can telnet to both 26 and 465. I get three 220 lines when I connect to port
26, including the ESMTP line, but not when I use port 465. When I connect to
port 465, I get kicked out if I enter the EHLO or a USER
Gary Dale wrote on 03/15/2015 04:26:
> I can telnet to both 26 and 465. I get three 220 lines when I connect to port
> 26, including the ESMTP line, but not when I use port 465. When I connect to
> port 465, I get kicked out if I enter the EHLO or a USER command, etc..
>
Also on the smtps server
On 14/03/15 09:48 PM, David Wright wrote:
Quoting Gary Dale (garyd...@torfree.net):
On 14/03/15 09:34 AM, Jörg-Volker Peetz wrote:
Gary Dale wrote on 03/14/2015 06:00:
I did add tls_on_connect_ports = 465 to exim4.conf.localmacros, which is
supposed to cover the SSL on connect issue.
Beside
On 14/03/15 11:08 AM, Jörg-Volker Peetz wrote:
Gary Dale wrote on 03/14/2015 15:46:
On 14/03/15 09:34 AM, Jörg-Volker Peetz wrote:
Gary Dale wrote on 03/14/2015 06:00:
I did add tls_on_connect_ports = 465 to exim4.conf.localmacros, which is
supposed to cover the SSL on connect issue.
Beside
Quoting Gary Dale (garyd...@torfree.net):
> On 14/03/15 09:34 AM, Jörg-Volker Peetz wrote:
> >Gary Dale wrote on 03/14/2015 06:00:
> >
> >>I did add tls_on_connect_ports = 465 to exim4.conf.localmacros, which is
> >>supposed to cover the SSL on connect issue.
> >>
> >Besides the dc_smarthost additi
Gary Dale wrote on 03/14/2015 15:46:
> On 14/03/15 09:34 AM, Jörg-Volker Peetz wrote:
>> Gary Dale wrote on 03/14/2015 06:00:
>>
>>> I did add tls_on_connect_ports = 465 to exim4.conf.localmacros, which is
>>> supposed to cover the SSL on connect issue.
>>>
>> Besides the dc_smarthost addition "::
On 14/03/15 09:34 AM, Jörg-Volker Peetz wrote:
Gary Dale wrote on 03/14/2015 06:00:
I did add tls_on_connect_ports = 465 to exim4.conf.localmacros, which is
supposed to cover the SSL on connect issue.
Besides the dc_smarthost addition "::465", I added
protocol = smtps
in the "transport/
On 14/03/15 09:34 AM, Jörg-Volker Peetz wrote:
Gary Dale wrote on 03/14/2015 06:00:
I did add tls_on_connect_ports = 465 to exim4.conf.localmacros, which is
supposed to cover the SSL on connect issue.
Besides the dc_smarthost addition "::465", I added
protocol = smtps
in the "transport/
Gary Dale wrote on 03/14/2015 06:00:
>
> I did add tls_on_connect_ports = 465 to exim4.conf.localmacros, which is
> supposed to cover the SSL on connect issue.
>
Besides the dc_smarthost addition "::465", I added
protocol = smtps
in the "transport/30_exim4-config_remote_smtp_smarthost" sec
On 13/03/15 01:19 PM, Eduardo M KALINOWSKI wrote:
On Sex, 13 Mar 2015, Gary Dale wrote:
My update-exim4.conf.conf file is (replacing with
the actual name). If dc_smarthost has the port set to 26, mail gets
sent. However with it set to 465, it stays in the mailq.
dc_eximconfig_configtype='sma
On 13/03/15 01:28 PM, David Wright wrote:
Quoting Gary Dale (garyd...@torfree.net):
I'm running a Wheezy/64 server and am trying to get exim4 to send
e-mail using an SSL connection. My current configuration works when
I use their normal smtp port (which is 26, not 25) but fails when I
use their
Quoting Gary Dale (garyd...@torfree.net):
> I'm running a Wheezy/64 server and am trying to get exim4 to send
> e-mail using an SSL connection. My current configuration works when
> I use their normal smtp port (which is 26, not 25) but fails when I
> use their smtp/SSL port (465).
>
> However Thu
On Sex, 13 Mar 2015, Gary Dale wrote:
My update-exim4.conf.conf file is (replacing with
the actual name). If dc_smarthost has the port set to 26, mail gets
sent. However with it set to 465, it stays in the mailq.
dc_eximconfig_configtype='smarthost'
dc_other_hostnames=''
dc_local_interfaces
24 matches
Mail list logo
