>>>>> "JG" == Jeffrey Goldberg <J.Goldberg@cranfield.ac.uk> writes:
JG> Hmm. At first I thought that that was pointless because you would need
JG> the name of the outgoing list, but of course EXPN on the list name
JG> itself will give you that.
XYX:sina:~> telnet sina smtp
Trying 22.214.171.124 ...
Connected to sina.hpc.uh.edu.
Escape character is '^]'.
220 sina.hpc.uh.edu ESMTP Sendmail 8.7.3/8.7.3; Tue, 18 Nov 1997 13:14:17-0600 (CST)
250 sina.hpc.uh.edu Hello tibbs@Sina.HPC.UH.EDU [126.96.36.199], pleased to meet you
250 <"|/usr/local/lists/majordomo/wrapper resend -l fvwm -h hpc.uh.edu nobody"@sina.hpc.uh.edu>
JG> And what good does that do:
Well, not much. My list is distributed by TLB, which is called directly by
Majordomo; the MTA doesn't get involved until TLB contacts it and feeds
addresses to it. Other bonuses are that the list files can be mode 600 and
security cannot be broken by sending to the outgoing alias.
The down side is that TLB is hard to configure, isn't clean under perl
5.004 and is no longer supported by me. (Sorry; too much time spent on
other things.) As far as I know there is nothing else that works in quite
the same way. You can put bulk_mailer in your outgoing alias, ehich
protects against EXPN but still keeps the outgoing alias around. You can
have Majordomo call bulk_mailer directly (which is probably the best
solution) but then you have problems with archive and digest.
For grins, here is what my development version of the mythical future
version of Majordomo gets you:
250 <"|/home/tibbs/mj/2.0-snap/bin/mj_resend -d hpc.uh.edu -l test-list"@sina.hpc.uh.edu>
Note that you can't even give an outgoing address; there simply isn't one.