2 %; forwcomps - Our components file when we're using "forw"
4 %; We want people to be able to use the components from forwarded
5 %; messages in this file, so we have to cheat a bit. We create a series
6 %; of pseudo-components with a "nmh" prefix to represent arguments given
7 %; on the command line. We don't do this for %{fcc} since there's already
8 %; precedence for this from "repl".
10 %; If we're given multiple messages to forward, provide the components
11 %; from the first one. Can't really think of anything better to do there.
13 %; Generate a "From:" header; if we don't give one, use %(localmbox)
15 %<{nmh-from}%|%(void(localmbox))%>%(void(width))%(putaddr From: )
17 %; Generate To: and cc: headers; if we're given ones, put something in there
18 %; otherwise leave them blank.
20 %<{nmh-to}%(void(width))%(putaddr To: )%|To:%>
21 %<{nmh-cc}%(void(width))%(putaddr cc: )%|cc:%>
23 %; If we're not given a -fcc switch, then default to +outbox
25 Fcc: %<{fcc}%(putstr)%|+outbox%>
27 %; If we're not given a -subject switch, then use the original message
28 %; subject, but adding (fwd) on the end. I got this idea from exmh, and
29 %; I've always liked it.
31 Subject:%<{nmh-subject} %(trim)%(putlit)%?{subject} %(trim)%(putlit) (fwd)%>