--Boundary-02=_PELm9VKqXi4eoPi
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-Description: signed data
Content-Disposition: inline

On Monday 30 September 2002 11:08, Gene Heskett wrote:
<snip>
> I've got a Q here.  Since uuencode/uudecode is the inferior method,
> base64 having been the choice because of its increased robustness
> when the MIME specs were standardized, of what utility is support
> of an obsolete transport method?

The golden rule of the internet: "Be liberal in what you accept, be=20
conservative in what you create." There's no way to send an attachment=20
uuencoded with KMail except when using some kind of forwarding. We just=20
decode it. And even that only when it's in proper MIME format, not when=20
inlined, though that should be easy to do now and probably should be=20
done.

Marc

=2D-=20
If this were a dictatorship, it'd be a heck of a lot easier...just as
long as I'm the dictator...
=2D- George W. Bush, Washington, DC, Dec 18, 2000,
   during his first trip to Washington as President-Elect

--Boundary-02=_PELm9VKqXi4eoPi
Content-Type: application/pgp-signature
Content-Description: signature

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

iD8DBQA9mLEP3oWD+L2/6DgRAuMXAKDVTu2q0hgMLlEEmwH3TolF8S/mYgCfTQW6
C6bnK0YA57/o07tb5XCfegg=
=AdxY
-----END PGP SIGNATURE-----

--Boundary-02=_PELm9VKqXi4eoPi--

_______________________________________________
KMail Developers mailing list
kmail@mail.kde.org
http://mail.kde.org/mailman/listinfo/kmail