From owner-freebsd-current Wed Oct 3 17: 4: 2 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.cicely.de (ppp96.uni-duisburg.de [134.91.19.96]) by hub.freebsd.org (Postfix) with ESMTP id C60B437B403 for ; Wed, 3 Oct 2001 17:03:57 -0700 (PDT) Received: (from ticso@localhost) by mail.cicely.de (8.11.0/8.11.0) id f9403mg01704; Thu, 4 Oct 2001 02:03:48 +0200 (CEST) Date: Thu, 4 Oct 2001 02:03:47 +0200 From: Bernd Walter To: Nate Williams Cc: tlambert2@mindspring.com, current@FreeBSD.ORG Subject: Re: uucp user shell and home directory Message-ID: <20011004020347.C110@cicely20.cicely.de> References: <15289.56953.709463.415400@nomad.yogotech.com> <3BBB5D65.4A064AC0@mindspring.com> <15291.24332.479938.736587@nomad.yogotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <15291.24332.479938.736587@nomad.yogotech.com>; from nate@yogotech.com on Wed, Oct 03, 2001 at 12:55:08PM -0600 X-Operating-System: NetBSD cicely20.cicely.de 1.5 sparc Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Oct 03, 2001 at 12:55:08PM -0600, Nate Williams wrote: > > Tell me, is your mail compliant with the non-disclosure of "Bcc:" > > recipients requirement? If fetchmail doesn't strip the tunneling > > headers (it doesn't), then the headers disclose "Bcc:"'ed > > recipients to anyone who chooses to look. > > It sure is, because it's the responsibility of the mail sending program > to handle this. Fetchmail is a mail retrieval program, so it's only job > is to fetch the mail that is already delivered to me. You have missed the point: It's the responsibility of of the sending program not to put bcc informations into the data part of the mail. Since POP3 only stores the data part you won't see it unless the mailserver puts envelope informations into the data part. Now that it's the job of the POP3 client to remove these and reuse it as envelope informations. The typical Problems are: - Cheap implementations try to guess envelope informations from the To: and CC: Header. - Better implementations require envelope informations put into the header part by the MTA on the POP3 Server. - Realy working implementations also need to remove the helper headers. Otherwise a recpient would get the header encoded envelope. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message