[Pkg-exim4-users] Troubleshooting exim4 in Wheezy.

[Marc Haber]

On Thu, Mar 13, 2014 at 10:21:26AM -0700, Peter Easthope wrote:
> On Thu, March 13, 2014 12:47 am, Marc Haber wrote:
> > What do the logs say about the message?
> 
> /var/log/exim4/mainlog has many lines such as this.
> 2014-03-13 09:04:36 1WNjEW-0001wJ-6r Message is frozen

This is a follow-up log entry, there must be an entry for
1WNjEW-0001wJ-6r - probably from days ago - saying why the message was
frozen. See the exim specification about what exim means when it
freezes a message and why.

> And this.
> 2014-03-13 09:05:08 1WO884-0005FE-CB ** peter at easthope.ca R=smarthost
> T=remote_smtp_smarthost: retry time not reached for any host after a long
> failure period 2

This means that your smarthost was unreachable for such a long time
that exim doesn't even bother to try again. See the exim specification
chapter about retrying to find out how it calculates this.

What does your machine log when you do exim -M 1WO884-0005FE-CB?

> > What does "ip addr" show?
> 
> root at dalton:~# ip addr show
>   ...
> 4: LocBel7411cc: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc
> pfifo_fast state UP qlen 1000
>     link/ether 00:05:1b:74:11:cc brd ff:ff:ff:ff:ff:ff
>     inet 172.24.1.1/24 brd 172.24.1.255 scope global LocBel7411cc
>     inet6 fe80::205:1bff:fe74:11cc/64 scope link
>        valid_lft forever preferred_lft forever

That interface name looks really strange to me.

> My intention is that exim4 receives local SMTP connections on port
> 25 with no TLS and calls the remote SMTP server with tls_on_connect,
> port 465.

AFAIR, exim cannot do TLS on connect as a client. That protocol was
never standardized. Exim can do TLS on connect as a server to support
legacy Windows clients.

> http://www.exim.org/exim-html-current/doc/html/spec_html/ch-encrypted_smtp_connections_using_tlsssl.html
> admonishes,
> "You still need to specify all the ports that the daemon uses (by setting
> daemon_smtp_ports or local_interfaces or the -oX command line option)
> because tls_on_connect_ports does not add an extra port – rather, it
> specifies different behaviour on a port that is defined elsewhere."

That's the listening port when exim is a server.

> Can anyone advise how to assign ports according to my intention stated
> above?

If you want to use exim as a client, you don't assign ports.

Greetings
Marc

-- 
-----------------------------------------------------------------------------
Marc Haber         | "I don't trust Computers. They | Mailadresse im Header
Mannheim, Germany  |  lose things."    Winona Ryder | Fon: *49 621 31958061
Nordisch by Nature |  How to make an American Quilt | Fax: *49 621 31958062