On Sat, 25 May 2002, Florian Weimer wrote:
> Enabling debugging reveals that
>
> | direct command:
> | argv[0] = /usr/local/sbin/ezmlm-to-mailman
> | argv[1] = ${sg{$local_part}{-(?:un)?subscribe\$}{}}
> | argv[2] = $domain
> | argv[3] = ${sg{$local_part}{^.*-}{}}
>
> is expanded to:
>
> | direct command after expansion:
> | argv[0] = /usr/local/sbin/ezmlm-to-mailman
> | argv[1] = authors
> | argv[2] = lists.cert.uni-stuttgart.de
> | argv[3] = authors
>
> while I would have expected:
>
> | direct command after expansion:
> | argv[0] = /usr/local/sbin/ezmlm-to-mailman
> | argv[1] = authors
> | argv[2] = lists.cert.uni-stuttgart.de
> | argv[3] = subscribe
>
> Is my expectation wrong? If yes, why?
Your expectation is correct. However, I cannot reproduce this error. I
get this:
--------> authors-subscribe@??? <--------
locking /home/ph10/exim4/test/spool/db/retry.lockfile
locked /home/ph10/exim4/test/spool/db/retry.lockfile
opened hints database /home/ph10/exim4/test/spool/db/retry: flags=0
dbfn_read: key=T:authors-subscribe@???
no retry record exists
search_tidyup called
changed uid/gid: local delivery to authors-subscribe <authors-subscribe@???> transport=list_subscribe_transport
uid=1169 gid=1169
auxiliary group list: <none>
home=/ current=/
set_process_info: 12001 delivering 17FXYU-00037X-00 to authors-subscribe using list_subscribe_transport
list_subscribe_transport transport entered
direct command:
argv[0] = /usr/local/sbin/ezmlm-to-mailman
argv[1] = ${sg{$local_part}{-(?:un)?subscribe\$}{}}
argv[2] = $domain
argv[3] = ${sg{$local_part}{^.*-}{}}
direct command after expansion:
argv[0] = /usr/local/sbin/ezmlm-to-mailman
argv[1] = authors
argv[2] = my.host
argv[3] = subscribe
So the question now becomes, what is different on your host? I copied
your transport exactly, changing only the user and directories.
--
Philip Hazel University of Cambridge Computing Service,
ph10@??? Cambridge, England. Phone: +44 1223 334714.
