Re: problem with received attachments (possible MIME issue)

[Seb]

On Thu, 19 Mar 2009 16:22:32 -0500,
Seb <spluque@gmail.com> wrote:

> Hi, For a few weeks now, some messages I receive do not display
> properly, showing garbage like:

> RydkYXkgU2ViLA0KDQpZb3UgbmV2ZXIgY2FsbGVkLiAgRHJvcCBtZSBhbiBlbWFpbCB3aGVuIHlv
> dSB3YW50IHRvIFNreXBlIC0gSSBuZWVkIHRvIHR1bnIgaXQgb24gYXMgSSBjYW4ndCBrZWVwIGl0
> aW4gdGhlIGJhY2tncm91bmQgYXMgaXQgc3R1ZmZzIHVwIG15IGNvbm5lY3QgdG8gdGhlIHVuaSB2
> cG4uDQoNCkNoZWVycywNCkpvaG4NCg0KRHIgSi5QLlkuIEFybm91bGQNClNlbmlvciBMZWN0dXJl

> Others contain attachments that cannot be opened in any viewer, either
> via 't' (`gnus-mime-view-part-as-type' and selecting the appropriate
> type), 'v' (`gnus-mime-view-part' and selecting the viewer), or just
> saving it to a file with 'o' (`gnus-mime-save-part') and then trying
> to view it outside Gnus.  The buttons for these attachments show
> normally.  If I locate the corresponding Incoming* file and import it
> with 'G f [path to Incoming*]', then there are no problems and the
> attachments work perfectly with any method for viewing/saving.

> This occurs with GNU Emacs 23.0.91.1 (x86_64-pc-linux-gnu, GTK+
> Version 2.14.7) of 2009-03-08 on elegiac, modified by Debian, which is
> within a couple of weeks behind CVS Emacs.  Since Gnus is part of this
> Emacs I'm posting this here.  Thanks in advance for any pointers on
> what the problem might be.

Just an update on this, in case this rings a bell for somebody.  Now
with Emacs 23.1.50.1 and Gnus 5.13 from emacs-snapshot Debian sid
package.  This is where I'm at now:

o No problems reading the body of these messages

o Attachments are listed at the end of the message, but they are not
decoded properly by any viewer, and contain only the characters
indicated in my initial message

o To decode them properly, I have to open the mbox file containing it,
save each message along with all the mime parts in it to separate files
and then do "G f" to make doc group for each of them, and reprocess with
"B r" to get the messages back to the nnml backend.

Any tips appreciated.  Thanks


-- 
Seb