In the exim 4 plan you call for comments on the "include" syntax.
The use of '#' as a start-of-include line would confuse comment usage, but
may also mislead users into making assumptions about CPP like behaviours. I
would also like to be able to include external files "inline" for complex
lookups or conditions.
For non-inline includes, maybe $INCLUDE, like named zone files ? Other wise
#include would be fine by me.
For inline includes (if feasible) could exim support an additional
${include:xxx} ?
Forget it if that is getting to complex to maintain...
rgds,
--
Peter Galbavy
Knowledge Matters Ltd.
http://www.knowledge.com/
