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 <-----/	=09


(I suck at ASCII art, so bear mith me :-)

Incidentally, downloading that message with Evolution doesn't change
those headers, and that's how we found the bug in our app.

Thanks a lot.

On Sat, 2002-09-14 at 06:20, Ingo Kl=F6cker wrote:
    -----BEGIN PGP SIGNED MESSAGE-----
    Hash: SHA1
   =20
    On Friday 13 September 2002 23:30, Ruben Marrero wrote:
    > Now, I have two questions, first one: Is this true?, does kmail "fix"
    > messages to follow proper MIME? and if this is so, should it be doing
    > it?
   =20
    KMail doesn't alter messages in any way except by adding some custom=20
    headers. So the answer to all your questions is 'no'.
   =20
    I guess some MTA fixed the broken messages before KMail received it. Yo=
u=20
    can try this by fetching a sample message with fetchmail.
   =20
    Regards,
    Ingo
   =20
    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v1.0.7 (GNU/Linux)
   =20
    iD8DBQE9gxuZGnR+RTDgudgRAoHVAJ4xKD4+7BLuOQ6Uwmabr/xgbEG41wCcCO+1
    aeubcDoFXhnpF280S7sZQcI=3D
    =3DWpAq
    -----END PGP SIGNATURE-----
   =20
   =20
    _______________________________________________
    KMail Developers mailing list
    kmail@mail.kde.org
    http://mail.kde.org/mailman/listinfo/kmail
   =20
   =20
   =20

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