On Wed, 18 Aug 2010 13:07:35 -0400, Phil Pennock
<[email protected]> wrote:
> The split configuration system is a Debian addition, not supported here
> at the upstream; you should have a README.Debian.gz in
> /usr/share/doc/exim4/ which walks you through making sure that you
> regenerate the configuration file from the parts, if needed.
Anyway, all I did was transplant my configuration change,
exactly as I wrote it last night, from the
file under conf.d to the single configuration template.
The setup now passes the hello-world test: a test message now
goes into my maildir inbox.
webserver:/etc/exim4# quilt diff
Index: exim4/exim4.conf.template
===================================================================
--- exim4.orig/exim4.conf.template 2010-08-18 11:52:21.000000000
-0700
+++ exim4/exim4.conf.template 2010-08-18 11:57:30.000000000 -0700
@@ -1431,6 +1431,16 @@
envelope_to_add
return_path_add
+ maildir_format
+
+ directory = ${if eq{$address_file}{inbox} \
+ {$home/Maildir} \
+ {${if eq{${substr_0_1:$address_file}}{/} \
+ {$address_file} \
+ {$home/Maildir/$address_file} \
+ }} \
+ }
+
#####################################################
### end transport/30_exim4-config_address_file
#####################################################
But multiple things refer to the address_file transport.
Is it really okay to do this?
For instance the "mail4root" router wants to be able
to use the address_file transport to add
to /var/mail/mail.
Surely, the right thing is to create a new transport
which is a clone of address_file, but under a different
name?
--
## List details at http://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/
