From: pierre@baillet.name (Pierre Baillet)
Subject: [sup-talk] [PATCH] Configurable automatic CC and BCC
Date: Wed, 31 Oct 2007 09:42:58 +0100 [thread overview]
Message-ID: <6205b42d0710310142r4c1a699co6776e3180a21e46c@mail.gmail.com> (raw)
In-Reply-To: <6205b42d0710140517n1b006956tef57f60b101568e2@mail.gmail.com>
Hi William,
maybe you came accross my patch, but I don't know what you think about
integrating it to the trunk or not. Maybe it's not near enough in your TODO,
too :)
--
Pierre.
On 10/14/07, Pierre Baillet <pierre at baillet.name> wrote:
>
> Hi,
>
> In case you'd want to always have a given address CCed or BBCed, here is a
> patch that applies to current sup trunk. It adds a "cc" and "bcc" variable
> in the account configuration. Edit your ~/.sup/config.yaml and add bcc and
> cc options. These options are per account.
>
> When in compose and reply mode, sup then automatically adds these headers.
> Current limitation includes a single address per header, could be probably
> extended to a list of addresses...
>
> Feel free to make any comment if you wish so.
> --
> Pierre.
>
>
> :edit_signature: false
> :accounts:
> :default:
> :name: John Doe
> :alternates:
> - john.doe at internet.com
> :email: john at doe.com
> :signature: /home/john/.signature
> :sendmail: /usr/sbin/sendmail -oem -ti
> :bcc: john at home.net
> :cc: john at work.com
>
> --
> Pierre Baillet <pierre at baillet.name>
>
--
Pierre Baillet <pierre at baillet.name>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/sup-talk/attachments/20071031/9d21e900/attachment.html
next prev parent reply other threads:[~2007-10-31 8:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-14 12:17 Pierre Baillet
2007-10-31 8:42 ` Pierre Baillet [this message]
2007-11-02 3:54 ` William Morgan
2007-11-02 11:21 ` Pierre Baillet
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=6205b42d0710310142r4c1a699co6776e3180a21e46c@mail.gmail.com \
--to=pierre@baillet.name \
/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