Archive of RubyForge sup-devel mailing list
 help / color / mirror / Atom feed
From: Ben Walton <bwalton@artsci.utoronto.ca>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] [PATCH] add sendmail hook
Date: Wed, 29 Sep 2010 20:56:53 -0400	[thread overview]
Message-ID: <1285808187-sup-7819@pinkfloyd.chass.utoronto.ca> (raw)
In-Reply-To: <1285769580-15705-1-git-send-email-sascha-pgp@silbe.org>

Excerpts from Sascha Silbe's message of Wed Sep 29 10:13:00 -0400 2010:

> Add a hook that is run in place of the sendmail command. This allows
> last-minute adjustments including sending a separate copy to each
> recipient and setting the envelope sender, i.e. VERP (variable
> envelope return path).

+1 for this.  The patch looks sane although I didn't actually test it.
-Ben

Thanks
-Ben
--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302

_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel


  reply	other threads:[~2010-09-30  1:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-29 14:13 Sascha Silbe
2010-09-30  0:56 ` Ben Walton [this message]
2010-10-08  4:22 ` Rich Lane

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=1285808187-sup-7819@pinkfloyd.chass.utoronto.ca \
    --to=bwalton@artsci.utoronto.ca \
    --cc=sup-devel@rubyforge.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox