🚀 go-pugleaf

In article <JOE8UIP@odb.rhein-main.de> oli@odb.rhein-main.de (Oliver Boehmer) writes:
>I understand that full expansion features is tricky with variables
>like config_file, method_dir, transport_file, etc. But why are not all
>variables in the actual transports/routers/directors being expanded? Too
>much work?
>Let me tell you one of the goals I have: based on the $sender_host I want
>to assign a different value to the "path" or the "method" attribute of the 
>smart_host router. 

It may be possible to adjust the path attribute to be an expansion
string variable.  However, the historical implementation of method
files would have to be completely rewritten for this to work (they
should be reimplemented anyway, so it isn't such a bad thing).  The
problem is that method files are interpreted when the router file
is scanned.  To base the method file on the $sender_host, smail
would have to delay reading the method file until the sender_host
is known.

Also, you can usually do these kinds of expansions with the queryprogram
router, although this isn't very efficient.
-- 
	tron |-<=>-|		ARPAnet:  veritas!tron@apple.com
      tron@veritas.com		UUCPnet:  {apple,pyramid}!veritas!tron