From owner-freebsd-questions@FreeBSD.ORG Tue Jul 5 23:14:49 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org 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 7D14D16A41C for ; Tue, 5 Jul 2005 23:14:49 +0000 (GMT) (envelope-from somniosus@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3549243D48 for ; Tue, 5 Jul 2005 23:14:49 +0000 (GMT) (envelope-from somniosus@gmail.com) Received: by wproxy.gmail.com with SMTP id i4so1037209wra for ; Tue, 05 Jul 2005 16:14:48 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Qzi52Z4jsisowh0S3hSBUaMtVJhDEzUpRkplHiU3nz+HHbrIlW4EOMIwLvLpSvWSlYzexfeFa2WkvaG20l/5lKEgtuObnfmH/MdMJN/AahrkdgNE4M4NHvuAmsQ80l0Lv1ByCI6nhtF2YJM0lIVd9dNjDjVJol5oa2yZ3VV1SZY= Received: by 10.54.2.54 with SMTP id 54mr4782810wrb; Tue, 05 Jul 2005 16:14:48 -0700 (PDT) Received: by 10.54.149.7 with HTTP; Tue, 5 Jul 2005 16:14:48 -0700 (PDT) Message-ID: Date: Tue, 5 Jul 2005 16:14:48 -0700 From: cape canaveral To: freebsd-questions@freebsd.org In-Reply-To: <42CB0E22.4010504@mac.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20050705145350.W37501@neptune.atopia.net> <42CB0E22.4010504@mac.com> Subject: Re: Remote access to a user's mail spool X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: cape canaveral List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jul 2005 23:14:49 -0000 On 7/5/05, Chuck Swiger wrote: > Matt Juszczak wrote: > > We're an ISP, and we are currently looking for a way for our tech > > support guys to access customer's email without having shell access to > > the server, or knowing the customer's password. > > > > We'd like to install a custom webmail client on our private internal LA= N > > webserver that would only show the user's inbox and the ability to > > delete the messages (couldn't read messages, etc.). >=20 > The notion of being able to delete messages yet not see them doesn't make= much > sense, frankly. Are they going to just see the sender, or the subject, o= r do > they just delete mail randomly? What problem are you trying to solve? >=20 > -- > -Chuck Most likely the problem they are trying to solve is that of Outlook and Outlook Express choking on corrupt/damaged/unrecognized headers.=20 It's a huge problem for Outlook users these days. http://www.google.com/search?q=3Doutlook+%2Bok+octets+follow&btnG=3DSearch Aaron