On Thu 03 Sep, Conor Mc Goveran wrote:
> > > run for its domain. Ideally I would like to have a separate queue per
> > > domain but as far as I can tell Exim does not favour this. Also I would
> >
> > nope, we couldn't make it do this. split_spool_queue option just splits up
> > the file space on the basis of messageid.
>
> Ditto.
The only way to do this would be to cause Exim to send those messages to
a differently configured version of Exim with its own spool area. This
could be done via a pipe or SMTP to a private port. The main Exim,
listening on port 25, would then be configured to run an appropriate
command to prod one of the others when it received ETRN, by means of the
etrn_command option.
You could probably manage this with a single Exim binary and a number of
different configuration files, passed to the special versions using the
-C option. For this application they could all run as exim, since no
root privilege would be needed.
--
Philip Hazel University of Cambridge Computing Service,
ph10@??? Cambridge, England. Phone: +44 1223 334714.
--
*** Exim information can be found at
http://www.exim.org/ ***
