Go to the first, previous, next, last section, table of contents.

The Built-in Header Rewrite Functions

Below are examples of the styles of the various built-in header rewrite functions. Please note the following: first, the text which appears in the examples below as `fieldkey' indicates that the value of a particular information key corresponding to `fieldkey' will be inserted there. (See section Mail Fields and Information Keys). For example, in sc-header-on-said below, `date' and `from' correspond to the values of the `Date:' and `From:' mail headers respectively.

Also, the string ">>>>>" below is really the value of the variable sc-reference-tag-string, which is user definable. Finally, the references headers actually written may omit certain parts of the header if the information key associated with fieldkey is not present. In fact, for all built-in headers, if the `From:' field is not present in the mail headers, the entire reference header will be omitted.

sc-no-header
This function produces no header. It should be used instead of nil to produce a blank header. This header can possibly contain a blank line after the mail-header-separator line.
sc-no-blank-line-or-header
This function is similar to sc-no-header except that any blank line after the mail-header-separator line will be removed.
sc-header-on-said
>>>>> On date, from said:
sc-header-inarticle-writes
>>>>> In article message-id, from writes:
sc-header-regarding-adds
>>>>> Regarding subject; from adds:
sc-header-attributed-writes
>>>>> "sc-attribution" == sc-author <sc-reply-address> writes:
sc-header-verbose
>>>>> On date,
>>>>> sc-author
>>>>> from the organization of organization
>>>>> who can be reached at: sc-reply-address
>>>>> (whose comments are cited below with: "sc-cite")
>>>>> had this to say in article message-id
>>>>> in newsgroups newsgroups
>>>>> concerning the subject of subject
>>>>> see references for more details

Go to the first, previous, next, last section, table of contents.