For me, the process was so dead that even exim_what couldn't see
it. I found the process by looking for any very old exim processes
that weren't the daemon.
It stopped happening for me (so far) when I added a "connect_timeout =
3m" to my remote_smtp transport. So, it looks like:
remote_smtp:
driver = smtp
connect_timeout = 3m
Apparently my Caldera system does not have it's own timeout on a
connect call. It's supposed to. But this is the work-around.
Philip worked a long time with me to figure that this was partly
responsible for the duplicate messages I was generating.
I should write a little report for this list and this archive. I
will, but with a different subject so people can find it.
Marilyn Davis, Ph.D.
eVote - online polling software for email lists
http://www.deliberate.com
marilyn@???
+1 650 965-7121 (USA)
On Wed, 17 May 2000, Yann Golanski wrote:
> FAQ add time?
>
> On Wed, May 17, 2000 at 05:19:46PM +0200, yann algayon wrote:
> > I have a message in the spool.
> > this message couldn't be delivered because of a timeout expiration from
> > the remote smtp server.
> >
> > when I try to deliver this message in eximon, I have the following
> > error message :
> >
> > SPOOL FILE IS LOCKED
> >
> > how can I deliver this message again
>
> Run exiwhat, find the exim proccess that has gone mad and kill it.
> Happens from time to time.
>
> --
> Dr Yann Golanski Internet Systems Developer
> PGP: www.kierun.org/pgp/key Mailmaster for the Planet Online
>
> --
> ## List details at http://www.exim.org/mailman/listinfo/exim-users Exim details at http://www.exim.org/ ##
>
