Re: replying to text/plain base64

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

> Which doesn't get the '> ' inserted correctly by itself.. :(

I can get the '> ' by selecting text in the exmh message view
then using 'More...' -> 'Cite Selection' in the sedit window.

> Robert Elz was correct, the heavy lifting for this should
> probably be in the replcomps processing.

OK.  I thought it might be in the nmh arena.  I've attached my
current replcomps file.  I don't know how to get base64 text
decoded using replcomps.  Does anyone on this list?  If not, I
suppose I'll head over to comp.mail.mh.

> And *really* correct replcomps handling would allow citing only
> the 5 lines of text/plain in a multipart/mixed without blatting
> in base64 of the attached .jpg. :)

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.

Thanks....


--
Kevin

_______________________________________________
Exmh-users mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/exmh-users
replcomps (text/plain, 725 B)
%(lit)%(formataddr %<{reply-to}%|%<{from}%|%<{sender}%|%{return-path}%>%>%>)\
%<(nonnull)%(void(width))%(putaddr To: )\n%>\
%(lit)%(formataddr{to})%(formataddr{cc})%(formataddr(me))\
%<(nonnull)%(void(width))%(putaddr cc: )\n%>\
%<{fcc}Fcc: %{fcc}\n%>\
X-Message-Flag: Failure is not an option. It comes bundled with your Microsoft product.
X-Request-PGP: http://pgp.mit.edu:11371/pks/lookup?search=0xD165C0CC&op=index
X-PGP-KeyID: 0xD165C0CC
%<{subject}Subject: Re: %{subject}\n%>\
%<{message-id}In-reply-to: %{message-id}\n%>\
--------\n\

On %<(nodate{date})%{date}%|%(mday{date}) %(lmonth{date}) %(year{date}) \
at %(hour{date}):%02(min{date})%>, \
%<{from}%{from}%?{apparently-from}%{apparently-from}%|%{sender}%>wrote:
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.