[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
3.5.1 Summary Mail Commands | Sending mail. | |
3.5.2 Summary Post Commands | Sending news. | |
3.5.3 Summary Message Commands | Other Message-related commands. | |
3.5.4 Canceling Articles |
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Commands for composing a mail message:
Mail a reply to the author of the current article
(gnus-summary-reply
).
Mail a reply to the author of the current article and include the
original message (gnus-summary-reply-with-original
). This
command uses the process/prefix convention.
Mail a wide reply to the author of the current article
(gnus-summary-wide-reply
). A wide reply is a reply that
goes out to all people listed in the To
, From
(or
Reply-to
) and Cc
headers. If Mail-Followup-To
is
present, that’s used instead.
Mail a wide reply to the current article and include the original
message (gnus-summary-wide-reply-with-original
). This command uses
the process/prefix convention, but only uses the headers from the
first article to determine the recipients.
When replying to a message from a mailing list, send a reply to that
message to the mailing list, and include the original message
(gnus-summary-reply-to-list-with-original
).
Mail a very wide reply to the author of the current article
(gnus-summary-wide-reply
). A very wide reply is a reply
that goes out to all people listed in the To
, From
(or
Reply-to
) and Cc
headers in all the process/prefixed
articles. This command uses the process/prefix convention.
Mail a very wide reply to the author of the current article and include the
original message (gnus-summary-very-wide-reply-with-original
). This
command uses the process/prefix convention.
Mail a reply to the author of the current article but ignore the
Reply-To
field (gnus-summary-reply-broken-reply-to
).
If you need this because a mailing list incorrectly sets a
Reply-To
header pointing to the list, you probably want to set
the broken-reply-to
group parameter instead, so things will work
correctly. See section Group Parameters.
Mail a reply to the author of the current article and include the
original message but ignore the Reply-To
field
(gnus-summary-reply-broken-reply-to-with-original
).
Forward the current article to some other person
(gnus-summary-mail-forward
). If no prefix is given, the message
is forwarded according to the value of (message-forward-as-mime
)
and (message-forward-show-mml
); if the prefix is 1, decode the
message and forward directly inline; if the prefix is 2, forward message
as an rfc822 MIME section; if the prefix is 3, decode message and
forward as an rfc822 MIME section; if the prefix is 4, forward message
directly inline; otherwise, the message is forwarded as no prefix given
but use the flipped value of (message-forward-as-mime
). By
default, the message is decoded and forwarded as an rfc822 MIME
section.
Prepare a mail (gnus-summary-mail-other-window
). By default, use
the posting style of the current group. If given a prefix, disable that.
If the prefix is 1, prompt for a group name to find the posting style.
Prepare a news (gnus-summary-news-other-window
). By default,
post to the current group. If given a prefix, disable that. If the
prefix is 1, prompt for a group to post to.
This function actually prepares a news even when using mail groups. This is useful for “posting” messages to mail groups without actually sending them over the network: they’re just saved directly to the group in question. The corresponding back end must have a request-post method for this to work though.
If you have sent a mail, but the mail was bounced back to you for some
reason (wrong address, transient failure), you can use this command to
resend that bounced mail (gnus-summary-resend-bounced-mail
). You
will be popped into a mail buffer where you can edit the headers before
sending the mail off again. If you give a prefix to this command, and
the bounced mail is a reply to some other mail, Gnus will try to fetch
that mail and display it for easy perusal of its headers. This might
very well fail, though.
Not to be confused with the previous command,
gnus-summary-resend-message
will prompt you for an address to
send the current message off to, and then send it to that place. The
headers of the message won’t be altered—but lots of headers that say
Resent-To
, Resent-From
and so on will be added. This
means that you actually send a mail to someone that has a To
header that (probably) points to yourself. This will confuse people.
So, natcherly you’ll only do that if you’re really eVIl.
This command is mainly used if you have several accounts and want to
ship a mail to a different account of yours. (If you’re both
root
and postmaster
and get a mail for postmaster
to the root
account, you may want to resend it to
postmaster
. Ordnung muss sein!
This command understands the process/prefix convention (see section Process/Prefix).
Like the previous command, but will allow you to edit the message as if it were a new message before resending.
Digest the current series (see section Decoding Articles) and forward the
result using mail (gnus-uu-digest-mail-forward
). This command
uses the process/prefix convention (see section Process/Prefix).
Send a complaint about excessive crossposting to the author of the
current article (gnus-summary-mail-crosspost-complaint
).
This command is provided as a way to fight back against the current
crossposting pandemic that’s sweeping Usenet. It will compose a reply
using the gnus-crosspost-complaint
variable as a preamble. This
command understands the process/prefix convention
(see section Process/Prefix) and will prompt you before sending each mail.
Also See (message)Header Commands section ‘Header Commands’ in The Message Manual, for more information.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Commands for posting a news article:
Prepare for posting an article (gnus-summary-post-news
). By
default, post to the current group. If given a prefix, disable that.
If the prefix is 1, prompt for another group instead.
Post a followup to the current article (gnus-summary-followup
).
Post a followup to the current article and include the original message
(gnus-summary-followup-with-original
). This command uses the
process/prefix convention.
Post a followup to the current article via news, even if you got the
message through mail (gnus-summary-followup-to-mail
).
Post a followup to the current article via news, even if you got the
message through mail and include the original message
(gnus-summary-followup-to-mail-with-original
). This command uses
the process/prefix convention.
Forward the current article to a newsgroup
(gnus-summary-post-forward
).
If no prefix is given, the message is forwarded according to the value
of (message-forward-as-mime
) and
(message-forward-show-mml
); if the prefix is 1, decode the
message and forward directly inline; if the prefix is 2, forward message
as an rfc822 MIME section; if the prefix is 3, decode message and
forward as an rfc822 MIME section; if the prefix is 4, forward message
directly inline; otherwise, the message is forwarded as no prefix given
but use the flipped value of (message-forward-as-mime
). By
default, the message is decoded and forwarded as an rfc822 MIME section.
Digest the current series and forward the result to a newsgroup
(gnus-uu-digest-post-forward
). This command uses the
process/prefix convention.
Uuencode a file, split it into parts, and post it as a series
(gnus-uu-post-news
). (see section Uuencoding and Posting).
Also See (message)Header Commands section ‘Header Commands’ in The Message Manual, for more information.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Yank the current article into an already existing Message composition
buffer (gnus-summary-yank-message
). This command prompts for
what message buffer you want to yank into, and understands the
process/prefix convention (see section Process/Prefix).
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Have you ever written something, and then decided that you really, really, really wish you hadn’t posted that?
Well, you can’t cancel mail, but you can cancel posts.
Find the article you wish to cancel (you can only cancel your own
articles, so don’t try any funny stuff). Then press C or S
c (gnus-summary-cancel-article
). Your article will be
canceled—machines all over the world will be deleting your article.
This command uses the process/prefix convention (see section Process/Prefix).
Be aware, however, that not all sites honor cancels, so your article may live on here and there, while most sites will delete the article in question.
Gnus will use the “current” select method when canceling. If you want to use the standard posting method, use the ‘a’ symbolic prefix (see section Symbolic Prefixes).
Gnus ensures that only you can cancel your own messages using a
Cancel-Lock
header (see Canceling News: (message)Canceling News section ‘Canceling News’ in Message Manual).
If you discover that you have made some mistakes and want to do some corrections, you can post a superseding article that will replace your original article.
Go to the original article and press S s
(gnus-summary-supersede-article
). You will be put in a buffer
where you can edit the article all you want before sending it off the
usual way.
The same goes for superseding as for canceling, only more so: Some sites do not honor superseding. On those sites, it will appear that you have posted almost the same article twice.
If you have just posted the article, and change your mind right away,
there is a trick you can use to cancel/supersede the article without
waiting for the article to appear on your site first. You simply return
to the post buffer (which is called ‘*sent ...*’). There you will
find the article you just posted, with all the headers intact. Change
the Message-ID
header to a Cancel
or Supersedes
header by substituting one of those words for the word
Message-ID
. Then just press C-c C-c to send the article as
you would do normally. The previous article will be
canceled/superseded.
Just remember, kids: There is no ’c’ in ’supersede’.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] |
This document was generated on January 25, 2015 using texi2html 1.82.