unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: 9392@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	[thread overview]
Message-ID: <E1QxuE7-0005rc-Vz@fencepost.gnu.org> (raw)
In-Reply-To: <83d3fpexjk.fsf@gnu.org> (message from Eli Zaretskii on Mon, 29 Aug 2011 05:55:43 +0300)

> Date: Mon, 29 Aug 2011 05:55:43 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 9392@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.





  reply	other threads:[~2011-08-29  5:17 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-28  9:21 bug#9392: 24.0.50; rmail-forward produces messages in unsupported format that cannot be customized away Eli Zaretskii
2011-08-28 21:04 ` Andreas Schwab
2011-08-29  2:55   ` Eli Zaretskii
2011-08-29  5:17     ` Eli Zaretskii [this message]
2011-08-30  0:36       ` Kenichi Handa
2011-08-30  2:57         ` Eli Zaretskii
2011-08-30  5:47         ` Eli Zaretskii
2011-09-02 10:46           ` Eli Zaretskii
2011-09-02 10:54             ` Julien Danjou
2011-09-02 14:23               ` Eli Zaretskii
2011-09-02 14:27                 ` Julien Danjou
2011-09-02 17:59                   ` Eli Zaretskii
2011-09-02 18:47                     ` Eli Zaretskii
2011-09-02 19:13                       ` Julien Danjou
2011-09-02 19:26                         ` Eli Zaretskii
2011-09-03 21:49                       ` Lars Magne Ingebrigtsen
2011-09-09  9:05                         ` Eli Zaretskii
2011-09-16  3:41                           ` Kenichi Handa
2011-09-16  6:57                             ` Eli Zaretskii
2011-09-16  8:02                               ` Kenichi Handa
2011-09-03  0:24 ` Glenn Morris
2011-09-03  7:36   ` Eli Zaretskii
2011-09-06  6:53 ` Reiner Steib

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1QxuE7-0005rc-Vz@fencepost.gnu.org \
    --to=eliz@gnu.org \
    --cc=9392@debbugs.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).