Re: howto bcc the bcc's in mutt
On Wed, Aug 14, 2002 at 12:02:36PM +1000, Chris Kenrick wrote:
> On Wed, Aug 14, 2002 at 01:56:01AM +0000, p wrote:
> > debs,
> >
> > prelim: i just got a promotion--sysop of a
> > hundred-user network. ...peanuts
> > to most on the list, probably....
>
> Congratulations on the promotion, and good luck!
thx. hopefully, i'll be able to populate the
system with linux, debian, of course!
> >
> > prob: when i fire up mutt for emailing
> > those 100 users. i'd like to bcc
> > each user without the other 99
> > users' email addys being included
> > in the bcc. (so, each user's bcc
> > header only has 1 email addy in it,
> > not 100.)
> >
> > q: is there a way for mutt to bcc the
> > bcc's?
>
> I don't follow you here. The recipient of the email can only see the To
> and cc headers, but nothing at all for bcc. So doesn't it do what you
> want already?
>
> - Chris
>
//
...sorry, i knew that my setup wasn't as complete
as it should've been.
...
for example:
i have the 100 users's email addys as
an alias in .muttrc.
i send the same email to each of the
100 users by addressing it to myself
and "bcc-ing" it to the 100 users.
what i've seen is that the 100 users'
email addys are in the "resent-to"
header (like the attached, test
email). what i'm hoping is that
_each user_ doesn't have to see the
other user's email addys, like what
the "list" (deb-user) does--we get
list emails without seeing who else
gets them.
is this "bcc biz" the wrong approach?
my predecessor used to send 3-page emails
in which the content was only maybe 4
lines. the rest was basically all email
addys. what a waste and users made fun
of it. (my brother's email jokes are like
that, too.)
help appreciated,
b.
//
>From bt@pcisys.net Wed Aug 14 03:18:22 2002
Return-Path: <bt@pcisys.net>
Received: from cls210 (pplaw-216-229-42-179.cos.pcisys.net [216.229.42.179])
by leo.pcisys.net (8.12.5/8.12.5) via ESMTP id g7E3IMam001613; Tue, 13 Aug 2002 21:18:22 -0600 (MDT)
env-from (bt@pcisys.net)
Received: from bt by cls210 with local (Exim 3.12 #1 (Debian))
id 17eofu-000304-00; Wed, 14 Aug 2002 03:18:22 +0000
Date: Wed, 14 Aug 2002 03:18:22 +0000
From: p <pplaw@pcisys.net>
To: p <pplaw@pcisys.net>
Subject: test2a
Message-ID: <20020814031822.A11516@pcisys.net>
Reply-To: p <pplaw@pcisys.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
Operating-system: Debian Gnu/Linux ( http://www.debian.org )
Kernel: 2.2.17
Resent-from: p <pplaw@pcisys.net>
Resent-Message-Id: <E17eofu-000304-00@cls210>
Resent-Sender: b <bt@pcisys.net>
Resent-To: pplaw@pcisys.net, v1@pcisys.net, v2@pcisys.net, v3@pcisys.net,
v4@pcisys.net, v5@pcisys.net
Resent-Date: Wed, 14 Aug 2002 03:18:22 +0000
X-Mozilla-Status2: 00000000
Status: RO
testing.
later.
kthxbye.
b.
//
Reply to: