Message body cleanup requested

Charles Curley pluglist at plug.org
Tue Apr 29 16:29:20 MDT 2003


--/04w6evG8XlLl3ft
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Apr 29, 2003 at 01:36:18PM -0600, Sasha Pachev wrote:
> Guys,
>=20
> I subscribe to the digest and it posts every message body pretty much "as=
=20
> is". That means if your plain text is not very plain, it looks very ugly =
and=20
> hard to read. Some people's mail clients produce "poorly digestable"=20
> messages, including things like HTML, =3D20 line extension codes, and wha=
tever=20
> else the mail client decides is the fashion of the day. Could you please=
=20
> check the body of what you are sending (eg. use "view source" on your own=
=20
> message), and see if it is pleasant to read in that format? If not, could=
 you=20
> reconfigure your mail client to send messages in pure plain text at least=
=20
> when sending to the list?
>=20
> We have mentioned this subject in the past, but I am sure we always have =
new=20
> people, so maybe it is a good time for review. A typical Unix guy conside=
rs=20
> it good manners to send only plain text in the main body of the message, =
and=20
> if plain text is not enough, send the rest as an attachment. If the=20
> attachment would be large (lets say larger than 50K), and the message is=
=20
> going to a list, upload the files to a URL and send the location instead.=
=20
> Yes, and never send your resume in .doc format only when applying for a L=
inux=20
> job :-)

Thank you, Sasha. All good points.

See also: http://www.charlescurley.com/netiquette.html

--=20

Charles Curley                  /"\    ASCII Ribbon Campaign
Looking for fine software       \ /    Respect for open standards
and/or writing?                  X     No HTML/RTF in email
http://www.charlescurley.com    / \    No M$ Word docs in email

Key fingerprint =3D CE5C 6645 A45A 64E4 94C0  809C FFF6 4C48 4ECD DFDB

--/04w6evG8XlLl3ft
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQE+rvzA//ZMSE7N39sRApi2AJ9Fw82YCJQP5JXGzAUpMIoiBD61fACbBkc1
o9nFCMR5EVKQiLQ+nOV6iX8=
=Y//g
-----END PGP SIGNATURE-----

--/04w6evG8XlLl3ft--



More information about the PLUG mailing list