From: "Alexey I. Froloff" <raorn@immo.ru> To: ALT Linux Community <community@lists.altlinux.org> Subject: Re: [Comm] I Изменение имен файлов Мозилой. Date: Fri, 19 May 2006 10:17:15 +0400 Message-ID: <20060519061715.GO2173@immo.ru> (raw) In-Reply-To: <20060512163600.26638176@shadow.orionagro.com.ua> [-- Attachment #1: Type: text/plain, Size: 1520 bytes --] * Dmitriy L. Kruglikov <Dmitriy.Kruglikov@> [060512 17:37]: > The problem is caused by "name" and "filename" being replaced by > multiple parameters. This is due to Thunderbird switching from RFC2047 > to RFC2231 (a newer standard) for attachment filename handling. Outlook > supports RFC2047 (the older standard). RFC2047 _НИКОГДА_ не был стандартом кодирования attachment filename. > Предлагаю эту настройку сделать по умолчанию в сборке... > Иначе, можно огрести по загривку так же, как я сегодня :) Нет уж, нафиг такое счастье... Кстати: 7.3.281. rfc2047_parameters Type: boolean Default: no When this variable is set, Mutt will decode RFC-2047-encoded MIME parameters. You want to set this variable when mutt suggests you to save attachments to files named like this: =?iso-8859-1?Q?file=5F=E4=5F991116=2Ezip?= When this variable is set interactively, the change doesn't have the desired effect before you have changed folders. Note that this use of RFC 2047's encoding is explicitly, prohibited by the standard, but nevertheless encountered in the wild. Also note that setting this parameter will not have the effect that mutt generates this kind of encoding. Instead, mutt will unconditionally use the encoding specified in RFC 2231. -- Regards, Alexey I. Froloff AIF5-RIPN, AIF5-RIPE ------------------------------------------- Inform-Mobil, Ltd. System Administrator http://www.inform-mobil.ru/ [-- Attachment #2: Digital signature --] [-- Type: application/pgp-signature, Size: 191 bytes --]
prev parent reply other threads:[~2006-05-19 6:17 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-05-12 13:36 Dmitriy L. Kruglikov 2006-05-13 19:49 ` Vitaly Lipatov 2006-05-15 8:05 ` Dmitriy L. Kruglikov 2006-05-18 13:37 ` Michael Shigorin 2006-05-19 6:17 ` Alexey I. Froloff [this message]
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20060519061715.GO2173@immo.ru \ --to=raorn@immo.ru \ --cc=community@lists.altlinux.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
ALT Linux Community general discussions This inbox may be cloned and mirrored by anyone: git clone --mirror http://lore.altlinux.org/community/0 community/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 community community/ http://lore.altlinux.org/community \ mandrake-russian@linuxteam.iplabs.ru community@lists.altlinux.org community@lists.altlinux.ru community@lists.altlinux.com public-inbox-index community Example config snippet for mirrors. Newsgroup available over NNTP: nntp://lore.altlinux.org/org.altlinux.lists.community AGPL code for this site: git clone https://public-inbox.org/public-inbox.git