force rfc2047_parameters to be set to yes, and non configureable.

[apps/madmutt.git] / init.h

diff --git a/init.h b/init.h
index 9895751..841ae38 100644 (file)
--- a/init.h
+++ b/init.h
@@ -2971,26 +2971,6 @@ struct option_t MuttVars[] = {
    ** possibly including eventual real names.  When it is \fIunset\fP, Madmutt will
    ** override any such real names with the setting of the $realname variable.
    */
    ** possibly including eventual real names.  When it is \fIunset\fP, Madmutt will
    ** override any such real names with the setting of the $realname variable.
    */

-  {"rfc2047_parameters", DT_BOOL, R_NONE, OPTRFC2047PARAMS, "no" },
-  /*
-   ** .pp
-   ** When this variable is \fIset\fP, Madmutt will decode RFC-2047-encoded MIME 
-   ** parameters. You want to set this variable when Madmutt suggests you
-   ** to save attachments to files named like this:
-   ** .pp
-   **  \fT=?iso-8859-1?Q?file=5F=E4=5F991116=2Ezip?=\fP
-   ** .pp
-   ** When this variable is \fIset\fP interactively, the change doesn't have
-   ** the desired effect before you have changed folders.
-   ** .pp
-   ** Note that this use of RFC 2047's encoding is explicitly,
-   ** prohibited by the standard, but nevertheless encountered in the
-   ** wild.
-   ** .pp
-   ** Also note that setting this parameter will \fInot\fP have the effect 
-   ** that Madmutt \fIgenerates\fP this kind of encoding.  Instead, Madmutt will
-   ** unconditionally use the encoding specified in RFC 2231.
-   */

   {"save_address", DT_BOOL, R_NONE, OPTSAVEADDRESS, "no" },
   /*
    ** .pp
   {"save_address", DT_BOOL, R_NONE, OPTSAVEADDRESS, "no" },
   /*
    ** .pp


@@ -3687,7 +3667,8 @@ struct option_t MuttVars[] = {
    */
 #endif
   /*--*/
    */
 #endif
   /*--*/

-  {"strict_mime", DT_BOOL, R_NONE, OPTSTRICTMIME, "yes" },
+  {"strict_mime", DT_BOOL, R_NONE, OPTSTRICTMIME, "no" },
+  {"rfc2047_parameters", DT_BOOL, R_NONE, OPTRFC2047PARAMS, "yes"},

   { NULL, -1, R_NONE, -1, NULL }
 };
 
   { NULL, -1, R_NONE, -1, NULL }
 };