I find it incredibly impolite when people have a choice of doing something
that will work for everybody and still stubbornly choose to do something
that annoys a lot of people. I know that MUTT can send messages with PGP
signatures just appended as text at the end of a text body of a message - I
have a friend that has it do just that.
Your argument about standards doesn't hold. Most software doesn't support
SOME standard. If I start sending HTML mail, people will complain about how
they can't read it, even if they use otherwise excellent software for
reading their mail. (Incidentally, does mutt support HTML mail?)
You should also remember that not everybody has a choice about what software
they use - some people get their mail at work, where they have to use a
specific system because their employer wants/needs them to do that.
Trying to get people to use software different from what they use by
purposly giving them incompatible data usually doesn't do any good. It just
gives you a reputation as being hardheaded and stubborn. Look at what
happened to our own RMS. He didn't get elected to board of directors
(or whatever it was) for Gnome. His years of dedication and hard work have
been erased by his aggressivly disagreeable attitude towards people who
don't agree with him in 100%.
Please don't make this newsgroup into a hostile place. It is possible for
you to send mail as pure text. Please try to do that. It'll make everybody
happy.
Thnx
Michal
----- Original Message -----
From: "Jeroen Dekkers" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, December 07, 2001 10:22 AM
Subject: Re: [plex86] SourceForge Was: bochs 1.3 --> plex86?
I'm sending a MIME message with 2 parts, the first of type text/plain
and the second of type application/pgp-signature. According to RFC 2049
a MIME compliant client must do among other things the following
(quoting from that document):
(6) Explicitly handle the following media type values, to
at least the following extents:
Text:
-- Recognize and display "text" mail with the
character set "US-ASCII."
<snip>
-- Treat material in an unknown character set as if
it were "application/octet-stream".
As my message is just "text", every compliant mail user agent should
show that. It should handle my signature just as
"application/octet-stream" if it doesn't support signatures. As always
with M$ their software ignores every standard, I don't understand why
people are still using crappy non-free software from microsoft. But if
you really insist doing so, complain to microsoft about the bugs in it.
I'm not going to change my habit of signing every message I sent because
of some broken mail user agent.