Bug#501892: another reason for error 123 in /etc/cron.daily/exim4-base

[Martin Kaiser]

Dear exim4 maintainers,

I've just seen your bug report 501892. Although it's closed by now, I'd
like to add another comment.

I started getting the error 123 from /etc/cron.daily/exim4-base after
upgrading a box from etch to lenny. Eventually, I found out that the
reason was a file /var/log/exi4/db/vacation.db. This is created and used
by a domain-based vacation filter

      [...]
      once /var/spool/exim4/db/vacation.db 
      once_repeat 1d


I'm well aware that I could put this file everywhere else in the system.
When I set up the filter ages ago, I just happend to chose
/var/spool/exim4/db/

It looks like /etc/cron.daily/exim4-base did not produce an error until
the lenny version. It seems that when exim_tidydb is invoked
by start-stop-daemon with vacation.db as parameter, no error is returned.
The error started showing up when the lenny upgrade added something like

------- (snippet from the 4.71 package) --------
find $SPOOLDIR/db -maxdepth 1 -name '*.lockfile' -or -name 'log.*' \
-or -type f -printf '%f\0' | \
su - --shell /bin/bash \
     --command "xargs -0r -n 1 /usr/sbin/exim_tidydb $SPOOLDIR > /dev/null" \
     Debian-exim
-------------------------------------------------

This eventually invokes

exim_tidydb /var/spool/exim/db vacation.db which fails.

I was wondering if the filename selection for the find command shouldn't
be changed to search only for retry.db, wait-*.db and misc.db. AFAIK,
all other files can't be processed by exim_tidydb anyway.

Best regards,

   Martin