🚀 go-pugleaf

In article <115054@sun.Eng.Sun.COM> argv@sun.com (Dan Heller) writes:
> In article lyndon@cs.AthabascaU.CA (Lyndon Nerenberg) writes:
> > In article <114962@sun.Eng.Sun.COM> argv@sun.com (Dan Heller) writes:
> > >In mush you can do this by setting "no_expand".  Anything you have on the
> > >To: line remains untouched.
> > 
> > YOW! This is not a Good Thing to do.
> 
> Precisely.  That is the intention.  And it's not uncommon either.  There
> are many mailing lists that are supposed to be "one-way" -- that is, the
> moderator mails out, but no one can mail to the list.  This is one way to
> do that.

But the `real' way to do this is with mail groups, ala RFC822.  The `To:' line
can be specified as:

	To: user1, some_alias: user2, user3, ..., usern ;

to which the originating MTA is supposed to strip the mailboxes from the group,
leaving:
	
	To: user1, some_alias:;

Thus, this is a "one-way" alias - it can't be replied to.  Sadly, some
sendmail's become ill when originating group syntax.

BTW, I just put up 6.5.6 and installed the new default Mushrc.  Next time
I ran mush, it said "oh I see you're a new user to mush...".  While this
behavior might be desireable for someone who's really a new user to mush,
having to create a .mushexpert file to elide that behavior just clogs my
home directory.  Worse still, I realized that mush was always sourcing the
default Mushrc (before my .mushrc!).  So, naturally I thought to use "mush -n"
to prevent the sourcing of it, but that also prevents it from sourcing my
.mushrc - and leaves me with no identical way of having my .mushrc sourced
before the folder is read.  *Sigh*.  I wouldn't mind leaving the new default
Mushrc there for new users (its a help to them), but when a user has a .mushrc,
mush shouldn't go off and amuse what it should be sourcing.  My fix: I left
the Mushrc there, but removed the code from main.c that first sources Mushrc
and then goes off to source the .mushrc.  (It even looks from this code that
if I don't have a .mushrc, it will source Mushrc twice!).

Lastly, while it's nice mush no longer makes complains about changing the
"From:" header, it still provides its own (incorrect) "From:" header, even
when I've got a better set in my_hdrs.  This is just a matter of an #ifdef
here and there.  While this can be used for when I have to send mail from
my other domain, it would at least allow me to get around one other problem,
which is that mush makes From: headers thus:
	From: loverso@xylogics.com (John Robert LoVerso)
instead of:
	From: "John Robert LoVerso" <loverso@xylogics.com>
I prefer the latter, since I don't like putting somewhat important imformation
(my name!) in what is actually a comment that any MTA is allowed to strip off.

I've now been using mush for nearly 10 months - thats the longest I've stuck
with a new mailer ever.  Every time I switched to MH (almost a dozen times over
the course of 5 years), it would last for two or three weeks before I'd plod
back into UCB Mail.  I doubt that could happen now.  The best feature of mush
is the ability to incorporate new mail into the window interface - its good
for those like me who end up with 500 messages sitting around from the last
few weeks...  (I still miss the ability to make composition drafts, and leave
them incomplete - edit_hdrs *almost* lets me do this painlessly).
Anyway, this is to say, "mush is great - thanks a lot, Dan, Bart, et al!".

Ramblingly yours...
John

-- 
John Robert LoVerso			Xylogics, Inc.  617/272-8140
loverso@Xylogics.COM			Annex Terminal Server Development Group
buita!xylogics!loverso			[formerly of Encore Computer Corp]