RMAIL, MIME-related bug

RMAIL, MIME-related bug

[Alexander Pohoyda]

If the rmail-enable-mime variable is non-nil, replying to the message
with hidden header fields will produce an empty References header
field. This does not happen if you reply to the message with header
fields toggled on.
The problem is obvious in rmail-reply function.

Also, it seems to me that the MIME support in RMAIL is far from
finished. Is there any work in progress?

-- 
Alexander Pohoyda <alexander.pohoyda@gmx.net>
PGP Key fingerprint: 7F C9 CC 5A 75 CD 89 72  15 54 5F 62 20 23 C6 44

Re: RMAIL, MIME-related bug

[Eli Zaretskii]

> Date: Tue, 7 Oct 2003 21:29:03 +0200 (CEST)
> From: Alexander Pohoyda <alexander.pohoyda@gmx.net>
> 
> Also, it seems to me that the MIME support in RMAIL is far from
> finished. Is there any work in progress?

Didn't you yourself said that you were working on that?

Re: RMAIL, MIME-related bug

[Alexander Pohoyda]

> > Also, it seems to me that the MIME support in RMAIL is far from
> > finished. Is there any work in progress?
> 
> Didn't you yourself said that you were working on that?

Yes, last weekend I have completed a small but extensible library
which is plugable into RMail. It is able to parse a MIME message of
any complexity and show it in the RMail buffer. I want, however, to
finish some open points before I submit it here.
BTW, it also does header decoding (RFC 2047).

I have found a variable called rmail-enable-mime, and some void
variables of type rmail-*-mime-* which don't fit into my
implementation and I don't understand why they are here anyway.


Open points are:

1) I want to have a single mechanism to hide header
   fields. Independent whether they come from the top-level entity
   (currently implemented by deleting/copying them) or any other
   entity.

2) If I save an email to the file, I want it to be the same message
   as RMail read from my mailbox. I want to be able to read it from
   another mail client, for example.

3) I agree that some action (transfer-/charset decoding, PGP signature
   verification, etc.) is OK to do once in function called from
   rmail-convert-to-babyl-format, but some other (picture previews,
   big attachement hiding, etc.) should be done by every (?)
   rmail-show-message call.

I would like to hear some comments.


-- 
Alexander Pohoyda <alexander.pohoyda@gmx.net>
PGP Key fingerprint: 7F C9 CC 5A 75 CD 89 72  15 54 5F 62 20 23 C6 44

Re: RMAIL, MIME-related bug

[Alexander Pohoyda]

I just found out that if rmail-enable-mime is set, you cannot save a
message to file.

Is there anybody who uses current MIME-support in Rmail?


-- 
Alexander Pohoyda <alexander.pohoyda@gmx.net>
PGP Key fingerprint: 7F C9 CC 5A 75 CD 89 72  15 54 5F 62 20 23 C6 44

Re: RMAIL, MIME-related bug

[Eli Zaretskii]

> Date: Wed, 8 Oct 2003 00:14:38 +0200 (CEST)
> From: Alexander Pohoyda <alexander.pohoyda@gmx.net>
> 
> I have found a variable called rmail-enable-mime, and some void
> variables of type rmail-*-mime-* which don't fit into my
> implementation and I don't understand why they are here anyway.

IIRC, this is for add-on packages that add MIME support to RMAIL.

> 2) If I save an email to the file, I want it to be the same message
>    as RMail read from my mailbox. I want to be able to read it from
>    another mail client, for example.

Someone wrote code to do that, but it's currently on a separate
branch of the Emacs CVS.  I suggest to leave this issue alone, not to
mix it with the other changes you did.

> 3) I agree that some action (transfer-/charset decoding, PGP signature
>    verification, etc.) is OK to do once in function called from
>    rmail-convert-to-babyl-format, but some other (picture previews,
>    big attachement hiding, etc.) should be done by every (?)
>    rmail-show-message call.

I suggest to discuss this (on emacs-devel).  There are trade-offs here
that IMHO are not so trivial to resolve.

Re: RMAIL, MIME-related bug

[Eli Zaretskii]

> Date: Wed, 8 Oct 2003 00:40:34 +0200 (CEST)
> From: Alexander Pohoyda <alexander.pohoyda@gmx.net>
> 
> I just found out that if rmail-enable-mime is set, you cannot save a
> message to file.

That variable is not supposed to be set by humans.  See my other mail
for more info.