Mail client having trouble with email format.
Alexander Skwar
listen at alexander.skwar.name
Wed Aug 9 08:34:23 UTC 2006
Erik Christiansen <erik at dd.nec.com.au>:
> On Wed, Aug 09, 2006 at 07:51:33AM +0200, Alexander Skwar wrote:
>> ยท Erik Christiansen <erik at dd.nec.com.au>:
>> > Alexander,> > Apropos "was ich nicht kann", just your posts have in the last month or> so, started to fail to line-wrap here. My procmail & mutt configurations> have handled tens of thousands of posts OK, but in case it was my> automatic long-line wrapping in procmail, your posts now pass directly> to my inbox, without any processing. They still look lke they've been> through a sausage machine. :-)> > Trying "od -c" on the message, I see that the newlines preceding "> >"> are missing on receipt:> > 0007440 c o m > : \n > O n 8 / 7 / 0[...]> Is there any chance that the newline-eating gremlin is at your end?
>> Hm, "recently", I've switched to reading this list overGmane with the news client KNode. When I subscribed to thelist, I originally used mails and Thunderbird.
>> > P.S. At least your sig-quotes are still readable, so all is not lost. ;-)
>> Hm. Even more strange.
>
> It looks like I confused the issue there. They're only clear because
> they're at the end of the solid block of text resulting from the missing
> newlines. (I was merely expressing appreciation of the sometimes
> thought-provoking, and sometimes amusing quotes. Oh, and sometimes they
> stretch my atrophied linguistic muscle to the limit.)
>
> In the text quoted from your post, above, line 2 is a 654 character
> monster, running from "> > Alexander" to "is at your end?" The "> >" line
> quotation markers within are lacking the requisite preceding newline.
Strange.
But that's actually not my finding. When I have a look at my *MAILS*
I receive from the list with Thunderbird, all looks fine. Also, I
manually decoded the base64 from the message, to which you initially
responded in this subthread and where you changed the subject. Running
"od -c" on the text, I get:
0000000 302 267 G r e g o r y P i 303 261 e
0000020 r o < g r e g p i n e r o @ g
0000040 m a i l . c o m > : \n \n > O n
As you see, there are \n in there.
Reg. the message with the "654 char monster":
0000140 y o u r p o s t s h a v e
0000160 i n t h e l a s t m o n
0000200 t h o r \n > s o , s t a r
See in the 3rd line? There's "r \n >".
>> Hmm...
>> I noticed, that some of my messages are utf-8 encoded and base64transfer encoded.
>> Why is it base64? Strange. In other newsgroups, I also use utf-8,but in those newsgroups, my messages are 8bit encoded - that's whatI'd expect. Thus, it's not me who base64 encodes the messages.
>
> This is how it arrives:
>
> Content-Type: text/plain; charset="utf-8"
> Content-Transfer-Encoding: 8bit
> X-MIME-Autoconverted: from base64 to 8bit by <our_mailhost_id_goes_here>
>
> But base64 conversions shouldn't drop characters, I would have thought?
True, and from what I see, it doesn't.
> If you examine one of your posts with quoted text, at the character
> level, is each set of line quotation markers preceded by a newline?
Yes.
Because of my findings and because other people (like Peter) don't
see this issue, I'd expect that there's something faulty at your
end.
Alexander Skwar
--
So what is the best way to protect yourself against the ILOVEYOU virus? Install
Linux. If that's not an option, try uninstalling Windows.
-- Geoff Johnson
More information about the ubuntu-users
mailing list