On Thu, 9 Jul 1998, Philip Hazel wrote:
> > > The problem I see with this is that a message may have many recipients,
> >
> > I'm not sure that I fully understand why this is a problem ? Can you not just
> > apply the test to _each_ recipient, and if it matches, re-write, otherwise not ?
>
> Now *I'm* not sure I understand the requirement! I read Sean's comment
> to mean that he wanted to rewrite things (headers, envelope, whatever)
> only in the copy of a message that was sent to the particular recipient
> that had passed through a given director/router. Was this correct, Sean?
>
> I now see that perhaps I misunderstood him, and I have clearly
> misunderstood you! Is your requirement correctly stated thus:
>
> If an address is handled by a specific router or director, an option
> on that driver is able to request that rewriting take place on the
> addresses in the envelope and headers, exactly like the "global"
> rewriting rules. This rewriting will happen in the single copy of the
> headers, and therefore be visible to all recipients of the message.
That's what I would like :)
> In effect this is a private set of rewriting rules that gets triggered
> by the success of the router or director.
Spot on.
> That is simpler, but unfortunately not much. The problem is that when a
> message is deferred, the headers are re-written to the spool file for
> use at the next delivery attempt, so all this rewriting would be
> recorded, and if you've rewritten envelope addresses, they will be
> different next time. Either there has to be some extremely careful
> documentation of the consequences of all of this, or this rewriting has
> to be done on a copy of the headers and envelope so that they don't get
> saved. This is now getting similar to the problem I saw before :-(
You've lost me a little here, as well... :-(
DHS
-- David Sheryn <D.H.Sheryn@???> Postmaster, Computing Services
-- City University, Northampton Square, London, EC1V 0HB
-- Phone: (+44) 171 477 8000 Direct 0171 477 8196 Fax: 0171 477 8565
--
*** Exim information can be found at
http://www.exim.org/ ***
