Re: Rmail-mbox branch

[Evil Boris]

Eli Zaretskii <address@hidden> writes:

>> From: Evil Boris <address@hidden>
>> Date: Sun, 31 Aug 2008 15:15:04 -0400
>> 
>> [...] there was no support for dealing with attachments (and I somehow also
>> assumed that dealing with non-US character sets and/or UNICODE, but I
>> may be confused). [...]
>
> ?? The current Rmail, the one which uses Babyl, doesn't support
> attachments either.  Or am I misunderstanding what you mean by
> ``support for dealing with attachments''?

Now that I sent the msg, I am a bit confused by what I wrote myself. :-)

I am aware that rmail by itself does not deal with attachments (but
apparently forgot about it while writing the above).  I most recently
have been using etach, though I am not completely happy with it.  I have
tried other things in the past (rmime? rmail-mime?), but I do not recall
now.  [I also recall having to save msgs to a file and manually run them
through "metamail -w", which I still do in desperate situations.]

I guess in absense of such support (and hoping etach or equivalent will
magically support mbox format :-), my main concern would be handling of
different character sets (Unicode, ISO-8859-x, KOI8-R, are most popular)
in plain text msgs, so that I can see the text without jumping through
hoops.

--Boris

PS. Reading a multipart/alternative email with a text/plain component
encoded in quoted-printable [in a non-latin-based character set] or
base64 is currently a pain, as I have to detach and then play around
with decoding the character set in the raw RMAIL file...  but this is a
separate story...