From owner-freebsd-isp Mon Nov 27 07:57:43 1995 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id HAA08558 for isp-outgoing; Mon, 27 Nov 1995 07:57:43 -0800 Received: from itchy.mosquito.com (itchy.mosquito.com [206.205.132.2]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id HAA08551 for ; Mon, 27 Nov 1995 07:57:36 -0800 Received: (from boot@localhost) by itchy.mosquito.com (8.6.11/8.6.9) id KAA27423; Mon, 27 Nov 1995 10:58:31 -0500 From: Bruce Bauman Message-Id: <199511271558.KAA27423@itchy.mosquito.com> Subject: limiting mailbox size? To: freebsd-isp@freebsd.org Date: Mon, 27 Nov 1995 10:58:31 -0500 (EST) Cc: boot@itchy.mosquito.com (Bruce Bauman) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 360 Sender: owner-isp@freebsd.org Precedence: bulk We are a small ISP running FreeBSD. We run quotas to prevent users from using more disk space than their limit, but occasionally we find users with huge mailboxes in /var/mail. How do other providers deal with this? Should I just write a perl script that sends mail to the user, or sends a mail message when they log in? -- Bruce Bauman Mosquito Net, Inc. From owner-freebsd-isp Mon Nov 27 09:01:23 1995 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id JAA12985 for isp-outgoing; Mon, 27 Nov 1995 09:01:23 -0800 Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.20.4]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id JAA12980 for ; Mon, 27 Nov 1995 09:01:16 -0800 Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id LAA11217; Mon, 27 Nov 1995 11:00:03 -0600 From: Joe Greco Message-Id: <199511271700.LAA11217@brasil.moneng.mei.com> Subject: Re: limiting mailbox size? To: boot@mosquito.com (Bruce Bauman) Date: Mon, 27 Nov 1995 11:00:01 -0600 (CST) Cc: freebsd-isp@freebsd.org, boot@itchy.mosquito.com In-Reply-To: <199511271558.KAA27423@itchy.mosquito.com> from "Bruce Bauman" at Nov 27, 95 10:58:31 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-isp@freebsd.org Precedence: bulk > We are a small ISP running FreeBSD. We run quotas to prevent users from using more disk > space than their limit, but occasionally we find users with huge mailboxes in /var/mail. > How do other providers deal with this? Should I just write a perl script that sends mail > to the user, or sends a mail message when they log in? Actually, threats work well :-) "Users exceeding 5MB in their incoming mailbox will automatically have their mailbox zeroed". This is a tough one to deal with. What do you do? You can write a local mailer that checks their mailbox size and refuses to deliver if the mailbox is too full. Listservs will interpret the bounce message as an error and unsubscribe the user. That pisses people off. You can write a local mailer that checks their mailbox size and (if it is too full) gzip's their current mailbox into their home directory, zeroes the mailbox, and mails them a note about what happened, why, and how they can read the gzipped mail. This is an advantage if you charge by the byte for home directory space. If you quota limit home directories, this doesn't buy you anything other than to move the problem elsewhere. No clean solutions that I've seen. :-) ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 From owner-freebsd-isp Mon Nov 27 09:29:14 1995 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id JAA15357 for isp-outgoing; Mon, 27 Nov 1995 09:29:14 -0800 Received: from metronet.com (root@feenix.metronet.com [192.245.137.1]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id JAA15348 for ; Mon, 27 Nov 1995 09:29:08 -0800 Received: from eul141.metronet.com by metronet.com with SMTP id AA09299 (5.67a/IDA1.5hp for ); Mon, 27 Nov 1995 11:29:08 -0600 Date: Mon, 27 Nov 1995 11:29:08 -0600 Message-Id: <199511271729.AA09299@metronet.com> X-Sender: mnealey@metronet.com X-Mailer: Windows Eudora Light Version 1.5.2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: freebsd-isp@freebsd.org From: Mike Nealey Subject: Dynamic PPP... Sender: owner-isp@freebsd.org Precedence: bulk Hi all, I have a quick question. Is anyone out there offering dynamic ppp on their systems? If you are, how are you setting it up? I have read the man page and assorted documentation for ppp/pppd and the solution offered seems rather ugly. Is there a more elegant solution? Mike N. From owner-freebsd-isp Mon Nov 27 20:22:41 1995 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id UAA00452 for isp-outgoing; Mon, 27 Nov 1995 20:22:41 -0800 Received: from agora.rdrop.com (root@agora.rdrop.com [199.2.210.241]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id UAA00447 for ; Mon, 27 Nov 1995 20:22:38 -0800 Received: by agora.rdrop.com (Smail3.1.28.1 #8) id m0tKHYk-0002SPC; Mon, 27 Nov 95 20:22 PST Message-Id: From: batie@agora.rdrop.com (Alan Batie) Subject: Re: limiting mailbox size? To: boot@mosquito.com (Bruce Bauman) Date: Mon, 27 Nov 1995 20:22:02 -0800 (PST) Cc: freebsd-isp@freebsd.org In-Reply-To: <199511271558.KAA27423@itchy.mosquito.com> from "Bruce Bauman" at Nov 27, 95 10:58:31 am X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 760 Sender: owner-isp@freebsd.org Precedence: bulk > How do other providers deal with this? I make /var reasonably large and if it starts getting within a few 10's of megabytes of full, send nasty mail to the pigs. If it becomes critical, I compress the mailbox and put it in their home directory. If their home directory overflows their quota, that's their problem, but I don't have to deal with bounced mail and they don't get kicked off mailing lists. I would probably automate it if were a real problem, but it's pretty rare. -- Alan Batie ______ batie@agora.rdrop.com \ / Freedom for me to be and do +1 503 452-0960 \ / only what *you* approve of 45 28 59 N / 122 43 20 W / 440' MSL \/ is no freedom at all. From owner-freebsd-isp Mon Nov 27 20:47:09 1995 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id UAA01067 for isp-outgoing; Mon, 27 Nov 1995 20:47:09 -0800 Received: from neptune.pristine.com.tw ([192.72.150.2]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id UAA01060 for ; Mon, 27 Nov 1995 20:47:03 -0800 Received: (from team_fbf@localhost) by neptune.pristine.com.tw (8.6.11/8.6.9) id MAA09931; Tue, 28 Nov 1995 12:44:09 GMT From: ywliu Message-Id: <199511281244.MAA09931@neptune.pristine.com.tw> Subject: Re: limiting mailbox size? To: boot@mosquito.com (Bruce Bauman) Date: Tue, 28 Nov 1995 12:44:09 +0000 () Cc: freebsd-isp@freebsd.org, boot@itchy.mosquito.com In-Reply-To: <199511271558.KAA27423@itchy.mosquito.com> from "Bruce Bauman" at Nov 27, 95 10:58:31 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Length: 1065 Sender: owner-isp@freebsd.org Precedence: bulk > > We are a small ISP running FreeBSD. We run quotas to prevent users from using more disk > space than their limit, but occasionally we find users with huge mailboxes in /var/mail. > How do other providers deal with this? Should I just write a perl script that sends mail > to the user, or sends a mail message when they log in? > > -- Bruce Bauman > Mosquito Net, Inc. > We had the same problem here. First, we tried to set up a quota limitation on the mail partition, but when sendmail writes to the user box, its euid is root, so it still can writes to users' mail box. But, since most of our users are using POP mail, and the popper would duplicate the user's mail box in /var/mail, so quota restriction still working. But if the user reads his mail via ELM, PINE, etc., this doesn't work. Now we do this manually : if the user's mail quota is going to exceed, we mail a warning message to him/her, and when quota is exceeded, we redirect the user's mail to another place until s/he reduces the disk usage. --- Yen-Wei Liu team_fbf@pristine.com.tw From owner-freebsd-isp Tue Nov 28 10:12:49 1995 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id KAA23493 for isp-outgoing; Tue, 28 Nov 1995 10:12:49 -0800 Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.20.4]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id KAA23484 for ; Tue, 28 Nov 1995 10:12:44 -0800 Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id MAA12856; Tue, 28 Nov 1995 12:12:03 -0600 From: Joe Greco Message-Id: <199511281812.MAA12856@brasil.moneng.mei.com> Subject: Re: Dynamic PPP... To: mnealey@metronet.com (Mike Nealey) Date: Tue, 28 Nov 1995 12:12:03 -0600 (CST) Cc: freebsd-isp@freebsd.org In-Reply-To: <199511271729.AA09299@metronet.com> from "Mike Nealey" at Nov 27, 95 11:29:08 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-isp@freebsd.org Precedence: bulk > Hi all, > > I have a quick question. Is anyone out there offering dynamic ppp on > their systems? If you are, how are you setting it up? I have read the man > page and assorted documentation for ppp/pppd and the solution offered seems > rather ugly. Is there a more elegant solution? Stupid and yet simple: /usr/local/bin/ppplogin (login shell): #! /bin/sh - stty crtscts tty=`tty` tty=`basename ${tty}` exec /usr/sbin/ppp -direct "${tty}" /etc/ppp/ppp.conf: ttyd8: set debug lcp set ifaddr 206.55.67.17 206.55.67.72 set timeout 43200 ttyd9: set debug lcp set ifaddr 206.55.67.17 206.55.67.73 set timeout 43200 ttyda: set debug lcp set ifaddr 206.55.67.17 206.55.67.74 set timeout 43200 .... la de da, etc. Not true dynamic PPP in that you are reserving an IP for each serial port. However, this does prevent you from doing foolish things like overcommitting and it does make administration simpler because you can always reconstruct who was on a port given a hostname or whatever with very little effort. ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 From owner-freebsd-isp Thu Nov 30 08:29:13 1995 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id IAA01083 for isp-outgoing; Thu, 30 Nov 1995 08:29:13 -0800 Received: from kryten.atinc.com (kryten.Atinc.COM [198.138.38.7]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id IAA01015 ; Thu, 30 Nov 1995 08:28:27 -0800 Received: (jmb@localhost) by kryten.atinc.com (8.6.9/8.3) id LAA07158; Thu, 30 Nov 1995 11:20:46 -0500 Date: Thu, 30 Nov 1995 11:20:45 -0500 (EST) From: "Jonathan M. Bresler" Subject: Re: Majordomo coredumping To: freebsd-hackers@freebsd.org, freebsd-hubs@freebsd.org, freebsd-isp@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org Precedence: bulk On Thu, 30 Nov 1995, Basket Case wrote: > Ive been trying to setup majordomo with little or no avail. When Majordomo > is running -- when I send it asking for help, it replies just fine. But when > I ask to be subscribed to any list or do anything with Majordomo, it decides > to take a core for some odd reason. Here are is the bug that appears > when I run Majordomo (v 1.9.3 with fbsd) couple of options: --verify that the perl scripts are using /usr/sbin/sendmail not /usr/lib/sendmail --make sure that wrapper is compiled with the correct flags --use majordomo 1.92 available from kryten.atinc.com. --wait for the majordomo port. what happened to the majordomo port that was due monday???!!! well. i installed 2.1.0R onto the second disk, the first disk WAS 1.1.5.1 now its non-bootable . a&t lost internet connectivity for 2 days. and i am running late on the port. i will get the port out. my apologies to everyone that is waiting on the port. jmb Jonathan M. Bresler FreeBSD Postmaster jmb@FreeBSD.ORG play go. ride bike. hack FreeBSD.--ah the good life i am moving to a new job. PLEASE USE: jmb@FreeBSD.ORG From owner-freebsd-isp Fri Dec 1 13:29:13 1995 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id NAA25762 for isp-outgoing; Fri, 1 Dec 1995 13:29:13 -0800 Received: from okjunc.junction.net (michael@okjunc.junction.net [199.166.227.1]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id NAA25757 for ; Fri, 1 Dec 1995 13:29:08 -0800 Received: (from michael@localhost) by okjunc.junction.net (8.6.11/8.6.11) id NAA31314; Fri, 1 Dec 1995 13:32:29 -0800 Date: Fri, 1 Dec 1995 13:32:29 -0800 (PST) From: Michael Dillon X-Sender: michael@okjunc.junction.net To: freebsd-isp@freebsd.org Subject: Anyone ever used FDDI cards? Message-ID: Organization: we provide consulting re: Internet servers MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org Precedence: bulk We need to connect a gateway router to the Internet via an FDDI interface and would prefer to use a FreeBSD box for this. I know that there are drivers for a couple of DEC FDDI cards but I don't know how well tested these are. Has anyone else here used FDDI cards in a similar situation? Michael Dillon Voice: +1-604-546-8022 Memra Software Inc. Fax: +1-604-542-4130 http://www.memra.com E-mail: michael@memra.com