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

Marc Haber mh+pkg-exim4-users at zugschlus.de
Fri Mar 14 07:48:57 UTC 2014

On Thu, Mar 13, 2014 at 01:03:46PM -0700, Peter Easthope wrote:
> On Thu, March 13, 2014 10:39 am, Marc Haber wrote:
> >> 4: LocBel7411cc: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc
> >
> > That interface name looks really strange to me.
> There is method to the madness.
> Loc identifies the local zone of shorewall.  Making it a prefix
> of the name simplifies shorewall configuration.
> Bel refers to Belkin, the name on the USB-Ethernet adapter.
> 7411cc refers to the number on the adapter, which I can read
> to distinguish it from the other Belkins.

I see.

> > 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.
> Yikes!  Bad if websitewelcome.com uses an obsolete un-standardized
> protocol.  I'm pounding on a brick wall.  tls-on-connect works in
> swaks.  I'll try to use swaks or ssmtp to send to websitewelcome.com.
> Otherwise fall back to sending in the clear on port 25.  Bad practice!

The MX for websitewelcome.com seems to listen on Port 587, offers
STARTTLS and AUTH PLAIN. I'd guess that setting dc_smarthost to
websitewelcome.com::587 is going to work. They're using exim as well,

> > What does your machine log when you do exim -M 1WO884-0005FE-CB?
> root at dalton:/home/peter# exim -M 1WO884-0005FE-CB
> root at dalton:/home/peter# exit
> peter at dalton:~$ grep 1WO884-0005FE-CB /var/log/exim4/mainlog
> 2014-03-13 09:05:08 1WO884-0005FE-CB <= peter at easthope.ca
> H=localhost.localdomain (dalton) [] P=smtp S=615
> 2014-03-13 09:05:08 1WO884-0005FE-CB ** pleasthope at gmail.com R=smarthost
> T=remote_smtp_smarthost: retry time not reached for any host after a long
> failure period
> 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
> 2014-03-13 09:05:08 1WO884-0005FI-J4 <= <> R=1WO884-0005FE-CB
> U=Debian-exim P=local S=1573
> 2014-03-13 09:05:08 1WO884-0005FE-CB Completed
> 2014-03-13 12:43:46 1WO884-0005FE-CB Spool file 1WO884-0005FE-CB-D not found
> peter at dalton:~$

Ah. You need to -Mf to force a delivery attempt.

> > That's the listening port when exim is a server.
> OK, thanks.  The documentation would be so much more helpful if the
> distinction between sending and receiving were made.  Ambiguity seriously
> hobbles any documentation.

/usr/share/doc/exim4-base/README.Debian.gz, Chapter 2.2.1 "Exim 4 as
TLS/SSL client" and Chapter 2.2.2 "Enabling TLS support for Exim as
server" is ambiguous?

> Will be funny to end up feeding locally generated messages from exim into
> a local swaks or ssmtp which forwards to websitewelcome.com.

You could also use stunnel, which is kind of the canonical way to coax
the clumsy an unstandardizes protocol. Or you could try using the
obviously undocumented way to deliver to Port 587. If that works,
maybe they would be willing to actually document this method as an


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

More information about the Pkg-exim4-users mailing list