>>>>> "DB" == Dave Barr <email@example.com> writes:
>> 1. You might not want the list owner changing it (easy to fix, put it in
>> majordomo.cf instead).
DB> Or modify majordomo to allow that keyword to be updated only by the
DB> majordomo admin's password.
Well, now we're out of the realm of the simple fix that you mentioned that
this would be. This is a rewrite of the entire config system.
DB> (As a general concept this is a very good thing for majordomo to have -
DB> specific list variables which are viewable but not necessarily
DB> modifiable except by the majordomo owner.)
Well, we'll get to it eventually, as people seem to want this. I'm still
not convinced that this is useful, but that's just me. If the list owner
can't change it, I figure putting it in the config file will only be a
source of frustration.
>> 2. That doesn't really hide it. Some mailers will still reveal the
DB> Yes, but that can easily be fixed.
But the problem is that fixing it is mailer-dependent. Sometimes we have
to tack on extra cruft to what we tell sendmail is the outgoing alias (like
an extra comma or something), sometimes you have to add extra cruft in the
aliases. The first requires Majordomo to know more about the mailer, which
makes me uneasy. As for the second, well, I thought the idea was to
eliminate the games you have to play in the alias file to hide the outgoing
>> Don't use them at all. I expect that in the future Majordomo will just
>> talk SMTP itself and not pass an alias to sendmail.
DB> Both of these are a big departure, but I think the latter is
DB> preferable. It would be nice to do SMTP in a configurable way (like
DB> specifying '$mailer = "SMTP:mailhost"', meaning to use internal SMTP to
DB> 'mailhost' instead of calling an external program)
What a coincidence that I already wrote the code. Blah blah TLB plug blah.
It isn't built into Majordomo, but you (can, if you want to do so) call it
as a $mailer and get rid of your outgoing aliases. It does a bunch of
other stuff, too, but you can turn it all off. ftp.hpc.uh.edu:/pub/tlb. A
few people are using it and it seems to be working well, but it is alpha
code. Bugs seem to be few in number (and mostly in documentation), but I
have more I want to do with it before it gets a real release.