From: nicolas.pouillard@gmail.com (Nicolas Pouillard)
Subject: [sup-talk] [RFC] Bounce messages
Date: Sat, 06 Jun 2009 16:36:12 +0200 [thread overview]
Message-ID: <1244298935-sup-5932@ausone.local> (raw)
In-Reply-To: <1244291795-sup-1695@ntdws12.chass.utoronto.ca>
Excerpts from Ben Walton's message of Sat Jun 06 14:44:15 +0200 2009:
> 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?
It does! Thanks for the explanation.
--
Nicolas Pouillard
http://nicolaspouillard.fr
prev parent reply other threads:[~2009-06-06 14:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-01 0:54 Ben Walton
2009-06-05 16:02 ` William Morgan
2009-06-05 16:20 ` Ben Walton
2009-06-06 10:16 ` Nicolas Pouillard
2009-06-06 12:03 ` Helge Titlestad
2009-06-06 12:44 ` Ben Walton
2009-06-06 14:36 ` Nicolas Pouillard [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1244298935-sup-5932@ausone.local \
--to=nicolas.pouillard@gmail.com \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox