>>>>> "Paul" == Paul Slootman <paul@???> writes:
Paul> On Thu 10 Sep 1998, Paul Mansfield wrote:
>> On Thu, 10 Sep 1998, Paul Slootman wrote:
>>
>> > Now, I currently have queue_smtp set, so that exim doesn't
>> immediately > cause a dialout when a message is sent. However,
>> I'd love to see some > way of telling exim it's ok to
>> immediately deliver a message when the > connection is up and
>> running (otherwise it'll be queued, and perhaps > cause a
>> dialout when 'exim -q' is run, and waste money).
>>
>> could a script which did this under a cron-job...
>>
>> #!/bin/sh
>>
>> ping smarthost-at-isp if [ ?$ -eq 0 ] ; then exim
>> -some-flags-which-trigger-email fi
Paul> Unfortunately not, because:
Paul> - a ping will cause a dialout as well (finding the state is
Paul> not the problem; as I said, state transitions are handled
Paul> via the ip-up and ip-down scripts).
Paul> - I'd like *immediate* delivery when the system is online
Paul> (or at least before the hangup occurs :-), doing this right
Paul> will require very frequent running of the script), just as
Paul> if queue_smtp is false; and delayed delivery when the system
Paul> is not online. Unfortunately the ip-down script is run
Paul> *after* the connection is down, otherwise that would be the
Paul> ideal location for a 'exim -q'.
Surely, asolution is just set a flag file in ip-up, and then remove
the flag file in ip-down, and instead of having runq on its own in as
the cron job have :
[ -e /this/is/my/flag/file ] && runq
Adrian
--
*** Exim information can be found at
http://www.exim.org/ ***
