* Problems with inline multipart rfc822 messages
@ 1999-04-21 8:24 Oscar Figueiredo
1999-04-21 9:18 ` Kai.Grossjohann
0 siblings, 1 reply; 2+ messages in thread
From: Oscar Figueiredo @ 1999-04-21 8:24 UTC (permalink / raw)
Disclaimer: I've been testing pgnus since 0.81 only so I don't know if this has
been discussed before or is aknown problem.
I often receive MIME messages containing a message/rfc822 part being itself a
multipart MIME message often containing images and such. pgnus 0.83
systematically loses with this type of message: at best an image is properly
decoded and the raw base64 is displayed after in the buffer but most of the
time the message/rfc822 part is not (properly) decoded at all.
I guess this is not supposed to happen. If this is not a known problem, I can
try to give it a closer look or at least try to provide a simple test case
message, just let me know
Oscar
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Problems with inline multipart rfc822 messages
1999-04-21 8:24 Problems with inline multipart rfc822 messages Oscar Figueiredo
@ 1999-04-21 9:18 ` Kai.Grossjohann
0 siblings, 0 replies; 2+ messages in thread
From: Kai.Grossjohann @ 1999-04-21 9:18 UTC (permalink / raw)
pgnus 0.83 is known to have problems with double encoding/decoding of
characters. Maybe this has something to do with it? How about
waiting until Lars fixes the dreaded \201 problem and then testing
again?
It may be a different problem altogether, though.
kai
--
Abort this operation? [Abort] [Cancel]
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~1999-04-21 9:18 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1999-04-21 8:24 Problems with inline multipart rfc822 messages Oscar Figueiredo
1999-04-21 9:18 ` Kai.Grossjohann
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).