[Exim] eximon problem

Αρχική Σελίδα
Delete this message
Reply to this message
Συντάκτης: Andreas Behnert
Ημερομηνία:  
Προς: exim-users
Αντικείμενο: [Exim] eximon problem
Sorry 'bout my poor English :)

Exim 3.35, Linux Debian 3.0r0 aka "Woody", x86

two configuration files:
/etc/exim/exim.conf (incoming)
/etc/exim/exim-outgoing.conf (outgoing)

The "incoming" configuration just uses "queue_only = true"
and a defer director: driver = smartuser
                       new_address = :defer: All dlvs. are deferred


Mailcanner software (http://www.sng.ecs.soton.ac.uk/mailscanner/)
is scanning all messages from the incoming queue, adding some headers
and pushing them to the "outgoing" Exim. So the "outgoing" Exim is
doing all the "real" MTA stuff and this is the Exim "incarnation"
where all things like frozen messages etc. can occur. The whole
Exim configuration is working without any problem.

I'm using eximon. Eximon for the "incoming" queue-only config
is some kind of pointless but it is important for the "outgoing"
config.
I copied the /usr/sbin/eximon script to /usr/sbin/eximon.outgoing
and changed the file to use some other variables, for instance
all "/etc/exim/exim.conf" are now "/etc/exim/exim-outgoing.conf".
PATH variables are being correctly extracted, LOG_FILE_PATH and
the rest are ok (verified with "echo $FOO") but:
If I'm using the eximon menu (Shift-LeftClick) to work with the
queue files (at the moment there are lots of frozen messages
because of a network failure some days ago) and to start some
thing like "thaw message" or "deliver message" etc. there's
always a failure notice like "spool file ... not found" or "Spool
data for ... does not exist". The reason is that Exim is being
called with "/usr/sbin/exim <operation> <msg-ID>" - but without the
option that points to the exim-outgoing.conf file. So it just uses
the standard exim.conf which of course points to another spool
directory.
Is it possible to teach eximon.outgoing to use the outgoing.conf
file instead of the standard one? Again - the "outgoing" eximon
screen shows the correct log files and the correct spool contents -
just the operations on messages are not working because of Exim
being called without the exim-outgoing.conf option...


(Sorry if I just spammed the list - I just wanted to decribe the
problem as good as possible :)

Regards,
Andreas