At 02:13 PM 3/25/01 , you wrote:
>Weird. It should have waited less. The first message was
>received at 09:51:14, so,if I'm not mistaken, it should have
>retried at roughly 12:00, 14:00, 17:00, 21:30, ...
>
> > I can't determine why not.
>
>Grep the manual for delay_after_cutoff.
I found the error... Debian has moved the exim.conf file to /etc/exim from
/etc. Closer inspection found that the exim crontab entry was testing for
the file in the old location before "suggesting" a queue run, and so the
nudge was never sent along. It could be an oversight in the Debian package
of 3.22, or more likely the fact that I grabbed version 3.22 from the
"unstable" distribution and put it on a "stable" installation to take
advantage of the newer features, and this change never made it to the
crontab (it's there now, however).
Since this wasn't happening, my guess is that the remote host came back up
shortly after the final delivery attempt, and the only thing that had been
triggering a queue run was new messages which were no longer arriving. Most
likely the fault of my own impatience, but I very much appreciate the
feedback that got me headed in the right direction.
> > otherdomain.com * F,5d,24h
>
>It's not that domain you tried to deliver to, is it?
No, that's for another, but it bears revising as well. That's not very
timely service. Perhaps they were late with
a payment recently.
>Do they have UNIX in casinos? ;)
Very good question, I frankly have no idea. I don't give them my money,
they don't give me theirs.... well, ok, they do in a rather indirect way :)
Jeff
-----------
Jeffrey B. Green Personal Computer Consultant - Las Vegas, Nevada
http://jbgreen.com Networking Las Vegas Since 1986
