Re: replying to text/plain base64

Kevin Cosgrove <[email protected]>
Newsgroups gmane.mail.exmh.user
Message-ID <[email protected]>
On 17 October 2007 at 1:43, [email protected] wrote:

> On Tue, 16 Oct 2007 21:38:24 PDT, Kevin Cosgrove said:
> > This is a multipart MIME message.
> > 
> > --==_Exmh_10285909160
> > Content-Type: text/plain; charset=us-ascii
> 
> Hmm.. wonder how that got there? ;)
> 
> > But, my base64 is a text message from someone's Blackberry.
> > Both people who send me email from Blackberries come across
> > this way.  There are no pictures in the emails I'm dealing
> > with.
> 
> But your mail *still* triggers the issue - you had an
> attachment, so when I do a 'reply', all the MIME stuff gets
> included.  Yeah, *your* attachment was a dozen lines of
> text/plain.

The email messages I'm trying to reply to, the ones that come
from my friends' Blackberries, are almost always 5-10 lines of
text, and nothing but that, no attachments.  But, those lines of
text are text/plain and base64 encoded.  That's my rub.

> Unfortunately, the attachments I get tend to be 624 page PDF
> files or Microsoft Office documents or similar, and when you do
> a 'reply' to get the "Here's the document" line so you can add
> "thanks, got it" and hit send, you *also* get the base64 mess
> of all 624 pages of PDF.

Bummer dude.  Surely those PDF or Office files aren't text/plain,
only base64, right?

I'm still searching for a recipe to reply to something that's
both text/plain and base64.  My workaround is just to use "Cite 
Selection" from sedit's "More..." menu.

Cheerio....

--
Kevin
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.