It's Outlook Express, but don't feel too bad because it is not the only
reader that does it. If you look, you will notice that the line that kills
is "begin 644 file". Some readers decode the patch which follows, but don't
continue with the message after the end. They just truncate. You can mail
yourself a test message to confirm. Just begin the line as I state above.
In a perfect world, the readers would be fixed because I don't believe the
begin line is enough to warrent decoding [isn't a MIME header of sorts
required??? Anyone more knowledgeable about these things care to add?]
Seeing how this isn't a perfect world, maybe the list maintainer could add a
'>' before the "begin" when processing for the digest? I know I have asked
before, but it is rather annoying and worth asking for again. <g> My
.forward file sends duplicates to another machine which I read with pine
ONLY when I get a truncated digest. This also works for me, but is also
rather annoying.
Another fix would be for people to not send patches to the list in that
format... Yeah, that will happen... :-)
-Eric ;-)
--
Eric Princen
Micro Analysis & Design
http://www.maad.com/~eprincen
"I don't want to achieve immortality through my work.
I want to achieve it by not dying."
--Woody Allen
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu