On Wed, 8 Nov 2000 kuksi@??? wrote:
> And these mails aren't frozen messages...for example a new
> incoming message:
>
> ###########################################################################
> 2000-11-07 23:50:13 13tHZF-00038x-00 <=
> linux-kezdo-admin@??? H=localhost.localdom
> ain (localhost) [127.0.0.1] U=kuksi P=esmtp S=2411
> id=000701c0490d$408367d0$0a03a8c0@cele450a from
> <linux-kezdo-admin@???> for kuksi@localhost
> 2000-11-07 23:50:13 13tHZF-00038x-00 => kuksi <kuksi@localhost>
> D=procmail T=procmail_pipe
> 2000-11-07 23:50:13 13tHZF-00038x-00 Completed
> 2000-11-07 23:50:13 13tHZF-00038x-00
> link("/var/exim/spool/input//13tHZF-00038x-00-D", "/var/exim/
> spool/Finput//13tHZF-00038x-00-D") failed while moving message: No such
> file or directory
> ###########################################################################
>
> Look! The incoming message (13tHZF-00038x-00)is Completed!!
> And after the delivery comes the error message for the same
> mail(13tHZF-00038x-00-D)!
That's weird. It shouldn't be trying to move a frozen message after
completion. Something really odd is happening. Which version of Exim,
and which operating system are you using? Please run a delivery with -d9
set so as to get debugging output. That may help track this down.
The option to move frozen messages was requested by one specific user; I
don't think it is widely used! However, it is present in my testing
system, and it doesn't cause this problem in the standard tests.
--
Philip Hazel University of Cambridge Computing Service,
ph10@??? Cambridge, England. Phone: +44 1223 334714.
