Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: exim and bcc
- To: tlug@example.com
- Subject: Re: exim and bcc
- From: "Thomas O'Dowd" <tom@example.com>
- Date: Thu, 1 Mar 2001 15:54:00 +0900
- Content-Disposition: inline
- Content-Type: text/plain; charset=us-ascii
- In-Reply-To: <20010301155105.A19680@example.com>; from jwt-tlug@example.com on Thu, Mar 01, 2001 at 03:51:05PM +0900
- References: <20010301141332.X16710@example.com> <20010301155105.A19680@example.com>
- Reply-To: tlug@example.com
- Resent-From: tlug@example.com
- Resent-Message-ID: <9Sb1bD.A.nV.aLfn6@example.com>
- Resent-Sender: tlug-request@example.com
- User-Agent: Mutt/1.2.5i
On Thu, Mar 01, 2001 at 03:51:05PM +0900, Jim Tittsler wrote: > On Thu, Mar 01, 2001 at 02:13:32PM +0900, Thomas O'Dowd wrote: > > I use exim as my local mta on my machine at home and all mail goes > > out through it. I've noticed though that if I send a Bcc: it is > > visable on the receiving end for all parties which is bad behaviour > > and not what I intended. > > Isn't this a muttism? I use: > unset write_bcc > in my .muttrc to keep it from generating a header (the > bcc addresses only go in the envelope). Ahhhhhhhhhhhhhhhh!!!! Great! Thanks. I confirmed the change, Bcc is gone. Thanks Jim!!! Tom. -- Thomas O'Dowd Noop-de-Noop! tom@example.com http://www.nooper.com
- References:
- exim and bcc
- From: "Thomas O'Dowd" <tom@example.com>
- Re: exim and bcc
- From: Jim Tittsler <jwt-tlug@example.com>
Home | Main Index | Thread Index
- Prev by Date: Re: exim and bcc
- Next by Date: Re: "My Kanpo" open law project
- Prev by thread: Re: exim and bcc
- Next by thread: Re: exim and bcc
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links