On Thu, 4 Dec 2003, Mike Richardson wrote:
> However the current behaviour seems to be that exim is sending a bounce
> *and* freezing the message. I've read through the docs and as far as I can
> tell unless temp_errors or ignore_status is set exim *should* treat the
> above as a permenant error.
>
> Here is an appropriate log extract:
>
> root@scree:/var/log/exim4# fgrep 1ARpCO-0000Eg-2F mainlog
> 2003-12-04 08:51:00 1ARpCO-0000Eg-2F <= www@??? H=serenity.mcc.ac.uk [130.88.200.93] P=esmtp S=1036 id=E1ARpBt-0000oK-00@???
> 2003-12-04 08:51:00 1ARpCO-0000Eg-2F <asdf@???>: afs_mail_spool transport output: Aborting (code 1: asdf:: Can't find addressee in passwd file.)
> 2003-12-04 08:51:00 1ARpCO-0000Eg-2F ** asdf@??? R=afs_local_user T=afs_mail_spool: Child process of afs_mail_spool transport returned 128 from command: /local/packages/afsmail/bin/afsdeliver
> 2003-12-04 08:51:00 1ARpCO-0000El-5F <= <> R=1ARpCO-0000Eg-2F U=mail P=local S=1992
> 2003-12-04 08:51:00 1ARpCO-0000Eg-2F Completed
That looks like a permanent failure of 1ARpCO-0000Eg-2F to me, followed
by the creation of a bounce. Followed by "Completed", which means it has
got rid of the message. Not logging sign of freezing. Is
1ARpCO-0000Eg-2F still there after this? If so, something is badly
wrong. A message should never be there after "Completed".
Are you sure it isn't the *bounce* that is getting frozen?
--
Philip Hazel University of Cambridge Computing Service,
ph10@??? Cambridge, England. Phone: +44 1223 334714.
Get the Exim 4 book: http://www.uit.co.uk/exim-book
