summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLars Ingebrigtsen <larsi@gnus.org>2018-04-12 22:04:09 +0200
committerLars Ingebrigtsen <larsi@gnus.org>2018-04-12 22:04:09 +0200
commitc22677bf00e420e7049bd4fca8e0c05772e973c2 (patch)
treee32f12a40a972a320590d624f2426e914d7562f0
parente7c813e912de9c11438cf91b1fde20d75764697e (diff)
downloademacs-c22677bf00e420e7049bd4fca8e0c05772e973c2.tar.gz
Default message-forward-as-mime to nil
* doc/misc/gnus.texi (Summary Mail Commands): Ditto. * doc/misc/message.texi (Forwarding): Note the new default. * lisp/gnus/message.el (message-forward-as-mime): Default to nil since it's been reported that many recipients can't read MIME digest forwards (bug#24878).
-rw-r--r--doc/misc/gnus.texi3
-rw-r--r--doc/misc/message.texi8
-rw-r--r--etc/NEWS4
-rw-r--r--lisp/gnus/message.el4
4 files changed, 11 insertions, 8 deletions
diff --git a/doc/misc/gnus.texi b/doc/misc/gnus.texi
index 6c165424dd2..efda7f20b57 100644
--- a/doc/misc/gnus.texi
+++ b/doc/misc/gnus.texi
@@ -5658,8 +5658,7 @@ as an rfc822 @acronym{MIME} section; if the prefix is 3, decode message and
forward as an rfc822 @acronym{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 (@code{message-forward-as-mime}). By
-default, the message is decoded and forwarded as an rfc822 @acronym{MIME}
-section.
+default, the forwarded message is inlined into the mail.
@item S m
@itemx m
diff --git a/doc/misc/message.texi b/doc/misc/message.texi
index 0a2a6ce49d2..1d27ff1c585 100644
--- a/doc/misc/message.texi
+++ b/doc/misc/message.texi
@@ -345,10 +345,10 @@ constructed. The default value is @code{nil}.
@item message-forward-as-mime
@vindex message-forward-as-mime
-If this variable is @code{t} (the default), forwarded messages are
-included as inline @acronym{MIME} RFC822 parts. If it's @code{nil}, forwarded
-messages will just be copied inline to the new message, like previous,
-non @acronym{MIME}-savvy versions of Gnus would do.
+If this variable is @code{t}, forwarded messages are included as
+inline @acronym{MIME} RFC822 parts. If it's @code{nil} (the default),
+forwarded messages will just be copied inline to the new message, like
+previous, non @acronym{MIME}-savvy versions of Gnus would do.
@item message-forward-before-signature
@vindex message-forward-before-signature
diff --git a/etc/NEWS b/etc/NEWS
index 2847384a3a6..12b72eb25b1 100644
--- a/etc/NEWS
+++ b/etc/NEWS
@@ -374,6 +374,10 @@ achieve this, add 'message-sign-encrypt-if-all-keys-available' to
'"foo@bar.com" <foo@bar.com>', Message will elide the repeated "name"
from the address field in the response.
+*** The default of `message-forward-as-mime' has changed from t to nil
+as it has been reported that many recipients can't read forwards that
+are formatted as MIME digests.
+
* New Modes and Packages in Emacs 27.1
+++
diff --git a/lisp/gnus/message.el b/lisp/gnus/message.el
index 250cdc6b128..f7c3ec04ffc 100644
--- a/lisp/gnus/message.el
+++ b/lisp/gnus/message.el
@@ -548,7 +548,7 @@ The provided functions are:
(function-item message-forward-subject-name-subject)
(repeat :tag "List of functions" function)))
-(defcustom message-forward-as-mime t
+(defcustom message-forward-as-mime nil
"Non-nil means forward messages as an inline/rfc822 MIME section.
Otherwise, directly inline the old message in the forwarded
message.
@@ -556,7 +556,7 @@ message.
When forwarding as MIME, certain MIME-related headers in the
forwarded message may be removed/altered to ensure that the
resulting mail is syntactically valid."
- :version "21.1"
+ :version "27.1"
:group 'message-forwarding
:link '(custom-manual "(message)Forwarding")
:type 'boolean)