From owner-freebsd-questions@FreeBSD.ORG Tue Jul 8 05:13:35 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F3F5D37B401 for ; Tue, 8 Jul 2003 05:13:34 -0700 (PDT) Received: from catflap.home.slightlystrange.org (pc4-cmbg1-4-cust87.cmbg.cable.ntl.com [80.6.127.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8357F43FBF for ; Tue, 8 Jul 2003 05:13:33 -0700 (PDT) (envelope-from danielby@slightlystrange.org) Received: from danielby by catflap.home.slightlystrange.org with local (Exim 4.20) id 19ZrLf-000N3F-Vm for freebsd-questions@freebsd.org; Tue, 08 Jul 2003 13:13:31 +0100 Date: Tue, 8 Jul 2003 13:13:31 +0100 From: Daniel Bye To: freebsd-questions@freebsd.org Message-ID: <20030708121331.GB88356@catflap.home.slightlystrange.org> Mail-Followup-To: freebsd-questions@freebsd.org References: <20030708084527.GB60097@marvin.penguinpowered.org.uk> <20030708090447.GA34519@rot13.obsecurity.org> <20030708092226.GA60262@marvin.penguinpowered.org.uk> <20030708114422.GA35356@rot13.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="HlL+5n6rz5pIUxbD" Content-Disposition: inline In-Reply-To: <20030708114422.GA35356@rot13.obsecurity.org> User-Agent: Mutt/1.4.1i Sender: Daniel Bye Subject: Re: Bcc field viewable in Mutt generated e-mails X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: dan@slightlystrange.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Jul 2003 12:13:35 -0000 --HlL+5n6rz5pIUxbD Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jul 08, 2003 at 04:44:22AM -0700, Kris Kennaway wrote: > I still see no bcc in this message. The relevant headers are: Not in these examples, maybe - however, I have tested my config (Mutt 1.4.1i, Exim 4.20.1, FreeBSD 4.8-STABLE), and see the same behaviour. A test message sent from my home account to my work account, and Bcc:'d to an alias on the home account, results in the Bcc: field appearing in the headers of the copy received at work.=20 These are the From:, To: and Bcc: from the copy sent to the work address: From: Daniel Bye To: dan.bye@where-I-work.co.uk Bcc: www@slightlystrange.org The Bcc: also shows up (naturally enough) in the copy received by www@, but I, like the OP, am baffled as to why it is visible in the copy received at work. A search on Google turned up this http://tony.rocks.cc/muttrc - a forward search for bcc reveals: unset write_bcc # Exim does not removes Bcc headers So, adding this to mutt's config results in: From: Daniel Bye To: Dan Bye and no Bcc: where it don't belong! I see you are using Exim, as well, Wayne - try `unset write_bcc' in your ~/.muttrc. HTH Dan =20 >=20 > Date: Tue, 8 Jul 2003 10:22:26 +0100 > From: Wayne Pascoe > To: Kris Kennaway > Cc: freebsd-questions@freebsd.org > Subject: Re: Bcc field viewable in Mutt generated e-mails > Message-ID: <20030708092226.GA60262@marvin.penguinpowered.org.uk> > References: <20030708084527.GB60097@marvin.penguinpowered.org.uk> > +<20030708090447.GA34519@rot13.obsecurity.org> > Mime-Version: 1.0 > Content-Type: text/plain; charset=3Dus-ascii > Content-Disposition: inline > In-Reply-To: <20030708090447.GA34519@rot13.obsecurity.org> > User-Agent: Mutt/1.4i > X-System: FreeBSD i386 with kernel 4.8-STABLE > Sender: Wayne --=20 Daniel Bye PGP Key: ftp://ftp.slightlystrange.org/pgpkey/dan.asc PGP Key fingerprint: 3B9D 8BBB EB03 BA83 5DB4 3B88 86FC F03A 90A1 BE8F _ ASCII ribbon campaign ( ) - against HTML, vCards and X - proprietary attachments in e-mail / \ --HlL+5n6rz5pIUxbD Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (FreeBSD) iD8DBQE/CrVrhvzwOpChvo8RAhE3AJ47jXZfGPog0cHybIJBxzpPq6BoygCgvwk4 JuSlYgM9U8OZPqn8lA5fG8Y= =P/Fd -----END PGP SIGNATURE----- --HlL+5n6rz5pIUxbD--