After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 200166 - "redirect" command
"redirect" command
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Mailer
unspecified
Other All
: Normal enhancement
: ---
Assigned To: Jeffrey Stedfast
Evolution QA team
: 205729 214836 216963 (view as bug list)
Depends on: 201085
Blocks: 216098 216547
 
 
Reported: 2000-05-25 07:00 UTC by Dan Winship
Modified: 2013-09-10 14:01 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement



Description Dan Winship 2000-05-25 07:00:20 UTC
to make Jamie happy :)
Comment 1 Dan Winship 2001-01-08 17:32:19 UTC
Attach this to the "Forward" toolbar icon
Comment 2 Luis Villa 2001-07-09 22:07:14 UTC
Is this is futured, then cleaning up the Actions > Forward As menu is
a blocker. Not a big deal, just a reminder, in case you want to file
it as a separate bug.
Comment 3 Jeffrey Stedfast 2001-07-28 17:15:50 UTC
*** bug 205729 has been marked as a duplicate of this bug. ***
Comment 4 Luis Villa 2001-10-31 22:43:03 UTC
Is this 1.1able? we continue to see old mutt/pine users who want this.
Comment 5 Luis Villa 2001-11-26 17:04:15 UTC
Because of the decision to remap 1.1->1.2 and 1.2->1.4, I'm going to be
moving a large number of bugs around in the bugzilla. You can just
search on 'body contains' 'Because of the decision to remap' and mark
all as read. Please direct all questions about this change to
evolution@ximian.com, not the bug.
Luis

Comment 6 Luis Villa 2001-12-07 17:27:09 UTC
major because of continued user demand.
Comment 7 Heath Harrelson 2001-12-10 07:48:24 UTC
*** bug 216963 has been marked as a duplicate of this bug. ***
Comment 8 Jeffrey Stedfast 2001-12-11 03:01:39 UTC
personally I think they should just use forward...

I started to implement this but it got to be a pain in the ass because
the composer always sets From:, To:, Cc:, etc and it needs to set
Resent-To:, Resent-From:, Resent-Cc:, etc...

not only that, but camel needs to be all hacked up to realise that if
there are Resent-* headers to use those in place of the normal address
headers.

*sigh*
Comment 9 Dan Winship 2001-12-11 15:20:26 UTC
don't make camel_transport_send look at resent- headers. Just
use camel_transport_send_to instead.
Comment 10 Jeffrey Stedfast 2001-12-21 21:25:26 UTC
I've fixed camel_transport_send_to() to take a CamelAddress rather
than a GList now to make this easier.

I guess the next step is deciding if the composer should have a
"Redirect" mode or whether I should just open the composer and do some
hackery action after the user hits Send to convert all From/To/Cc/Bcc
to Resent-* and replace the original From/To/Cc/Bcc headers.

I'm not sure I like either way, but I think the Redirect-mode way
would be cleanest?
Comment 11 Dan Winship 2001-12-21 21:39:34 UTC
One idea I'd had before was to open the composer with a MailDisplay
in the body instead of an editor control. (I don't think any other
mailers let you edit when redirecting either). So then you see
the old headers there, and you type the new recipients, and send it.
Comment 12 Jeffrey Stedfast 2002-01-15 22:04:54 UTC
danw: how about just using the html-editor-control but de-sensitizing
it? That's what I'd been planning to do...

my next question is whether or not to make CamelMimeMessage know about
Resent-To/Cc/Bcc (ie, adding CAMEL_RECIPIENT_RESENT_TO and
CAMEL_RECIPIENT_RESENT_CC macros). Bah, probably not, since it'd be
lame to have camel_mime_message_get_resent_from().
Comment 13 Heath Harrelson 2002-01-17 01:42:13 UTC
*** bug 214836 has been marked as a duplicate of this bug. ***
Comment 14 Jeffrey Stedfast 2002-01-29 21:26:01 UTC
yay, this works n stuff now.