Path: utzoo!attcan!uunet!cs.utexas.edu!sun-barr!newstop!sun!argv From: argv@turnpike.Eng.Sun.COM (Dan Heller) Newsgroups: comp.mail.misc Subject: Re: user's aliases on the To: line (was: UUnet and munging headers.) Message-ID: <138046@sun.Eng.Sun.COM> Date: 28 Jun 90 20:47:58 GMT References: <2777.AA2777@julie> <136802@sun.Eng.Sun.COM> <7329@gollum.twg.com> <10128@ogicse.ogc.edu> <2705@litchi.bbn.com> Sender: news@sun.Eng.Sun.COM Organization: O'Reilly && Associates Lines: 33 In article <2705@litchi.bbn.com> rsalz@bbn.com (Rich Salz) writes: > |If he sets $no_expand in mush and gives the command > | mail everybody > |mush will send out a message with the headers (among others) > | From: joe@joes.domain.org > | To: everybody > > It is totally wrong to send out mail with an invalid address. You're reacting out of context and are giving readers a skewed view based on your statement. Bart said the above, but noted that we have acknowledged that it was wrong and are considering better options. The problem is not that simple to solve since many sites don't recognize or do the same thing with any arbitrary header. > If you must provide a "no_expand" sort of facility, leave OFF the to > address and treat everyone as Bcc recipients. That's silly -- you must have a To: line or most MTAs such as sendmail will add one for you in the form of Apparently-To: and that's not going to contain very useful information either. The bottom line is, Mush's solution is "adequate" in that it doesn't provide any more or less than what other mailing lists do. However, it's not good enough in that it doesn't conform to the RFC. -- dan ---------------------------------------------------- O'Reilly && Associates argv@sun.com / argv@ora.com Opinions expressed reflect those of the author only.