Path: utzoo!yunexus!geac!syntron!jtsv16!uunet!peregrine!elroy!ames!mailrus!ukma!rutgers!att!ihlpb!gregg From: gregg@ihlpb.ATT.COM (Wonderly) Newsgroups: comp.mail.mh Subject: Re: learning mh Message-ID: <8982@ihlpb.ATT.COM> Date: 25 Oct 88 20:16:12 GMT Article-I.D.: ihlpb.8982 References: <376@tron.UUCP> Organization: AT&T Bell Laboratories - Naperville, Illinois Lines: 47 From article <376@tron.UUCP>, by carson@tron.UUCP (Dana Carson): > > A specific question is how do I tailor my headers. I want to > always have a Fcc line in the header. The components file seems to be > the place to start but I don't want to change it for everybody on the > system :-). What is the user level way to do it. I've tried a > components file in ~HOME, a .components , and the same in ~HOME/Mail. While not completely obvious, it is true that each mh program looks for a line in YOUR .mh_profile file when it starts up. That line starts with the program name followed by a colon. For example, comp looks for the line beginning with 'comp:'. These lines contain default command line arguments that you would like to give to a particular command. I use lines like scan: -form scan.st repl: -annotate -filter inbody -nocc me next: -noheader prev: -noheader send: -msgid -verbose -alias aliases show: -noheader ali: -alias aliases in my .profile. One of the real benefits of this setup is that you can copy repl (or comp) to a file by another name, e.g. thanks, and add the line thanks: -format thankscomp to you .mh_profile and create the file 'thankscomp' in you mh directory. It can contain whatever you want. In this example it might just say ...header stuff as from replcomps... Thanks... ...your signature... or it might be as personal as you want. You can do the same thing with comp to allow you to use mail messages with precomposed To: lists. There are lots of other posibilities... Gregg Wonderly -- Gregg Wonderly AT&T Bell Laboratories DOMAIN: gregg@ihlpb.att.com IH2D217 - (312) 979-2794 UUCP: att!ihlpb!gregg