Path: utzoo!attcan!uunet!husc6!uwvax!dogie!uwmcsd1!ig!agate!pasteur!cory.Berkeley.EDU!dheller From: dheller@cory.Berkeley.EDU (Dan Heller) Newsgroups: comp.mail.misc Subject: Re: making the Mail reply command use From_ rather than From: Message-ID: <4250@pasteur.Berkeley.Edu> Date: 4 Jul 88 21:37:12 GMT References: <10682@andante.UUCP> <8120014@hpfclp.SDE.HP.COM> Sender: news@pasteur.Berkeley.Edu Reply-To: dheller@cory.Berkeley.EDU.UUCP (Dan Heller) Organization: University of California, Berkeley Lines: 28 In article <8120014@hpfclp.SDE.HP.COM> diamant@hpfclp.SDE.HP.COM (John Diamant) writes: >> For example, I set mine to Reply-To, Return-Path, From. This is usually >> the best list to choose from. >I'm surprised you haven't been burned by this. Return-Path is not a valid >header to use for replies. In many cases, it holds the path only back to the >last system, not the originator. If you check your RFCs, it isn't intended >as an originator mail path. But in many cases it is a legitimate path. Of course, I check the path anyway to see if it is correct. In the cases where it isn't, I just kill the reply and reply again with different values in my reply_to_hdr variable. Because Mush has command line aliases, I condense all the required commands to simple keystrokes ... mush> cmd R 'set reply_to_hdr = reply-to ; replyall' mush> cmd r 'unset reply_to_hdr ; replysender' etc... "cmd" is the way to set a command line alias ("alias" is reserved for compatibility with Mail). Now, all I have to do is use R, r, or one of my other aliases. Because not all mailers guarantee that the correct address will be in the same header, I can't use the same set of headers to get the reply path. Besides, the whole point to my posting was that mush makes it _configurable_ about which header you want to use. Dan Heller