On Tue, 27 Jan 1998, Brad Mohning wrote:
> We have an alias for all System Administrators called sysadm. One of
our group was moving offices and subsequently shutdown his workstation.
This caused all e-mail sent to the sysadm alias to be deferred, since
Exim could no longer read his .forward file. When I booted his system
again, the messages were delivered.
> So, my question, is there a setting to have the message delivered to
the other recipients while it is deferred for only the "offending" user?
That should be the way Exim works normally. You will see "sysadm" as an
undelivered address in Eximon and in exim -bp lists, since delivery to
it has not been completed, but in fact all other addresses generated on
that alias should have been delivered. You can check this by reading the
mainlog files for appropriate messages to check what happened to them.
Now, if the above isn't the case, then either there's some bug I am not
aware of, or there are some special circumstances that apply in your
case. If you can find one of the messages that got delayed, get hold of
its message id and use exigrep to get all the relevant log entries, e.g.
exigrep 0xxTzM-0001vO-00 /var/spool/exim/log/mainlog
That should give the entire history of the message. (You may have to
include other log files if the incident lasted over a log cycling
operation.)
--
Philip Hazel University Computing Service,
ph10@??? New Museums Site, Cambridge CB2 3QG,
P.Hazel@??? England. Phone: +44 1223 334714
--
*** Exim information can be found at
http://www.exim.org/ ***
