From: Oscar Figueiredo <Oscar.Figueiredo@di.epfl.ch>
Subject: Problems with inline multipart rfc822 messages
Date: 21 Apr 1999 10:24:15 +0200 [thread overview]
Message-ID: <o97wvz6wfdc.fsf@lspsun17.epfl.ch> (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
next reply other threads:[~1999-04-21 8:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-21 8:24 Oscar Figueiredo [this message]
1999-04-21 9:18 ` Kai.Grossjohann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=o97wvz6wfdc.fsf@lspsun17.epfl.ch \
--to=oscar.figueiredo@di.epfl.ch \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).