Author: oliver Date: To: exim-users Subject: Re: [Exim] Under which circumstances Exim sends an automaticallygeneratedmessage to an extern user?
Note: I forgot still to say that we using Exim 4.10.
>
> That is very strange. Are you quite sure there's no "arrival" message?
> It would have been around 13:54:15.
>
No incomming message with the same id (18LOMR-0002Vn-00) in the
whole log file.
>
> > Maybe an impotant hint:
> > As a result of an misconfiguration there was no space left on the root
> > partition at that time the message was send.
> > But I don't think that this have caused the message.
> > (/var/spool/mail is mounted on it's own partition.)
>
> Is your Exim log in the root partition?
Yes it is.
> Is there anything on your system
> log around 13:54:15? Is there anything in the Exim panic log?
>
No there is nothing into the panic log and there is no incomming message
with the same id in the whole log file.
(Log file starting at 4 a.m.)
But I found something which could be of note.
An error has occurred in the shadow transport.
I'am still using the shadow transport for backing up incomming messages.
The shadow transport error was the result of a misconfiguration.
(Normally /mailserv2 is mounted to a remote nfs device and not to the local root filesystem.)
Here are the corresponding log entrys:
2002-12-09 14:52:45 18LOKu-0002UL-00 <= user1@??? H=merkur.hrz.uni-giessen.de [134.176.2.12] P=esmtp S=2376 id=xxxx
2002-12-09 14:52:45 18LOKu-0002UL-00 => user2 <user2@???> R=localuser T=local_delivery ST=local_backup_delivery (No space left on device: error while writing to /mailserv2/user2)
2002-12-09 14:52:45 18LOKu-0002UL-00 Completed
And then 91 seconds later Exim send another message to this (extern) user:
