GNU bug report logs - #9392
24.0.50; rmail-forward produces messages in unsupported format that cannot be customized away

Previous Next

Package: emacs;

Reported by: Eli Zaretskii <eliz <at> gnu.org>

Date: Sun, 28 Aug 2011 09:25:02 UTC

Severity: normal

Found in version 24.0.50

Done: Eli Zaretskii <eliz <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: 9392 <at> debbugs.gnu.org
Subject: bug#9392: 24.0.50; rmail-forward produces messages in unsupported format that cannot be customized away
Date: Mon, 29 Aug 2011 01:17:39 -0400
> Date: Mon, 29 Aug 2011 05:55:43 +0300
> From: Eli Zaretskii <eliz <at> gnu.org>
> Cc: 9392 <at> debbugs.gnu.org
> 
> > *Note (emacs-mime) MML Definition::
> 
> Thanks.  So you are saying that the _actual_ bug is that rmail-forward
> doesn't run the outgoing message buffer through mml-generate-mime, is
> that right?

Actually, I should have told that the original problem happens with
mail-user-agent set to sendmail-user-agent.

So, given the above input regarding MML, I assumed that message.el
does TRT with MML before sending the forwarded message, and tried
rmail-forward in "emacs -Q".  However, with that configuration, the
code which inserts the MML "<#part ...>" tag is never executed, and in
fact the "*unsent mail*" buffer popped by message.el does not have the
text of the message being forwarded; the body of the composed message
is empty.

AFAICS, the "<#part ...>" tag is not inserted because rmail-forward
expects rmail-start-mail return a non-nil value, but with
message-user-agent it returns nil.

So it looks like message-user-agent is incompatible with
rmail-forward, or else I'm doing something terribly wrong.




This bug report was last modified 13 years and 334 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.