In message <199404281952.MAA20834@mango.synopsys.com>, Arnold de Leon writes:
> Majordomo uses "hidden" aliases to actually send mail
> to the members of the lists (typically listname-out).
> Anyone who knows the name of the list can send mail to
> the members directly. Sendmail version 8 makes it easier
> for recipients to discover this name since it is very
> good at recording envelope information in the
> "Received" headers.
Actually you could always get it because resend has the outgoing list
name right in the command invocation which is viewable with SMTP vrfy.
> My current idea for a "solution" is give majordomo
> a separate aliase file. The separte alise file
> can use "listname" as the address for resend to
> use for actually delivering mail. When resend
> invokes sendmail it will use the alternate (private)
> alias file.
I proposed this a few days ago on majordomo workers. If the sendmail
won't allow changing alias files using -o on the command line, have it
use a different config file.
> Are there better way of doing this?
> What about having resend talk to port 25 directly and
> expand the alias itself?
One problem is that the incomming addresses would show up in the
received headers. You know "Received: from localhost for
email@example.com ...". Sendmail 8 and most versions of IDA supply
this as do sgi default version (IDA based), and some svr4 based
sendmails. Sadly one of the features of majordomo is easy setup even
for those that are sendmail illiterate. Also what about the other SMTP
mailers that allow expn/vrfy?
> Comments, ideas?
The split alias idea is the only solution I can see. We have to allow
sendmail to expand the alias otherwise it can nicely put info into the
received headers that doesn't belong there.
Special Projects Volunteer University of Massachusetts at Boston
firstname.lastname@example.org (preferred) Boston, MA, (617) 287-6480
My employers don't acknowledge my existence much less my opinions.