I used two different config files (-c) to do a similar job, a bit of a pain in that you have to main two files but do-able as changes tend to be one of other file (pre or post exim).<br><br><a href="http://wiki.mailscanner.info/doku.php?id=documentation:configuration:mta:exim:installation">http://wiki.mailscanner.info/doku.php?id=documentation:configuration:mta:exim:installation</a><br>
<br><br clear="all">-- <br>Martin Hepworth<br>Oxford, UK<br>
<br><br><div class="gmail_quote">On 18 February 2011 11:21, George B. <span dir="ltr"><<a href="mailto:list1@gir.me.uk">list1@gir.me.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Hello,<br>
<br>
This is really an Exim question so feel free to tell me to ask elsewhere... ;-) It is related to my MailScanner configuration though.<br>
<br>
Apparently Exim 4.73 will not allow any "-D" options by default and eventually the functionality will be removed. From mailing list post:<br>
<br>
<a href="http://lists.exim.org/lurker/message/20101215.161702.fcdb3f77.gl.html" target="_blank">http://lists.exim.org/lurker/message/20101215.161702.fcdb3f77.gl.html</a><br>
---<br>
+# By contrast, you might be maintaining a system which relies upon the ability<br>
+# to override values with -D and assumes that these will be passed through to<br>
+# the delivery processes. As of Exim 4.73, this is no longer the case by<br>
+# default. Going forward, we strongly recommend that you use a shim Exim<br>
+# configuration file owned by root stored under TRUSTED_CONFIG_PREFIX_LIST.<br>
+# That shim can set macros before .include'ing your main configuration file.<br>
+#<br>
+# As a strictly transient measure to ease migration to 4.73, the<br>
+# WHITELIST_D_MACROS value definies a colon-separated list of macro-names<br>
+# which are permitted to be overriden from the command-line which will be<br>
+# honoured by the Exim user. So these are macros that can persist to delivery<br>
+# time.<br>
+# Examples might be -DTLS or -DSPOOL=/some/dir. The values on the<br>
+# command-line are filtered to only permit: [A-Za-z0-9_/.-]*<br>
+#<br>
+# This option is highly likely to be removed in a future release. It exists<br>
+# only to make 4.73 as easy as possible to migrate to. If you use it, we<br>
+# encourage you to schedule time to rework your configuration to not depend<br>
+# upon it. Most people should not need to use this.<br>
---<br>
<br>
I think I am already seeing symptoms of this on my Debian Squeeze box which relies (as per documentation of the rather old Debian MailScanner package) on the "-DOUTGING" option for the split pool configuration:<br>
---<br>
scruffy:~# exim4 -bP -DOUTGOING spool_directory<br>
macros_trusted overriden to true by whitelisting<br>
spool_directory = /var/spool/exim4<br>
<br>
vs<br>
<br>
scruffy:~# exim4 -bP spool_directory<br>
spool_directory = /var/spool/exim4_incoming<br>
---<br>
<br>
I have only just noticed this an I am looking for some advice on how to "future-proof" my Mailscanner + Exim4 implementation.<br>
<br>
The message above talks about a "shim configuration file" but I don't really understand what they are talking about there and how to use it for split pool configuration. :-(<br>
<br>
Any pointers would be greatly appreciated.<br>
<br>
<br>
Thanks,<br>
<br>
George.<br><font color="#888888">
-- <br>
MailScanner mailing list<br>
<a href="mailto:mailscanner@lists.mailscanner.info" target="_blank">mailscanner@lists.mailscanner.info</a><br>
<a href="http://lists.mailscanner.info/mailman/listinfo/mailscanner" target="_blank">http://lists.mailscanner.info/mailman/listinfo/mailscanner</a><br>
<br>
Before posting, read <a href="http://wiki.mailscanner.info/posting" target="_blank">http://wiki.mailscanner.info/posting</a><br>
<br>
Support MailScanner development - buy the book off the website! </font></blockquote></div><br>