Excerpts from Nicolas Pouillard's message of Sat Jun 06 06:16:55 -0400 2009: > I don't get the purpose of this, how it is different from hitting 'D' to send > again the same message?
Look at the From: header when you do that. It gets set to _your_ address. You could use D, edit the from address to that of the original sender and then fire to achieve the same effect (although I'm not sure how it handles attachments, etc), but that's a lot of typing for a common action. I also believe that with D, since you're injecting a new message with original content, that you'd lose much of the original header info. The idea is that when you 'bounce' the message, it's akin to you having had a .forward in place at MTA delivery time. Redirect, not forward. My biggest use case for this is bouncing mail sent to me personally asking for support into our ticket system. The original sender will see the autoreply with the ticket id, etc because the From: header contained their address. Colleagues using other mail clients lacking this feature will forward mail to the ticket system which sees them get the replies. They then have to go into the ticket and set a proper 'requester' address for further correspondence on the ticket. I remember when I discovered this feature in mutt how weird I thought it was. It wasn't long before it was in common use for me though. Does that make sense? Thanks -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting.
signature.asc
Description: PGP signature
_______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk
