From owner-freebsd-questions Fri May 18 10: 4:58 2001 Delivered-To: freebsd-questions@freebsd.org Received: from oddjob.adhesivemedia.com (oddjob.adhesivemedia.com [207.202.159.77]) by hub.freebsd.org (Postfix) with ESMTP id 54E9B37B422 for ; Fri, 18 May 2001 10:04:55 -0700 (PDT) (envelope-from philip@adhesivemedia.com) Received: from localhost (philip@localhost) by oddjob.adhesivemedia.com (8.11.1/8.11.1) with ESMTP id f4IH4kx89314; Fri, 18 May 2001 10:04:46 -0700 (PDT) (envelope-from philip@adhesivemedia.com) Date: Fri, 18 May 2001 10:04:46 -0700 (PDT) From: Philip Hallstrom To: Sheldon Hearn Cc: Subject: Re: stunnel + pop-b4-smtp In-Reply-To: <68481.990178103@axl.fw.uunet.co.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG The qpopper port (version 4.x) has built in support for SSL so you don't need stunnel at all.. it works for me... -philip On Fri, 18 May 2001, Sheldon Hearn wrote: > > Hi folks, > > Has anyone had any luck using something like stunnel to provide a POP3S > service that doesn't interfere with pop-b4-smtp functionality? > > The problem with stunnel is that the POP3 server sees all incoming > connections coming from the IP address on which the POP3S connection was > accepted by stunnel. This completely thwarts pop-b4-smtp. :-( > > Ciao, > Sheldon. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message