From owner-freebsd-isp Fri Feb 16 07:33:48 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA10391 for isp-outgoing; Fri, 16 Feb 1996 07:33:48 -0800 (PST) Received: from overlord.dmv.com (root@overlord.dmv.com [206.30.64.6]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA10381 for ; Fri, 16 Feb 1996 07:33:41 -0800 (PST) Received: from overlord.dmv.com by overlord.dmv.com via SMTP (950215.SGI.8.6.10/940406.SGI.AUTO) id KAA16699; Fri, 16 Feb 1996 10:33:15 -0500 Date: Fri, 16 Feb 1996 10:33:15 -0500 (EDT) From: Patrick Ferguson To: Michael Dillon cc: Bruce Bauman , freebsd-isp@freebsd.org, Bruce Bauman Subject: Re: mail question... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org Precedence: bulk Or you could just edit your sendmail config file and place the following line in S0. Basically it's for virtual domains, and it routes all mail addressed user@virtual.dom --> real@virtual.dom (real is the account that is an actual account on your machine. Otherwise, you will loose each name you alias to as a login account.) R$-<@virtual.dom> $#local$:real *** Put this BEFORE R@ $#local$:$n *** This will bypass your local mailer from checking whether the rightside of the lefthand equation is an actual valid account, ie is user@virtual.dom a local account????? This should be the very first line in the S0 section. BTW, replace the @virtual.dom with their domainname and the real with the account that they are gonna pop the mail from remotely. Remember also to put the domainname in the w macro: Cwlocalhost virtual.dom Patrick On Thu, 15 Feb 1996, Michael Dillon wrote: > On Thu, 15 Feb 1996, Bruce Bauman wrote: > > > We have a customer who has a Novell network, and their users want to receive > > Internet mail from us. This customer won't have a static IP address. They just > > want to dial in and fetch mail from us, similar to the way our normal dialup > > customers do (e.g. using POP). > > > > The problem is, they want a single machine on their end to basically dial us > > up and snarf the mail for all of their users, and feed back the outgoing > > mail to us for eventual delivery on the Internet. We want a simple solution. > > Make a sendmail database that forwards mail for all of their users to one > account. But warn them that they will need to sort the mail on their end > and if it is done manually, then their employees email will not be > confidential any more, just like a fax machine. > > Better if you find out what corporate email system they are using and > talk to local VAR's about setting up some sort of gateway, maybe using UUCP. > > Or if they would put a FreeBSD box on their network (an old 386 perhaps) > you could configure it to run a dialin script that makes a PPP connection > and then runs POPMAIL for each usera nd deposits each user's email in a > separate mailbox on the FreeBSD machine. Then they can just run Eudora or > Pegasus on each desktop and the FreeBSD box will be acting as their mail > server. Of course, this requires all machines to be running a TCP/IP > stack. This is unlikely if they have Novell 3.x > > > Michael Dillon Voice: +1-604-546-8022 > Memra Software Inc. Fax: +1-604-546-3049 > http://www.memra.com E-mail: michael@memra.com >