Tony Finch wrote:
> On Wed, 7 Jun 2006, Mordur wrote:
>
>> Any ideas?
>>
>
> You didn't follow the instructions precisely - you changed the name of
> the macro which caused macro name problems.
>
> Tony.
>
This is true. I have partially followed the instructions for Exim
contained in the Debian package, and partially the document you
mentioned and have a well functioning setup.
I have also solved my little problem:
/etc/defaults/exim4 contains the following after I changed it to bet
suitable for use in my situation:
# /etc/default/exim4
EX4DEF_VERSION=''
# 'combined' - one daemon running queue and listening on SMTP port
# 'no' - no daemon running the queue
# 'separate' - two separate daemons
# 'ppp' - only run queue with /etc/ppp/ip-up.d/exim4.
# 'nodaemon' - no daemon is started at all.
# 'queueonly' - only a queue running daemon is started, no SMTP listener.
# setting this to 'no' will also disable queueruns from
/etc/ppp/ip-up.d/exim4
QUEUERUNNER='separate'
# how often should we run the queue
QUEUEINTERVAL='15m'
# options common to quez-runner and listening daemon
COMMONOPTIONS=''
# more options for the daemon/process running the queue (applies to the one
# started in /etc/ppp/ip-up.d/exim4, too.
QUEUERUNNEROPTIONS='-DOUTGOING'
# special flags given to exim directly after the -q. See exim(8)
QFLAGS=''
# options for daemon listening on port 25
SMTPLISTENEROPTIONS='-odq'
So of course what I need to do to get an exim4 invocation to operate on
"the other" spool directory is to use the -DOUTGOING option. For example:
exim4 -bp -DOUTGOING
14h 1.6K 1FnrTv-0000v0-5Z <> *** frozen ***
root@???
I should have looked a little longer for the solution, sorry about
that. Thank you for your effort Tony.
Mordur
