[Pkg-exim4-users] configuring exim4 smtp to use SSL

[Gary Dale]

On 16/03/15 11:56 AM, Marc Haber wrote:
> On Mon, Mar 16, 2015 at 10:54:41AM -0400, Gary Dale wrote:
>> On 16/03/15 04:10 AM, Marc Haber wrote:
>>> On Sun, Mar 15, 2015 at 11:20:38PM -0400, Gary Dale wrote:
>>>> The log for an unsuccessful mail says:
>>>> 2015-03-14 00:47:44 1YWdzE-0000l6-CR <= <sending e-mail address>
>>>> U=garydale P=local S=1665
>>>> 2015-03-14 00:47:44 1YWdzE-0000l6-CR ** -r at localhost: Unrouteable address
>>>> 2015-03-14 00:47:44 1YWdzE-0000l6-CR ** gary at extremeground.com
>>>> R=smarthost T=remote_smtp_smarthost: retry time not reached for any
>>>> host after a long failure period
>>>> 2015-03-14 00:47:44 1YWdzE-0000l6-CR ** <sending e-mail address>
>>>> R=smarthost T=remote_smtp_smarthost: retry time not reached for any
>>>> host after a long failure period
>>>> 2015-03-14 00:47:44 1YWdzE-0000lB-Ik <= <> R=1YWdzE-0000l6-CR
>>>> U=Debian-exim P=local S=2720
>>>> 2015-03-14 00:47:44 1YWdzE-0000lB-Ik ** <sending e-mail address>
>>>> R=smarthost T=remote_smtp_smarthost: retry time not reached for any
>>>> host after a long failure period
>>>> 2015-03-14 00:47:44 1YWdzE-0000lB-Ik Frozen (delivery error message)
>>>> 2015-03-14 00:47:44 1YWdzE-0000l6-CR Completed
>>> You need to force the delivery out of the queue or remove the hint.
>>> Exim is not even trying to send here.
>> What do you mean? Why would Exim4 not be trying to send to port 465
>> when it does if I'm sending to port 26? And what hint are you
>> referring to?
> See exim spec.txt chapter 3, especially 3.14, and chapter 32.
>
>>> And please do not obfuscate logs, it happens to often that there are
>>> obvious hints in that kind of data.
>> On the other hand, my clients are entitled to their privacy. The
>> e-mail address is well formed, legitimate and hosted by the company
>> whose smtp server I am trying to reach. Again, the setup works when
>> I change only port 465 to port 26.
> Commercial support for exim is available through numerous sources.
> Please consider buying some if you're using exim commercially and
> can't figure things out by yourself.
>
>>> It might also help to run a delivery attempt from the command line
>>> with debugging enabled.
>>>
>> Sorry, but I find Exim4's command line man page to be opaque. When I
>> try to use exim4 from the command line using -bem
>> /var/log/exim4/msglog/<message id>, I get "Warning: no message
>> headers read" and a prompt for more input. Same if I add a -t
>> option.
> Get the mail into the queue and try delivering with exim -M <msgid>
> -D. If that is inconclusive, try -D+all
I don't think you looked carefully at the log. The message enters then 
freezes. When sent to port 26, it enters and gets delivered. If I 
unfreeze a message to port 465, it still doesn't get delivered. I need 
to change back to port 26 to get delivery.

>
>> I'm not an exim guru.
> If you're making money of it, you should either become one or hire one.
>
>
I don't make money supporting exim4. I support small/home offices. I use 
Debian for servers and Exim4 to deliver system messages to me. In over a 
decade this is the about only Exim problem I've not been able to work out.