I am having a problem getting Exim4 to obey the following options:
queue_only=true
queue_run_max=0
My goal is to have Exim receive messages but not deliver them until I
am ready for them.
I did, in fact, have this working as I wanted to at one time. But
now, with no changes to the system of which I am aware, it no longer
works.
We are running Debian and Exim4.
Exim is configured to use separate configuration files in the
following directory structure:
/etc/exim4/conf.d
:
:
v
/acl
/auth
/main
/retry
/rewrite
/router
/transport
With /etc/exim4/main/02_exim4-config_options being the primary main
configuration file and where the above mentioned queue options are
placed.
Exim is then stopped and re-started. I see the new options appear
in /var/lib/exim4/config.autogenerated.
But, exim processes messages as though nothing had changed. Here is
what mainlog looks like as exim is restarted:
2005-07-05 14:14:33 IPv6 socket creation failed: Address family not
supported by protocol
2005-07-05 14:14:33 Failed to create IPv6 socket for wildcard
listening (Address family not supported by protocol): will use IPv4
2005-07-05 14:14:33 IPv6 socket creation failed: Address family not
supported by protocol
2005-07-05 14:14:33 Failed to create IPv6 socket for wildcard
listening (Address family not supported by protocol): will use IPv4
2005-07-05 14:14:33 exim 4.33 daemon started: pid=26002, -q5m,
listening for SMTP on port 25 (IPv4) port 587 (IPv4)
2005-07-05 14:14:33 Start queue run: pid=26005
2005-07-05 14:14:33 End queue run: pid=26005
As you can see, a queue run begins as soon as exim is started.
Messages that are received are then authenticated and delivered as if
queue_only were false and queue_run_max were greater than 0,
There are no Exim processes running other than this daemon.
Can you please give me some much needed guidance on this functionality.
Thank you,
Mike
