X-Git-Url: http://cgit.sxemacs.org/?p=gnus;a=blobdiff_plain;f=texi%2Fgnus.texi;h=ed882d2663fa45f4108eb118c7089fe227eb2ebd;hp=6feab478b1676142b670343d7c2a18b34983f63d;hb=4598d7eb56ad42593c8aee7189d3b31e6c476344;hpb=cf1cc15caa87116a3869bbfaea7cd0b02a8250e2 diff --git a/texi/gnus.texi b/texi/gnus.texi index 6feab478b..ed882d266 100644 --- a/texi/gnus.texi +++ b/texi/gnus.texi @@ -2885,7 +2885,7 @@ composed messages will be @code{Gcc}'d to the current group. If generated, if @code{(gcc-self . "string")} is present, this string will be inserted literally as a @code{gcc} header. This parameter takes precedence over any default @code{Gcc} rules as described later -(@pxref{Archived Messages}). +(@pxref{Archived Messages}), with the exception for messages to resend. @strong{Caveat}: Adding @code{(gcc-self . t)} to the parameter list of @code{nntp} groups (or the like) isn't valid. An @code{nntp} server @@ -3028,6 +3028,7 @@ like this in the group parameters: @example (posting-style (name "Funky Name") + ("X-Message-SMTP-Method" "smtp smtp.example.org 587") ("X-My-Header" "Funky Value") (signature "Funky Signature")) @end example @@ -12670,6 +12671,22 @@ and matches the Gcc group name, attach files as external parts; if it is non-@code{nil}, the behavior is the same as @code{all}, but it may be changed in the future. +@item gnus-gcc-self-resent-messages +@vindex gnus-gcc-self-resent-messages +Like the @code{gcc-self} group parameter, applied only for unmodified +messages that @code{gnus-summary-resend-message} (@pxref{Summary Mail +Commands}) resends. Non-@code{nil} value of this variable takes +precedence over any existing @code{Gcc} header. + +If this is @code{none}, no @code{Gcc} copy will be made. If this is +@code{t}, messages resent will be @code{Gcc} copied to the current +group. If this is a string, it specifies a group to which resent +messages will be @code{Gcc} copied. If this is @code{nil}, @code{Gcc} +will be done according to existing @code{Gcc} header(s), if any. If +this is @code{no-gcc-self}, that is the default, resent messages will be +@code{Gcc} copied to groups that existing @code{Gcc} header specifies, +except for the current group. + @end table @@ -12801,6 +12818,7 @@ So here's a new example: (signature-file "~/.work-signature") (address "user@@bar.foo") (body "You are fired.\n\nSincerely, your boss.") + ("X-Message-SMTP-Method" "smtp smtp.example.org 587") (organization "Important Work, Inc")) ("nnml:.*" (From (with-current-buffer gnus-article-buffer @@ -12815,6 +12833,13 @@ if you fill many roles. You may also use @code{message-alternative-emails} instead. @xref{Message Headers, ,Message Headers, message, Message Manual}. +Of particular interest in the ``work-mail'' style is the +@samp{X-Message-SMTP-Method} header. It specifies how to send the +outgoing email. You may want to sent certain emails through certain +@acronym{SMTP} servers due to company policies, for instance. +@xref{Mail Variables, ,Message Variables, message, Message Manual}. + + @node Drafts @section Drafts @cindex drafts @@ -14228,8 +14253,9 @@ if the server supports UID EXPUNGE, but it's not done by default on servers that doesn't support that command. @item nnimap-streaming -Virtually all @code{IMAP} server support fast streaming of data. If -you have problems connecting to the server, try setting this to @code{nil}. +Virtually all @acronym{IMAP} server support fast streaming of data. +If you have problems connecting to the server, try setting this to +@code{nil}. @item nnimap-fetch-partial-articles If non-@code{nil}, fetch partial articles from the server. If set to @@ -14237,6 +14263,10 @@ a string, then it's interpreted as a regexp, and parts that have matching types will be fetched. For instance, @samp{"text/"} will fetch all textual parts, while leaving the rest on the server. +@item nnimap-record-commands +If non-@code{nil}, record all @acronym{IMAP} commands in the +@samp{"*imap log*"} buffer. + @end table @@ -14752,6 +14782,18 @@ corresponding keywords. A script to be run before fetching the mail. The syntax is the same as the @code{:program} keyword. This can also be a function to be run. +One popular way to use this is to set up an SSH tunnel to access the +@acronym{POP} server. Here's an example: + +@lisp +(pop :server "127.0.0.1" + :port 1234 + :user "foo" + :password "secret" + :prescript + "nohup ssh -f -L 1234:pop.server:110 remote.host sleep 3600 &") +@end lisp + @item :postscript A script to be run after fetching the mail. The syntax is the same as the @code{:program} keyword. This can also be a function to be run.