On Thu, 13 Aug 1998 arb-exim@??? wrote:
> So going back to my original problem, while this scenario works quite well
> most times, it fails when a mail has come via a .forward file whose
> original domain is not the same as the virtual domain.
OK. I think I see the problem. The way you have set things up, the
normal case is
original-domain1 => new-domain
original-domain2 => new-domain
and you can distinguish on the original domain. But if it happens that
when processing new-domain you hit a .forward file, you might get
original_domain1 => intermediate-domain1 => final_domain
and you want to distinguish on the intermediate domain, not the original
one. In general there could be any number of intermediate domains. Exim
doesn't help you in this situation. I suppose what you want is
$immediately_previous_domain (or $parent_domain), but that does seem a
very specialised facility. What do others on the list think? Would
$parent_domain be a generally useful thing to have available? My own
feeling is that it should be empty in the case of a top-level domain
(i.e. when there is no parent).
> OK. I don't have much to report. As before, there was a core file in exim's
> spool directory. I ran gdb, and it reported that exim had exited on signal
> 11.
If you still have it, could you try running the "where" command in gdb?
That should give some information as to where in the program it crashed.
Philip
--
Philip Hazel University of Cambridge Computing Service,
ph10@??? Cambridge, England. Phone: +44 1223 334714.
--
*** Exim information can be found at
http://www.exim.org/ ***
