=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Monday 16 September 2002 22:35, Ruben Marrero wrote:
> Maybe I'm missing something, but no, the raw message sitting on my
> POP server it's different (on the headers I mentioned of course) from
> the one in the kmail inbox. That message was generated on yet another
> server, so:
>
>
> 	   bad MIME	       bad MIME
> sendmail ------------> qmail ----------------\
>
> 	     SMTP		   POP	     |
>
>
> 	             good MIME 	     	     |
> 	             Inbox <-----Kmail <-----/

O.k., I stand corrected. I didn't knew that KMail fixes MIME messages.=20
The golden rule of RFCs is don't produce broken code but accept broken=20
code. That's why web browsers manage to display most web pages although=20
the code of many web pages is horribly broken. The same way a good mail=20
client should try to interpret even broken MIME code correctly. That=20
seems to be what KMail does. The fact that you didn't notice the broken=20
code your script produced is a small drawback. But the great advantage=20
is that KMail probably often correctly displays messages sent with=20
broken mail clients. Normal users are not interested in knowing that=20
they received broken MIME messages. They are only interested in reading=20
the messages they receive.

So in future you should not use KMail to validate MIME messages and you=20
should not use web browsers to validate HTML code. In the later case=20
use the HTML validator of the w3c and in the former case use a mail=20
client which isn't as tolerant as KMail.

=46or all other use cases you should of course still use KMail. ;-)

Regards,
Ingo

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

iD8DBQE9iOoKGnR+RTDgudgRAioTAJ0TFnz4lxHjb/Zjq3NL9i12jDMwMQCgrYdG
PKPypfM2iUcPLa1PiY36dQA=3D
=3DgbeQ
=2D----END PGP SIGNATURE-----

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