Bcc => ADDRESSES

Receivers of blind carbon copies: their names will not be published to other message receivers.

Cc => ADDRESSES

The carbon-copy receivers, by default a copy of the "Cc" field of the source message.

From => ADDRESSES

Your identification, by default taken from the "To" field of the source message.

Message-ID => STRING

Supply a STRING as specific message-id for the reply. By default, one is generated for you. If there are no angles around your id, they will be added.

Subject => STRING|CODE

Force the subject line to the specific STRING, or the result of the subroutine specified by CODE. The subroutine will be called passing the subject of the original message as only argument. By default, Mail::Message::replySubject() is used.

To => ADDRESSES

The destination of your message. By default taken from the "Reply-To" field in the source message. If that field is not present as well, the "From" line is scanned. If they all fail, "undef" is returned by this method: no reply message produced.

body => BODY

Usually, the reply method can create a nice, sufficient message from the source message's body. In case you like more complicated reformatting, you may also create a body yourself first, and pass this on to this "reply" method. Some of the other options to this method will be ignored in this case.

group_reply => BOOLEAN

Will the people listed in the "Cc" headers (those who received the message where you reply to now) also receive this message as carbon copy?

include => 'NO'|'INLINE'|'ATTACH'

Must the message where this is a reply to be included in the message? If "NO" then not. With "INLINE" a reply body is composed. "ATTACH" will create a multi-part body, where the original message is added after the specified body. It is only possible to inline textual messages, therefore binary or multipart messages will always be enclosed as attachment.

max_signature => INTEGER

Passed to "stripSignature" on the body as parameter "max_lines". Only effective for single-part messages.

message_type => CLASS

Create a message with the requested type. By default, it will be a Mail::Message. This is correct, because it will be coerced into the correct folder message type when it is added to that folder.

postlude => BODY|LINES

The line(s) which to be added after the quoted reply lines. Create a body for it first. This should not include the signature, which has its own option. The signature will be added after the postlude when the reply is INLINEd.

prelude => BODY|LINES

The line(s) which will be added before the quoted reply lines. If nothing is specified, the result of the replyPrelude() method is taken. When "undef" is specified, no prelude will be added.

quote => CODE|STRING

Mangle the lines of an "INLINE"d reply with CODE, or by prepending a STRING to each line. The routine specified by CODE is called when the line is in $_.

By default, '> ' is added before each line. Specify "undef" to disable quoting. This option is processed after the body has been decoded.

signature => BODY|MESSAGE

The signature to be added in case of a multi-part reply. The mime-type of the signature body should indicate this is a used as such. However, in INLINE mode, the body will be taken, a line containing '-- ' added before it, and added behind the epilogue.

strip_signature => REGEXP|STRING|CODE

Remove the signature of the sender. The value of this parameter is passed to Mail::Message::Body::stripSignature(pattern) unless the source text is not included. The signature is stripped from the message before quoting.

When a multipart body is encountered, and the message is included to ATTACH, the parts which look like signatures will be removed. If only one message remains, it will be the added as single attachment, otherwise a nested multipart will be the result. The value of this option does not matter, as long as it is present. See Mail::Message::Body::Multipart.

example:

my $reply = $msg->reply
 ( prelude         => "No spam, please!\n\n"
 , postlude        => "\nGreetings\n"
 , strip_signature => 1
 , signature       => $my_pgp_key
 , group_reply     => 1
 , 'X-Extra'       => 'additional header'
 );