Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: bwalton@artsci.utoronto.ca (Ben Walton)
Subject: [sup-talk] [RFC] Bounce messages
Date: Sun, 31 May 2009 20:54:08 -0400	[thread overview]
Message-ID: <1243817649-7642-1-git-send-email-bwalton@artsci.utoronto.ca> (raw)

Hi All,

I spent a few hours this evening putting together the basics of (I
think) the last feature of mutt that I miss in sup: Message bouncing.

It works in it's current form, but I think it needs a little further
tweaking before it is merge ready.

Currently it's pretty dumb wrt which sendmail command it calls.  It
simply calls sendmail with some sane (for my environment, anyway) args
and a list of recipients (skipping the -t flag which makes it read
recipients from headers in the input).  I didn't want to implement a
second mail variable per account, although that would solve the
problem, and I didn't want to use the default sendmail command with
the -t stripped from the args (although that would also work).

The other thing that I don't like presently is the confirmation UI.
Without resorting to a whole bounce-mode, is there a better way to
handle this in the face of (potentially) multiple recipients that may
make the question stretch outside the viewable area?

I'm interested in what others think is the right solution to these
problems...and whether others besides myself miss this feature of
mutt.

Thanks
-Ben


             reply	other threads:[~2009-06-01  0:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-01  0:54 Ben Walton [this message]
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

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=1243817649-7642-1-git-send-email-bwalton@artsci.utoronto.ca \
    --to=bwalton@artsci.utoronto.ca \
    /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