---

1.8 Forwarding

The message-forward command pops up a message buffer to forward the message in the current buffer. If given a prefix, forward using news.

message-forward-ignored-headers ¶

In non-nil, all headers that match this regexp will be deleted when forwarding a message.

message-forward-included-headers ¶

In non-nil, only headers that match this regexp will be kept when forwarding a message. This can also be a list of regexps.

message-forward-included-mime-headers ¶

In non-nil, headers that match this regexp will be kept when forwarding a message as MIME, but MML isn’t used. This can also be a list of regexps.

message-make-forward-subject-function ¶

A list of functions that are called to generate a subject header for forwarded messages. The subject generated by the previous function is passed into each successive function.

The provided functions are:

message-forward-subject-author-subject ¶

Source of article (author or newsgroup), in brackets followed by the subject.

message-forward-subject-fwd

Subject of article with ‘Fwd:’ prepended to it.

message-wash-forwarded-subjects ¶

If this variable is t, the subjects of forwarded messages have the evidence of previous forwards (such as ‘Fwd:’, ‘Re:’, ‘(fwd)’) removed before the new subject is constructed. The default value is nil.

message-forward-as-mime ¶

If this variable is t, forwarded messages are included as inline MIME RFC822 parts. If it’s nil (the default), forwarded messages will just be copied inline to the new message, like previous, non MIME-savvy versions of Gnus would do.

message-forward-before-signature ¶

If non-nil, put forwarded message before signature, else after.