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

[Peter Easthope]

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.

> 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!

>> /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.

Right oh; but given the above it will boil down to "not supported".

>> 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.

Again, it will boil down to "not supported".

> 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) [127.0.0.1] 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:~$

I didn't bother opening earlier logs.

> 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.

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

Thanks for the help,          ... Peter E.

-- 
Telephone 1 360 639 0202.  Bcc: peter at easthope.ca "http://carnot.yi.org/ "