On Sun, 18 Jun 2006, Mathias Lagerwall wrote:
> 19072 set_process_info: 19072 delivering 1Fs3E6-0004xZ-2H to vactest using uservacation_transport
> 19072 uservacation_transport transport entered
> 19072 taking data from transport
> 19073 exec /usr/sbin/exim4 -d=0xfbbd5cfd -t -oem -oi -f <> -E1Fs3E6-0004xZ-2H
> 19073 Exim version 4.34 uid=5503 gid=100 pid=19073 D=fbbd5cfd
> 19073 changed uid/gid: forcing real = effective
> 19073 uid=0 gid=100 pid=19073
> 19073 auxiliary group list: <none>
> 19073 configuration file is /var/lib/exim4/config.autogenerated
> 19073 log selectors = 00000ffc 00010400
> exim: debugging permission denied
That's a bit odd. Exim ought to pass debugging information to child
processes properly. What are your exim_user, exim_group, and admin_groups
settings?
> 19072 uservacation_transport transport succeeded
> 19072 search_tidyup called
> 19070 uservacation_transport transport returned DEFER for vactest@???
> 19070 added retry item for T:vactest@???: errno=0 0 flags=0
> 19070 post-process vactest@??? (1)
> 19070 LOG: MAIN
> 19070 == vactest@??? R=uservacation T=uservacation_transport defer (0): Failed to send message from uservacation_transport transport (1)
The problem is somewhere in the child process that refused to produce any
debugging output :-(
Tony.
--
<fanf@???> <dot@???>
http://dotat.at/ ${sg{\N${sg{\
N\}{([^N]*)(.)(.)(.*)}{\$1\$3\$2\$1\$3\n\$2\$3\$4\$3\n\$3\$2\$4}}\
\N}{([^N]*)(.)(.)(.*)}{\$1\$3\$2\$1\$3\n\$2\$3\$4\$3\n\$3\$2\$4}}
