From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <raorn@immo.ru>
Date: Fri, 19 May 2006 10:17:15 +0400
From: "Alexey I. Froloff" <raorn@immo.ru>
To: ALT Linux Community <community@lists.altlinux.org>
Message-ID: <20060519061715.GO2173@immo.ru>
References: <20060512163600.26638176@shadow.orionagro.com.ua>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="ugCSa1rMkiCAmd9S"
Content-Disposition: inline
In-Reply-To: <20060512163600.26638176@shadow.orionagro.com.ua>
User-Agent: Mutt/1.5.11
X-Virus-Scanned: amavisd-new at immo.ru
Subject: Re: [Comm] =?koi8-r?b?SSDp2s3FzsXOycUgyc3FziDGwcrMz9cg7c/ayczPyi4=?=
X-BeenThere: community@lists.altlinux.org
X-Mailman-Version: 2.1.7
Precedence: list
Reply-To: ALT Linux Community <community@lists.altlinux.org>
List-Id: ALT Linux Community <community.lists.altlinux.org>
List-Unsubscribe: <https://lists.altlinux.org/mailman/listinfo/community>,
	<mailto:community-request@lists.altlinux.org?subject=unsubscribe>
List-Archive: <http://lists.altlinux.org/pipermail/community>
List-Post: <mailto:community@lists.altlinux.org>
List-Help: <mailto:community-request@lists.altlinux.org?subject=help>
List-Subscribe: <https://lists.altlinux.org/mailman/listinfo/community>,
	<mailto:community-request@lists.altlinux.org?subject=subscribe>
X-List-Received-Date: Fri, 19 May 2006 06:17:15 -0000
Archived-At: <http://lore.altlinux.org/community/20060519061715.GO2173@immo.ru/>
List-Archive: <http://lore.altlinux.org/community/>
List-Post: <mailto:mandrake-russian@linuxteam.iplabs.ru>


--ugCSa1rMkiCAmd9S
Content-Type: text/plain; charset=koi8-r
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

* 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 _=EE=E9=EB=EF=E7=E4=E1_ =CE=C5 =C2=D9=CC =D3=D4=C1=CE=C4=C1=D2=D4=
=CF=CD =CB=CF=C4=C9=D2=CF=D7=C1=CE=C9=D1 attachment
filename.

> =F0=D2=C5=C4=CC=C1=C7=C1=C0 =DC=D4=D5 =CE=C1=D3=D4=D2=CF=CA=CB=D5 =D3=C4=
=C5=CC=C1=D4=D8 =D0=CF =D5=CD=CF=CC=DE=C1=CE=C9=C0 =D7 =D3=C2=CF=D2=CB=C5...
> =E9=CE=C1=DE=C5, =CD=CF=D6=CE=CF =CF=C7=D2=C5=D3=D4=C9 =D0=CF =DA=C1=C7=
=D2=C9=D7=CB=D5 =D4=C1=CB =D6=C5, =CB=C1=CB =D1 =D3=C5=C7=CF=C4=CE=D1 :)
=EE=C5=D4 =D5=D6, =CE=C1=C6=C9=C7 =D4=C1=CB=CF=C5 =D3=DE=C1=D3=D4=D8=C5...


=EB=D3=D4=C1=D4=C9:

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:
   =3D?iso-8859-1?Q?file=3D5F=3DE4=3D5F991116=3D2Ezip?=3D

   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.

--=20
Regards, Alexey I. Froloff
AIF5-RIPN, AIF5-RIPE
-------------------------------------------
  Inform-Mobil, Ltd. System Administrator
       http://www.inform-mobil.ru/

--ugCSa1rMkiCAmd9S
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)

iD8DBQFEbWLrVqT7+fkT8woRAlbSAJ9kI9VJJkRMHTLOOnmLXOlWWW0eEACfeVIK
Wm/+c7iZoX1uJLMtQ15kdHI=
=8HyO
-----END PGP SIGNATURE-----

--ugCSa1rMkiCAmd9S--