Thanks for the suggestion Tom but, as I expected, that didn't work. I
already had ident disabled for the origin host so setting the timeout to
0 didn't change anything.
It did however get me thinking. I strongly suspect that the problem is
that Exim responds too quickly for Outlook and this causes Outlook to
somehow "lose" the OK reply. So, to try to slow Exim down, I tried
ENABLING ident lookups and it appears to have worked! I had one message
which was hanging and it's now gone through.
In case it's only reduced the problem, does anybody have any hints on
things I can do to increase the time between Exim receiving the "MAIL
FROM" and it responding OK?
Thanks,
Greg
-----Original Message-----
From: Knaupp, Thomas [
mailto:Thomas.Knaupp@schwarz.de]
Sent: 02 October 2003 21:58
To: xgk@???; exim-users@???
Subject: AW: [Exim] Outlook timeouts
Greg,
| I have Exim v4.24 running on Windows XP using Cygwin and Outlook as a
| client. Outlook intermittently hangs while sending mail and I'm |
reasonably confident that the problem is a Microsoft
| "feature". I have seen that Postcast has a special option to |
handle Outlook clients and I'm hoping that somebody here may be able |
to help with something similar that I can tune to get past Outlook's
behaviour.
maybe you want to try this:
# The settings below, which are actually the same as the defaults in the
# code, cause Exim to make RFC 1413 (ident) callbacks for all incoming
SMTP # calls. You can limit the hosts to which these calls are made,
and/or change # the timeout that is used. If you set the timeout to
zero, all RFC 1413 calls # are disabled. RFC 1413 calls are cheap and
can provide useful information # for tracing problem messages, but some
hosts and firewalls have problems # with them. This can result in a
timeout instead of an immediate refused # connection, leading to delays
on starting up an SMTP session.
rfc1413_hosts = *
rfc1413_query_timeout = 0s
Tom
